Implemented feature - #511
Open
PragyaPandey5 wants to merge 2 commits into
Open
Conversation
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #511 +/- ##
===========================================
- Coverage 100.00% 99.99% -0.01%
===========================================
Files 127 127
Lines 12309 12319 +10
===========================================
+ Hits 12309 12318 +9
- Misses 0 1 +1
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
kozistr
reviewed
Jul 15, 2026
kozistr
left a comment
Owner
There was a problem hiding this comment.
Hi! thanks for the PR!
Overall, looks good to me! Could you fix the lint issue and test coverage?
This file contains hidden or 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
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.
Problem (Why?)
The project did not include an exponential learning rate scheduler with linear warmup. Adding this scheduler provides users with another learning rate scheduling strategy for training PyTorch models.
_What problem are you trying to solve?
Added an ExponentialScheduler with linear warmup to provide an additional learning rate scheduling option for PyTorch models.
Solution (What/How?) - - Added an example demonstrating how to use the learning rate scheduler.
ExponentialSchedulerwith linear warmup.gammaparameter.lr_schedulerpackage.How did you solve the problem? Please provide a complete description and explanation!
Implemented a new
ExponentialSchedulerwith linear warmup by extending the existing scheduler framework. Added validation for thegammaparameter, registered the scheduler in thelr_schedulerpackage, created an example demonstrating its usage, and added unit tests to verify its functionality. Finally, ran the test suite to ensure the new scheduler integrates correctly with the existing codebase.Other changes (bug fixes, small refactors) - no additional changes
_Are there any small changes? yes
Notes None.
Please note any questions, helps or contexts what maintainer(s) should know
Checklist
make formatbefore commitmake checkshows no errors)make testOn branch main
Your branch is up to date with 'origin/main'.
nothing to commit, working tree clean