-
Notifications
You must be signed in to change notification settings - Fork 16
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
ValueError: Internal error occurred: b'Intel MKL DFTI ERROR: Inconsistent configuration parameters' for certain shapes in _numpy_fft.rfft #57
Comments
No errors with fft along axis 1 import numpy as np
from mkl_fft._numpy_fft import rfft
X = np.random.randn(1, 18134053)
rfft(X, axis=1)
print(1, 18134052)
X = np.random.randn(16, 18134053)
rfft(X, axis=1)
print(16, 18134052) |
The same error happens for |
Thank you for the report @JesseLivezey. This must be a recently introduced change.
Also, just having created an environment from conda-forge: conda create -n cf_mkl_fft_issue_57 python ipython mkl numpy mkl_fft mkl-service I can not reproduce the issue:
I also can not reproduce the issue using the latest oneMKL version 2020.1, and the development version 2020.2 to be released soon. |
@oleksandr-pavlyk I only get errors when the first dim is the long/fft dimension and the second is >1 X = np.random.randn(18134053, 2) # for me, anything >=2 for the second dim causes an error In your tests, it looks like the second dimension is long, but you're taking the fft over the first. |
Thank you @JesseLivezey I have reproduced the issue. It appears like MKL raises this exception when the dimension is greater than 2^24.
|
I reproduced the internal error using C programming language and reported the issue to MKL team. |
@oleksandr-pavlyk Apologies for reopening this old issue, but was there a resolution to this problem? We think we might be seeing a very similar issue in our code which directly calls the mkl runtime, and it would be good to rule out if it's an error on our end. Is there a link to the issue reporting (if public)? |
@ahnitz Once the issue was originally reported, I changed I have just checked that nightly builds of MKL still flag the input generated from input I would therefore think the problem has not found its resolution as yet. |
I encounter a similar issue when using ifft2d. Is there any progress on this ticket? |
@JesseLivezey @GeJulia @ahnitz I am happy to report that the error has been addressed in MKL 2024.2:
|
@oleksandr-pavlyk thanks for following up! |
For certain large 1d
rfft
s, I get the following error. Tested this in anaconda python 3.7 and 3.8 on linux. If the long/fft axis is 1 instead of 0, I don't get this error.This example generates the error below
This is in a basic conda environment with only
numpy
added.and
Possibly similar to #24.
cc @hlillemark
The text was updated successfully, but these errors were encountered: