Fix: Adjusted PiecewiseConstantDecay schedule to match training steps on Fashion MNIST #206
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.
Chapter: 11
Cell: Piecewise Constant Scheduling
Issue:
In the PiecewiseConstantDecay example, the original boundaries were set to [50000, 80000], but with 55,000 training images, batch size 32, and 10 epochs, total training steps are only about:
55000 / 32 × 10 ≈ 17,190 steps
The model never reaches the first boundary, and the learning rate never decays.
So,I changed:
boundaries=[50_000, 80_000],to:
boundaries=[6000, 13_000],Hope this PR might be meaningful.
I’ve also opened a few other PRs recently ->
#202
#205