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

upload the learner object with each run #411

Open
giuseppec opened this issue Mar 12, 2018 · 2 comments
Open

upload the learner object with each run #411

giuseppec opened this issue Mar 12, 2018 · 2 comments

Comments

@giuseppec
Copy link
Member

giuseppec commented Mar 12, 2018

There are sometimes bugs in mlr (e.g. mlr-org/mlr#2218) or OpenML (e.g. 171aee9 ) causing critical issues (e.g. some hyperparameters are not uploaded properly on the OpenML server).
Maybe we should always upload the learner object just to be sure that if something went wrong, one can still get the hyperparameters from the uploaded mlr learner object.
I thought of uploading just the result of getHyperPars(lrn) instead of the learner object itself, but this still does not solve the issue when there are also bugs in mlr (e.g. mlr-org/mlr#2218).

@joaquinvanschoren
Copy link
Contributor

joaquinvanschoren commented Mar 12, 2018 via email

@giuseppec
Copy link
Member Author

giuseppec commented Mar 12, 2018

@joaquinvanschoren do you think this could be a file storage problem for the server? A mlr learner object can be up to 0.1 MegaByte and we currently have 9.000.000 runs now. Or are these peanuts?

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