This repository has been archived by the owner on Dec 16, 2022. It is now read-only.
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.
Addresses a bug in #5534.
Changes proposed in this pull request:
There were two subtle bugs in
ShouldValidateCallback
merged in #5534. One caused validation to always happen after the first epoch regardless ofvalidation_start
. The other caused validation to happen everyvalidation_interval + 1
epochs instead of everyvalidation_interval
epochs. Fixed both with the following changes:on_start
method toShouldValidateCallback
that correctly sets_should_validate_this_epoch
when training begins.on_epoch
is called at the end of every epoch, it needs to considerepoch + 1
(instead ofepoch
) when setting_should_validate_this_epoch
.TrainerTest.test_should_validate_callback
so that it fails without these fixes.Before submitting
section of the
CONTRIBUTING
docs.Writing docstrings section of the
CONTRIBUTING
docs.After submitting
codecov/patch
reports high test coverage (at least 90%).You can find this under the "Actions" tab of the pull request once the other checks have finished.