Align polynomial scheduler with other schedulers #549
Merged
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
|
@andrey-churkin please fix the merge conflicts. |
andrey-churkin
force-pushed
the
ac/polynomial_scheduler
branch
from
f94c690
to
867b68e
Compare
Done. |
vshampor
approved these changes
Mar 5, 2021
kshpv
pushed a commit
to kshpv/nncf
that referenced
this pull request
Oct 11, 2022
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.
When we use the polynomial scheduler with
"sparsity_target_epoch": 0and"update_per_optimizer_step": truewe get thatsparsity_targetvalue is reached at step 0 of the 1st epoch.This behavior does not correspond to the
sparsity_target_epochparameter description:nncf/nncf/config/schema.py
Lines 513 to 515 in 4189d09
Also, this behavior is different from other schedulers. This PR fixes it.