Skip to content
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

should a learner have a model as a state member variable? #11

Closed
berndbischl opened this issue Aug 28, 2018 · 3 comments
Closed

should a learner have a model as a state member variable? #11

berndbischl opened this issue Aug 28, 2018 · 3 comments

Comments

@berndbischl
Copy link
Sponsor Member

this matches better with mlrPipelines

@berndbischl
Copy link
Sponsor Member Author

and sklearn

@larskotthoff
Copy link
Sponsor Member

Sounds to me like having a workflow or similar object to combine learner and model would be better. It's not clear to me how a learner with state would fit into the current framework. For example, what happens when a learner with a model is wrapped? Model removed or automatically retrained? Same with changing hyperparameters for a learner.

@berndbischl
Copy link
Sponsor Member Author

we already decided this for the new framework. it makes the new API better.
you can see this when we document this a bit better.

short answer:

Sounds to me like having a workflow or similar object to combine learner and model would be better.

we do this. the object "Learner" now combines calls regarding training, predictions and model. this makes everything simpler and more natural.

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

No branches or pull requests

2 participants