-
Notifications
You must be signed in to change notification settings - Fork 21.4k
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
[nn] add set_to_none flag for C++ optim endpoint #92989
Conversation
[ghstack-poisoned]
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/92989
Note: Links to docs will display an error until the docs builds have been completed. ✅ No FailuresAs of commit b74ccac: This comment was automatically generated by Dr. CI and updates every 15 minutes. |
ghstack-source-id: 77afd5ad165d689e1919d8d7ab1a1143c5a7d6a6 Pull Request resolved: #92989
[ghstack-poisoned]
ghstack-source-id: ca6e9ad746ce77e2d53f1e97b09371d3280eafd1 Pull Request resolved: #92989
if (p.grad().defined()) { | ||
p.grad().detach_(); | ||
p.grad().zero_(); | ||
if (p.mutable_grad().defined()) { |
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.
why mutable_grad
and not grad
here?
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.
Because grad() comes up with an error when using reset that it is const.
The module.cpp zero_grad equivalent also uses mutable_grad().
@pytorchbot merge |
Merge startedYour change will be merged once all checks pass (ETA 0-4 Hours). Learn more about merging in the wiki. Questions? Feedback? Please reach out to the PyTorch DevX Team |
Stack from ghstack (oldest at bottom):