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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
Force ModelCheckpoint callback to run last #5731
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for sending this out so quickly @awaelchli ! Any reason this is blocked on #5621? Can this go in first and then be refactored by #5621?
Codecov Report
@@ Coverage Diff @@
## release/1.2-dev #5731 +/- ##
================================================
- Coverage 88% 88% -0%
================================================
Files 181 181
Lines 12890 12747 -143
================================================
- Hits 11339 11195 -144
- Misses 1551 1552 +1 |
53b55a7
to
9812866
Compare
Hello @awaelchli! Thanks for updating this PR. There are currently no PEP 8 issues detected in this Pull Request. Cheers! 馃嵒 Comment last updated at 2021-02-03 14:38:18 UTC |
9812866
to
e22d74f
Compare
@ananthsub No particular reason, just a matter of rebasing. I changed it now |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM !
What does this PR do?
Force ModelCheckpoint callbacks to run last, ensuring that all states get saved to the checkpoint.
The test that I added fail if we remove the changes in the callback connector.
This change only affects usecases where the user provides their own callback list.
The automated default ModelCheckpoint was already running last before this PR.
PR #5615 will make use of this helper function and add more tests to ensure the same applies to the model checkpoints defined by configure_callbacks.
Before submitting
PR review
Anyone in the community is free to review the PR once the tests have passed.
Before you start reviewing make sure you have read Review guidelines. In short, see the following bullet-list:
Did you have fun?
Make sure you had fun coding 馃檭