You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 19, 2021. It is now read-only.
I think changing people's configuration files is a bit invasive and could lead to race conditions (e.g. if the user has left open an editor). What we could do is adding an option that copies the configuration file on each epoch with an improvement, with the model file for that epoch. So, you'd have epoch-15.conf, epoch-23.conf, etc.
Imo, one for the ultimately best epoch should be enough. But on the other hand, it'd be straight forward to write a script to do predictions for all epochs which showed improvements if there's a config for each of those. So not completely sure what I'd prefer.
It's just a minor thing but I felt like setting the epoch was the only hurdle to automating prediction (& evaluation).
picking the epoch with the highest number should correspond to the best epoch when used in conjunction with only saving upon improvements. Maybe there could be a flag use latest?
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Maybe for sticker2, if it's too invasive for sticker?
The text was updated successfully, but these errors were encountered: