-
Notifications
You must be signed in to change notification settings - Fork 2
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
save a pickle file at save_every
iteration?
#27
Comments
I'm testing a new branch |
Some current caveats - loading in a checkpoint means that any parameters that are changed in the CLI script will be disregarded. I don't fully know how to handle this right now. |
I can have a look in a few days. Thanks for taking the time to hack this together... I think it's fine to ignore the CLI parameters if we include a warning statement. |
Where are we w/r/t this? |
This is implemented in the v0.2.0 branch but will require some io functions to properly handle the pickle files. link to the saving function here |
Is it necessary to have an additional copy of the model along with the checkpoints we currently have implemented? |
Updated tests to test for checkpoints Fixed testing bug: prefix=tmp Implemented safer trans_disnts retrieval, mentioned in Issue #47
Instead of saving the data at the end, can we update a pickle at every
save_every
iteration? It would be nice to have a saved output in case the modeling fails for some reasonThe text was updated successfully, but these errors were encountered: