-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
** On entry to DLASCL parameter number 4 had an illegal value Crashes Python #3596
Comments
There is a nan or inf in the matrix being inverted. |
Thanks Kevin
Damn data wrangling. The dumping out of python is a bit of a harsh error!
Cheers,
Berowne
… On 6 Apr 2017, at 9:30 pm, Kevin Sheppard ***@***.***> wrote:
There is a nan or inf in the matrix being inverted.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
This crash is a feature of Intel's MKL, not Python/statsmdodels/numpy. Best would be to check for nan/inf in sm and raise with a nice error message. |
Closing since fixed as far as it can since mostly a MKL issue. |
I can reproduce this error as well! But my fist notice of a similar error came from sklearn PLSRegression model fit. It raises a problem with linalg svd decomposition but only for the first time it is run. If I run the same cell for a second time it will work, Any clues from where this problem might come in your case with the ARIMA model? Cheers |
@dario-passos Are you using Windows by chance? If you are:
then you might be experiencing numpy/numpy#16744 |
@bashtage , yes, I'm on a Windows 10 (version 2004) PC and I have my numpy installed through pip! |
This OpenBLAS bug is definitely a nasty one that will be catching a lot out until fixed. |
G'day.
I'm trying to test the VAR model on multivariate TS.
http://statsmodels.sourceforge.net/devel/vector_ar.html#granger-causality
from statsmodels.tsa.vector_ar.var_model import VAR
when I run
results=model.fit(2)
I get the error
** On entry to DLASCL parameter number 4 had an illegal value
The text was updated successfully, but these errors were encountered: