Repository navigation
save_last to save last checkpoint - #544
Conversation
|
Should be marked as relevant issue in summation model also right? |
|
@felix-e-h-p have you tested this already on a dummy model run? If so could you please link that wandb run and detail any checking you did to check this works as expected? Obviously no test coverage on this so would be good to know it's already been tried and works as expected |
Yeah will do so later today In here - https://wandb.ai/openclimatefix/pvnet_uk_test/runs/ Saving locally then gonna read step count and early stopping counter - have limited at low train and val batches so shouldn't be too long to check it |
|
All good. 50 epochs with 100 train sample limit, best is 49, I loaded best and last just for a direct check: last step 5000 | best step 4900 |
Related to #542
save_last: Truewas meant to save the model from the most recent epoch tolast.ckpt.last.ckptis written when a top-k checkpoint is saved at the same step.save_top_k: 1, so only happens when validation loss improves, andlast.ckptends up being a copy of the best ckpt.save_last: Truedid save real last epoch.Changes:
configs.example/callbacks/default.yaml: turned offsave_last. added secondModelCheckpointwithlast_checkpoint. Hence saves after every validation and overwriteslast.ckpteach time.pvnet/training/train.py: Both callbacks now to be saved to the same run folder. The config files are still saved once, as before.tests/training/test_train.py: Updated fixture accordingly