-
Notifications
You must be signed in to change notification settings - Fork 156
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
serializable
and restore!
should be "safe" to use any time
#965
Comments
@ericphanson Thanks for reporting. I get the idea that (However, Perhaps you mean that the data should be preserved in the untrained case? |
Ah ok, I’m probably too used to neural nets where you can predict with untrained models (using the randomly initialized weights), it will just be a very bad prediction. In that case, the use is two fold: (1) to write tests of code that saves and loads models (don’t need to have a trained one around to test it), and (2) if you want to save checkpoints out starting from the very beginning, so you can track validation loss since the beginning. In this case maybe it makes less sense, in which case an informative error sounds good. |
Ah, I see now where you were coming from.
That's my feeling also. The following are now addressed at JuliaAI/MLJBase.jl@ec977aa:
|
thank you! |
I think it would be helpful if one could call
serializable
andrestore!
on un-fit models, as well as multiple times in a row. Why? This makes it much easier to e.g. save a model, then load it, then save it again, and have models "safe" to be saved any time.MWE of the issues:
As a workaround, I am checking-before-calling with
and
The text was updated successfully, but these errors were encountered: