-
Notifications
You must be signed in to change notification settings - Fork 24.3k
Derivative for aten::linalg_pinv is not implemented #66618
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
Comments
Is this actually a regression? |
Do we not have sample inputs covering the tensor rcond case? |
No, and I totally missed this signature. Looks like not that much of a common use case to pass tensor rcond or any rcond for that matter. |
If it's not in our tests it doesn't mean there's no use case for it.
Here's a use case for differentiable rcond: |
I think that solving a regularized problem like that is very confusing. Besides, |
The problem will be fixed with #63102, I also included missing sample inputs there. |
Summary: This pull request introduces new keyword arguments for `torch.linalg.matrix_rank` and `torch.linalg.pinv`: `atol` and `rtol`. Currently, only tensor overload has default values for either `atol` or `rtol`, the float overload requires both arguments to be specified. FC compatibility: #63102 (comment) Fixes #54151. Fixes #66618. cc jianyuh nikitaved pearu mruberry walterddr IvanYashchuk xwang233 Lezcano Pull Request resolved: #63102 Reviewed By: H-Huang Differential Revision: D31641456 Pulled By: mruberry fbshipit-source-id: 4c765508ab1657730703e42975fc8c0d0a60eb7c
Uh oh!
There was an error while loading. Please reload this page.
🐛 Bug
This PR #66092 added an explicit derivative rule for the following signature:
but there is also an overload that accepts
rcond
argument of type Tensor. Differentiation withTensor rcond
is broken currently and was working before #66092.To Reproduce
Steps to reproduce the behavior:
Expected behavior
It should work as it did before #66092.
cc @ezyang @albanD @zou3519 @gqchen @pearu @nikitaved @soulitzer @lezcano @Varal7 @jianyuh @mruberry @walterddr @IvanYashchuk @xwang233
The text was updated successfully, but these errors were encountered: