Fix: epoch does not increase after finishing warming up #24
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
After the warming up phase, executing `scheduler_warmup.step()` does not affect `scheduler_warmup.last_epoch` Since in `scheduler_warmup.step`, either epoch is None or not, `self.after_scheduler.step` updates `self.after_scheduler.last_epoch` instead of `self.last_epoch`. And it is reasonable to add `self.total_epoch + 1` to make epochs seem to be continuing.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
After the warming up phase, executing
scheduler_warmup.step()does not affectscheduler_warmup.last_epochSince in
scheduler_warmup.step, either epoch is None or not,self.after_scheduler.stepupdatesself.after_scheduler.last_epochinstead ofself.last_epoch. And it is reasonable to addself.total_epoch + 1to make epochs seem to be continuing.