You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently we have a functional API with static methods like build_model.build_model_from_featureset and predict.model_predictions. Not only are these a bit of a mouthful, they're also a bit unintuitive because of how differently they are used than the corresponding sklearn functionality. I suggest that we try to modify our API to be more like that of sklearn, specifically:
Add a Model class that wraps a sklearn model and provides an sklearn-like API (.fit, .predict, .predict_proba) for interacting with Featureset objects.
(optional) Also change featurize to behave more like an sklearn preprocessor; maybe you'd initialize a Featureset and call .transform on a dataset? This is less obvious but there's probably some improvement to be made here as well.
The text was updated successfully, but these errors were encountered:
Currently we have a functional API with static methods like
build_model.build_model_from_featureset
andpredict.model_predictions
. Not only are these a bit of a mouthful, they're also a bit unintuitive because of how differently they are used than the correspondingsklearn
functionality. I suggest that we try to modify our API to be more like that ofsklearn
, specifically:Model
class that wraps asklearn
model and provides ansklearn
-like API (.fit
,.predict
,.predict_proba
) for interacting withFeatureset
objects.featurize
to behave more like ansklearn
preprocessor; maybe you'd initialize aFeatureset
and call.transform
on a dataset? This is less obvious but there's probably some improvement to be made here as well.The text was updated successfully, but these errors were encountered: