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
Beef up {jacobian, hessian} vectorize docs; eliminate a warning #51638
Conversation
This PR makes the following doc changes: - Makes it clear to users that they should use vectorize "at their own risk" - Makes it clear that vectorize uses the "experimental prototype vmap" so that when users see error messages related to vmap they will know where it is coming from. This PR also: - makes it so that {jacobian, hessian} call a version of vmap that doesn't warn the user that they are using an "experimental prototype". The regular torch.vmap API does warn the user about this. This is to improve a UX a little because the user already knows from discovering the flag and reading the docs what they are getting themselves into. Test Plan: - Add test that {jacobian, hessian} with vectorize=True don't raise warnings [ghstack-poisoned]
💊 CI failures summary and remediationsAs of commit 0cb72ed (more details on the Dr. CI page):
This comment was automatically generated by Dr. CI (expand for details).Follow this link to opt-out of these comments for your Pull Requests.Please report bugs/suggestions to the (internal) Dr. CI Users group. |
This PR makes the following doc changes: - Makes it clear to users that they should use vectorize "at their own risk" - Makes it clear that vectorize uses the "experimental prototype vmap" so that when users see error messages related to vmap they will know where it is coming from. This PR also: - makes it so that {jacobian, hessian} call a version of vmap that doesn't warn the user that they are using an "experimental prototype". The regular torch.vmap API does warn the user about this. This is to improve a UX a little because the user already knows from discovering the flag and reading the docs what they are getting themselves into. Test Plan: - Add test that {jacobian, hessian} with vectorize=True don't raise warnings ghstack-source-id: 51cc04dbc16c2cf45f0ee403ccaa44bc08081f70 Pull Request resolved: #51638
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.
LGTM!
Thanks for the update!
The new phrasing will help reduce confusion for sure!
Codecov Report
@@ Coverage Diff @@
## gh/zou3519/347/base #51638 +/- ##
=======================================================
- Coverage 80.87% 80.87% -0.01%
=======================================================
Files 1943 1943
Lines 211692 211694 +2
=======================================================
- Hits 171208 171199 -9
- Misses 40484 40495 +11 |
Stack from ghstack:
This PR makes the following doc changes:
risk"
so that when users see error messages related to vmap they will know
where it is coming from.
This PR also:
doesn't warn the user that they are using an "experimental prototype".
The regular torch.vmap API does warn the user about this. This is to
improve a UX a little because the user already knows from discovering
the flag and reading the docs what they are getting themselves into.
Test Plan:
warnings
Differential Revision: D26225402