You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Would be nice if a simple dask interface were provided to mkl_fft (much like the numpy one currently). In fact it could be built right on top of the _numpy_fft module by wrapping these functions using fft_wrap just as it is done in Dask except using the one's in _numpy_fft instead.
The text was updated successfully, but these errors were encountered:
Thanks for the follow up. Glad to hear this works.
I am not clear as to what exactly should be done in _numpy_fft.
Don’t think anything has to be done to _numpy_fft. That just works well for this purpose. Namely fft_wrap works well with FFT functions adhering to the NumPy API.
Are you proposing to add _dask_fft.py to the package, which would export these fft_wrapped function if dask is found in the environment?
Yep, exactly.
Any thoughts on how we name things in the public API? Also any thoughts on what would be adequate testing?
Would be nice if a simple
dask
interface were provided tomkl_fft
(much like thenumpy
one currently). In fact it could be built right on top of the_numpy_fft
module by wrapping these functions usingfft_wrap
just as it is done in Dask except using the one's in_numpy_fft
instead.The text was updated successfully, but these errors were encountered: