-
Notifications
You must be signed in to change notification settings - Fork 29
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
Add fft support for numpy and cupy #78
Conversation
This is based off of numpy/numpy#25317
Need to re-run the tests here, but NumPy 2.0 shouldn't require any wrapping for fft. For NumPy 1.26, the only wrapping that should be needed is to avoid upcasting 32-bit dtypes. CuPy doesn't have that bug, so presumably no wrapping will be needed there (although I haven't run the tests yet so they may have other issues). |
Confirmed numpy |
CuPy 13.0.0 also passes all fft tests (although annoyingly you have to use |
It's |
It means you can't run the test suite against cupy:
you have to go through the compat layer instead ( (note that the standard uses |
With that being said, I feel like this is something that we fixed previously. Is this a regression @honno? |
Ah OK, but CuPy main namespace is not array-api compliant yet. When CuPy becomes fully NumPy 2.0 compatible we should get the fix for free (cc: @kmaehashi). |
I think we did do some work to make testing the top-level Maybe we could special case things like this in the test suite, but if there's momentum for CuPy to have a |
The only thing that needs to be wrapped is a few functions which do not properly map axes to dim.
The latest version of numpy also has this problem:
|
CuPy test failures:
|
CC @leofang
and a similar issue exists for |
Actually the |
|
This is based off of numpy/numpy#25317
Still need to