-
Notifications
You must be signed in to change notification settings - Fork 3.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support torch.optim.lr_scheduler.ReduceLROnPlateau #320
Merged
williamFalcon
merged 18 commits into
Lightning-AI:master
from
vikmary:support-reduceonplateau-lr-scheduler
Dec 3, 2019
Merged
Changes from all commits
Commits
Show all changes
18 commits
Select commit
Hold shift + click to select a range
1a173d8
feat: add reducelronplateau callback
vikmary acb30c0
feat: use reducelronplateau callback in trainer
vikmary 6827262
feat: only on unsupported lr schedulers
vikmary b6f827b
feat: merge origin
vikmary fa4094e
feat: merge master origin (second try)
vikmary d232a7c
feat: last but not the least merge of master
vikmary 94a285d
Merge branch 'master' into support-reduceonplateau-lr-scheduler
vikmary 26844ac
feat: merge master
vikmary cae83ca
feat: support only on scheduler in reduceLrOnPlateauScheduler
vikmary 29c5480
feat: merge origin
vikmary cd946a3
feat: merge origin & refactor
vikmary 78b975b
refactor: code style
vikmary 4f5ae52
Merge branch 'master' into support-reduceonplateau-lr-scheduler
williamFalcon c9d5618
Update pt_callbacks.py
williamFalcon 75faae5
Update trainer.py
williamFalcon 5465466
Update train_loop_mixin.py
williamFalcon d16a6c0
Update trainer.py
williamFalcon 7650fa4
Update train_loop_mixin.py
williamFalcon File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this seems very specific. does it only need to work with val_loss?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it could be any validation metric in theory, but how do we let the user pass it in? Perhaps via a dedicated dict entry in the validation_end output similar to "log" and "progress_bar"? It's one more thing the user needs to remember, but maybe its fine since this lr_scheduler is optional and it should be mentioned in the docs.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yeah, good option. let’s do it in a separate PR?