-
Notifications
You must be signed in to change notification settings - Fork 25.6k
Fix mistakes and increase clarity of norm documentation #42696
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
Conversation
💊 CI failures summary and remediationsAs of commit 210dd6d (more details on the Dr. CI page): 💚 💚 Looks good so far! There are no failures yet. 💚 💚 1 failure confirmed as flaky and can be ignored:
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 on the GitHub issue tracker or post in the (internal) Dr. CI Users group. This comment has been revised 27 times. |
@WANGZhaowei-Wesley could you help take a look at this fix? Thanks! |
This might be nice to have merged before the next release. Although, we now have a warning on |
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.
@ezyang has imported this pull request. If you are a Facebook employee, you can view this diff on Phabricator.
Codecov Report
@@ Coverage Diff @@
## master #42696 +/- ##
==========================================
- Coverage 68.19% 68.19% -0.01%
==========================================
Files 410 410
Lines 53403 53403
==========================================
- Hits 36418 36417 -1
- Misses 16985 16986 +1
Continue to review full report at Codecov.
|
@kurtamohler It looks like this was never merged and #41388 never closed. Is this still relevant? Should I take a look for you? |
@mruberry, thanks for asking, yes I think this is still relevant since |
@mruberry, maybe hold off on reviewing for a bit. I want to see if I can fix some of the confusing points brought up here: #44796 (comment) |
Sounds great. We'll wait for your update. |
fc73637
to
95bfb7f
Compare
@mruberry, OK I think this is a bit better, ready for review. |
95bfb7f
to
8e5dd3b
Compare
72e2a5f
to
144b9ff
Compare
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 I finally understand what torch.norm does. Thanks @kurtamohler. Just ping me when the test(s) are move to test_linalg.py.
Haha yes, me too, even though I've been working with it for a couple months now. |
144b9ff
to
c1d6a7a
Compare
@mruberry , I've moved the tests, should be good to go now. |
c1d6a7a
to
df284d9
Compare
df284d9
to
210dd6d
Compare
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.
@mruberry has imported this pull request. If you are a Facebook employee, you can view this diff on Phabricator.
p
,ord
, and input size.test/test_torch.py
totest/test_linalg.py
p='fro'
andp=2
give same results for mutually valid inputsFixes #41388