Skip to content
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

Create torchtnt.utils.lr_scheduler.TLRScheduler #286

Closed
wants to merge 3 commits into from

Conversation

dmtrs
Copy link
Contributor

@dmtrs dmtrs commented Dec 21, 2022

Summary:

Introduce torchtnt.utils.lr_scheduler.TLRScheduler to manage compatibility of torch with expose of LRScheduler pytorch/pytorch#88503

It seems that issue persist still with 1.13.1 (see #285). Replace the get_version logic with try/except. _LRscheduler.

Fixes #285 https://github.com/pytorch/tnt/issues/285

@facebook-github-bot
Copy link
Contributor

Hi @dmtrs!

Thank you for your pull request and welcome to our community.

Action Required

In order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you.

Process

In order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA.

Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with CLA signed. The tagging process may take up to 1 hour after signing. Please give it that time before contacting us about it.

If you have received this in error or have any questions, please contact us at cla@meta.com. Thanks!

@facebook-github-bot
Copy link
Contributor

Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Meta Open Source project. Thanks!

@facebook-github-bot
Copy link
Contributor

Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Meta Open Source project. Thanks!

Copy link
Contributor

@ananthsub ananthsub left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thanks for your contribution @dmtrs !

requirements.txt Outdated Show resolved Hide resolved
@codecov
Copy link

codecov bot commented Dec 22, 2022

Codecov Report

Merging #286 (3796902) into master (98890cd) will decrease coverage by 0.00%.
The diff coverage is 77.77%.

@@            Coverage Diff             @@
##           master     #286      +/-   ##
==========================================
- Coverage   87.90%   87.89%   -0.01%     
==========================================
  Files          87       88       +1     
  Lines        5870     5874       +4     
==========================================
+ Hits         5160     5163       +3     
- Misses        710      711       +1     
Impacted Files Coverage Δ
torchtnt/framework/auto_unit.py 80.79% <ø> (ø)
torchtnt/utils/lr_scheduler.py 66.66% <66.66%> (ø)
tests/framework/test_app_state_mixin.py 100.00% <100.00%> (ø)
torchtnt/framework/unit.py 86.99% <100.00%> (+0.37%) ⬆️
torchtnt/utils/__init__.py 100.00% <100.00%> (ø)

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

@facebook-github-bot
Copy link
Contributor

@ananthsub has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator.

@facebook-github-bot
Copy link
Contributor

@ananthsub has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator.

@dmtrs
Copy link
Contributor Author

dmtrs commented Dec 23, 2022

@ananthsub Commit 0d1067e introduced linting error that is fixed with a separate commit. I am expecting ✅ CI pipeline.

Feel free to merge squash, if required to have clean history.

@facebook-github-bot
Copy link
Contributor

@ananthsub has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator.

@ananthsub
Copy link
Contributor

Thanks for your patience @dmtrs . This is now committed. We will aim to make a new pypi release soon containing this fix

@dmtrs
Copy link
Contributor Author

dmtrs commented Jan 3, 2023

Thanks so much for the support

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Issue with torch 1.13
3 participants