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
We can have the current checkpointing logic as is to check point every specific interval
We can enhance the trainer code to take a custom function callback from the scenario code that dictates which is the best checkpoint to use based on operations on the custom metric relevant to that scenario. Then the trainer can overwrite the best checkpoint based on scenario owner implemented custom logic in the function provided to the trainer and by default we can have the latest checkpoint as the best checkpoint.
jsleep
changed the title
best <metric> checkpointing
user defined save_best_checkpoint() hook
Sep 16, 2021
it should be a feature of our library to keep the "best" checkpoint based on a tracked metric like the minimum value of validation loss.
this could be a semi-big change because:
The text was updated successfully, but these errors were encountered: