-
Notifications
You must be signed in to change notification settings - Fork 33
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
torch.minimum
and torch.copysign
don't accept scalars for one argument
#271
Comments
Would be great to report these to pytorch itself. Meanwhile we'll need a workaround in |
Maybe once we figure out the extent of the problem (e.g. other functions beyond Or I've suggested before that we can probably work out a more streamlined reporting mechanism than to file the same issue in multiple places, customized for each affected backend. It might help if we can just ping someone from the libraries in these sorts of issues, and they can just add a link in a tracking issue in their project or something. Do you know anyone on the Torch side who is interested in array API compatibility who we might ping here? |
cross-ref #272 and data-apis/array-api-tests#348 The bottom line seems to be that that in torch accepting scalars is more of an exception than a rule. |
Testing shows 16 missing kernels, all xfailed for now: https://github.com/data-apis/array-api-compat/blob/1.11.2/torch-xfails.txt#L139 |
Per the 2024.12 standard, these should work, but don't:
Looks like
maximum
also has trouble. Haven't checked the rest of the functions that now accept scalars, but I assume others may have trouble.The text was updated successfully, but these errors were encountered: