Skip to content

MLOperation #74

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
eduard93 opened this issue Apr 3, 2020 · 1 comment
Open

MLOperation #74

eduard93 opened this issue Apr 3, 2020 · 1 comment
Labels
enhancement New feature or request

Comments

@eduard93
Copy link
Contributor

eduard93 commented Apr 3, 2020

A lot of models conform to the same interface:

  • Fit(X, Y, Modeltype, Hyperparameters) → trained model
  • Predict(X)Y
  • Optimize(Model, HyperparameterBoundaries, SearchStrategy) → Optimized model (via Hyperparameter optimization)

I propose adding a new BO (or extending existing PythonOperation) to automatically train/use the models, by providing these high-level requests:

  • FitRequest
  • PredictRequest
  • ValidateRequest

Questions:

  1. Passing X, Y is trivial but what about hyperparams? I can write/extract a list of params for each supported model but how to make it convenient for user?
  2. This is also a departure from our current approach of Python code being written by user into a low-code territory. What do you think about it?
  3. How do we do pipelines?

Ideas? @lukyanchikov, @bdeboe, @tom-dyar

@eduard93 eduard93 added the enhancement New feature or request label Apr 3, 2020
@eduard93
Copy link
Contributor Author

Also add some Hyperparameter optimization.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant