by asavinov on 12/3/18, 5:58 PM with 24 comments
by ericand on 12/3/18, 7:04 PM
Very intriguing and thoughtful statement. I hadn't ever thought of it that way.
by asavinov on 12/3/18, 6:01 PM
* Feature engineering and machine learning: Lambdo does not distinguish them and treats them as data transformations
* Model training and prediction: both feature definitions and ML models can be trained as part of one workflow
* Table population and column evaluation: workflow consists of nodes of these two types. This makes it similar to Bistro: https://github.com/asavinov/bistro
Lambdo is intended for the following use cases:
* Numerous derived features with parameters derived from the data
* Regular re-training is required by using the same features as those to be used during prediction
* Time series analysis because it is where the quality of derived features is especially important
* Customization via user-defined Python functions
by kmax12 on 12/3/18, 7:24 PM
I see this tool as a something that can help with the deployment piece of the feature engineering. As things stand, it's "easy" to package and deploy modeling code, but much harder to package up your feature engineering workflow. In part because there is no agreed upon standard for developing feature engineering pipelines.
I'd be curious how this could be combined with a library like Featuretools (http://github.com/featuretools/featuretools/) which helps automate the discovery of features, but currently has less functionality related to deployment.
(full disclosure: I work on Featuretools)
by mooneater on 12/3/18, 7:06 PM
- Where does it sit in relation to other data science components?
- What does it integrate with, and what is it agnostic to?
- Smallest self-contained use case? I see some examples in the repo readme but they are not self-contained so its harder for me to imagine its use