Skip to content
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

WARN: possible windows x64 issue with older numpy MKL #3434

Closed
jreback opened this issue Apr 23, 2013 · 7 comments
Closed

WARN: possible windows x64 issue with older numpy MKL #3434

jreback opened this issue Apr 23, 2013 · 7 comments
Labels
Build Library building on various platforms

Comments

@jreback
Copy link
Contributor

jreback commented Apr 23, 2013

I happened to have an older verion of numpy 1.6.2 MKL installed on a windows machines

very intermittently (I think you hae to be using a really big frame)
sometimes I got a:

OMP : Error # 134 Cannot set thread affinity mask

which I think is caused by numexpr operations

see this

http://software.intel.com/en-us/forums/topic/279406

I am not sure its a real problem, because it only affects some versions of MKL, upgrading numpy (or even using a newer version of 1.6.2) seems to fix it..

also can be programatically disabled by

pandas.core.expressions.set_use_numexpr(False)

just a FYI

@davidljung
Copy link
Contributor

I'm seeing the same error using Pandas 0.13.1 with Numpy 1.8.0 in Windows 7. It also occurs with expressions such as:
df = df.loc[(df['timediff'] > -20) & (df['timediff'] < 20),:]
and
df['GP'] = (df['Price'] - df['Cost'] - (df['Discount'] / df['Qty'])) * df['Qty']

They pop-up and empty shell window titles pythonw.exe and the error text given is:

OMP: Error #134: Cannot set thread affinity mask.
OMP: System error #87: The parameter is incorrect.

Unfortunately, there is no expressions module in pandas.core in this version, so I haven't figured out how to work around it yet.

(I think I'll open a new bug report, since this indicates an older issue and a build problem, which it may not be)

@jreback
Copy link
Contributor Author

jreback commented Mar 27, 2014

pls show the frame exactly as constructed. it appears you are trying to compare timedeltas with integers which is not implemented exactly right ATM IIRC.

I think the expression is passed to numexpr which is an open bug (it shouldn't be ), and instead evaluated directly (which does work)

@jreback
Copy link
Contributor Author

jreback commented Mar 27, 2014

I don't recall if timedelta ops were fixed in this or not #4924

@davidljung
Copy link
Contributor

pd.computation.expressions.set_use_numexpr(False)

Does avoid the issue.
The timediff column is float64 type. I tried it with > -20.0 and < 20.0 and the error still occurs.

@jreback
Copy link
Contributor Author

jreback commented Mar 27, 2014

pls show how you constructed this frame

@JohnNapier
Copy link

Please find here (#9328) code to reproduce this issue.

@jreback
Copy link
Contributor Author

jreback commented Mar 26, 2018

closing as non-supported numpy version

@jreback jreback closed this as completed Mar 26, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Build Library building on various platforms
Projects
None yet
Development

No branches or pull requests

3 participants