Default EarlyStopping.check_on_train_epoch_end=True
#8286
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do?
After the changes in #7357 (not released yet), this is the safer default value as
train_epoch_end
will run aftervalidation_end
so it is more likely that the monitored value will have been logged. This assumes that most users want to run their ES callback at the end of the epoch and not somewhere in the middle.Structure BEFORE #7357: running validation at the end of the epoch
Structure AFTER #7357, BEFORE this PR: running validation at the end of the epoch
Structure AFTER #7357, AFTER this PR: running validation at the end of the epoch
This matches the
ModelPruning
flag: https://github.com/PyTorchLightning/pytorch-lightning/blob/83039ba4705b02fbb55d5922d15a258a2f041986/pytorch_lightning/callbacks/pruning.py#L74And one for
ModelCheckpoint
will be added in a follow-up PR.Included some very minor typing/test changes
Part of #7724
Before submitting
PR review