Mailman 3 Problem introduced after 1.0rc2 on AIX with xlc - NumPy-Discussion

Problem introduced after 1.0rc2 on AIX with xlc

Brian Granger

21 Oct 2006 21 Oct '06

8:12 a.m.

Hi, i am running numpy on aix compiling with xlc. Revision 1.0rc2 works fine and passes all tests. But 1.0rc3 and more recent give the following on import: Warning: invalid value encountered in multiply Warning: invalid value encountered in multiply Warning: invalid value encountered in multiply Warning: invalid value encountered in add Warning: invalid value encountered in not_equal Warning: invalid value encountered in absolute Warning: invalid value encountered in less Warning: invalid value encountered in multiply Warning: invalid value encountered in multiply Warning: invalid value encountered in equal Warning: invalid value encountered in multiply Warning: invalid value encountered in multiply Warning: invalid value encountered in multiply Warning: invalid value encountered in add Warning: invalid value encountered in not_equal Warning: invalid value encountered in absolute Warning: invalid value encountered in less Warning: invalid value encountered in multiply Warning: invalid value encountered in multiply Warning: invalid value encountered in equal Warning: invalid value encountered in multiply Warning: invalid value encountered in multiply Warning: invalid value encountered in multiply [lots more of this] The odd thing is that all tests pass. I have looked, but can't find where this Warning is coming from in the code. Any thoughts on where this is coming from? What can I do to help debug this? I am not sure what revision introduced this issue. Thanks Brian ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642

Show replies by date

Tim Hochberg

21 Oct 21 Oct

8:40 a.m.

Brian Granger wrote:

...

Hi,

i am running numpy on aix compiling with xlc. Revision 1.0rc2 works fine and passes all tests. But 1.0rc3 and more recent give the following on import:

Warning: invalid value encountered in multiply Warning: invalid value encountered in multiply Warning: invalid value encountered in multiply Warning: invalid value encountered in add Warning: invalid value encountered in not_equal Warning: invalid value encountered in absolute Warning: invalid value encountered in less Warning: invalid value encountered in multiply Warning: invalid value encountered in multiply Warning: invalid value encountered in equal Warning: invalid value encountered in multiply Warning: invalid value encountered in multiply Warning: invalid value encountered in multiply Warning: invalid value encountered in add Warning: invalid value encountered in not_equal Warning: invalid value encountered in absolute Warning: invalid value encountered in less Warning: invalid value encountered in multiply Warning: invalid value encountered in multiply Warning: invalid value encountered in equal Warning: invalid value encountered in multiply Warning: invalid value encountered in multiply Warning: invalid value encountered in multiply [lots more of this]

The odd thing is that all tests pass. I have looked, but can't find where this Warning is coming from in the code. Any thoughts on where this is coming from? What can I do to help debug this? I am not sure what revision introduced this issue.

The reason that you are seeing this now is that the default error state has been tightened up. There were some issues with tests failing as a result of this, but I believe I fixed those already and you're seeing this on import, not when running the tests correct? The first thing to do is figure out where the invalids are occurring, and the natural way to do that is to set the error state to raise, but you can't set the error state till you import it, so that's not going to help here. I think the first thing that I would try is to throw in a seterr(all='raise', under='ignore') right after the call to _setdef in numeric.py. If you're lucky, this will point out where the invalids are popping up. As a sanity check, you could instead make this seterr(all='ignore'), which should make all the warnings go away, but won't tell you anything about why there are warnings to begin with. Regards, -tim ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642

Brian Granger

9:02 a.m.

New subject: Problem introduced after 1.0rc2 on AIX with xlc

Here is the traceback that I got: In [1]: import numpy --------------------------------------------------------------------------- exceptions.FloatingPointError Traceback (most recent call last) /u2/granger/<ipython console> /usr/common/homes/g/granger/usr/local/lib/python/numpy/__init__.py 36 import core 37 from core import * ---> 38 import lib 39 from lib import * 40 import linalg /usr/common/homes/g/granger/usr/local/lib/python/numpy/lib/__init__.py 3 from numpy.version import version as __version__ 4 ----> 5 from type_check import * 6 from index_tricks import * 7 from function_base import * /usr/common/homes/g/granger/usr/local/lib/python/numpy/lib/type_check.py 8 import numpy.core.numeric as _nx 9 from numpy.core.numeric import asarray, array, isnan, obj2sctype, zeros ---> 10 from ufunclike import isneginf, isposinf 11 12 _typecodes_by_elsize = 'GDFgdfQqLlIiHhBb?' /usr/common/homes/g/granger/usr/local/lib/python/numpy/lib/ufunclike.py 44 return y 45 ---> 46 _log2 = umath.log(2) 47 def log2(x, y=None): 48 """Returns the base 2 logarithm of x FloatingPointError: invalid value encountered in log Obviously because I am having the error raised, I only get the first one. Hmmm. Brian On 10/20/06, Tim Hochberg wrote:

...

Brian Granger wrote:

...
Hi,

i am running numpy on aix compiling with xlc. Revision 1.0rc2 works fine and passes all tests. But 1.0rc3 and more recent give the following on import:

Warning: invalid value encountered in multiply Warning: invalid value encountered in multiply Warning: invalid value encountered in multiply Warning: invalid value encountered in add Warning: invalid value encountered in not_equal Warning: invalid value encountered in absolute Warning: invalid value encountered in less Warning: invalid value encountered in multiply Warning: invalid value encountered in multiply Warning: invalid value encountered in equal Warning: invalid value encountered in multiply Warning: invalid value encountered in multiply Warning: invalid value encountered in multiply Warning: invalid value encountered in add Warning: invalid value encountered in not_equal Warning: invalid value encountered in absolute Warning: invalid value encountered in less Warning: invalid value encountered in multiply Warning: invalid value encountered in multiply Warning: invalid value encountered in equal Warning: invalid value encountered in multiply Warning: invalid value encountered in multiply Warning: invalid value encountered in multiply [lots more of this]

The odd thing is that all tests pass. I have looked, but can't find where this Warning is coming from in the code. Any thoughts on where this is coming from? What can I do to help debug this? I am not sure what revision introduced this issue.

The reason that you are seeing this now is that the default error state has been tightened up. There were some issues with tests failing as a result of this, but I believe I fixed those already and you're seeing this on import, not when running the tests correct? The first thing to do is figure out where the invalids are occurring, and the natural way to do that is to set the error state to raise, but you can't set the error state till you import it, so that's not going to help here.

I think the first thing that I would try is to throw in a seterr(all='raise', under='ignore') right after the call to _setdef in numeric.py. If you're lucky, this will point out where the invalids are popping up. As a sanity check, you could instead make this seterr(all='ignore'), which should make all the warnings go away, but won't tell you anything about why there are warnings to begin with.

Regards,

-tim

------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Numpy-discussion mailing list Numpy-discussion@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/numpy-discussion

------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642

Brian Granger

9:13 a.m.

New subject: Problem introduced after 1.0rc2 on AIX with xlc

Also, when I use seterr(all='ignore') the the tests fail: ====================================================================== FAIL: Ticket #112 ---------------------------------------------------------------------- Traceback (most recent call last): File "/usr/common/homes/g/granger/usr/local/lib/python/numpy/core/tests/test_regression.py", line 219, in check_longfloat_repr assert(str(a)[1:9] == str(a[0])[:8]) AssertionError ---------------------------------------------------------------------- Ran 516 tests in 0.823s FAILED (failures=1) Thanks for helping out on this. On 10/20/06, Tim Hochberg wrote:

...

Brian Granger wrote:

...
Hi,

i am running numpy on aix compiling with xlc. Revision 1.0rc2 works fine and passes all tests. But 1.0rc3 and more recent give the following on import:

Warning: invalid value encountered in multiply Warning: invalid value encountered in multiply Warning: invalid value encountered in multiply Warning: invalid value encountered in add Warning: invalid value encountered in not_equal Warning: invalid value encountered in absolute Warning: invalid value encountered in less Warning: invalid value encountered in multiply Warning: invalid value encountered in multiply Warning: invalid value encountered in equal Warning: invalid value encountered in multiply Warning: invalid value encountered in multiply Warning: invalid value encountered in multiply Warning: invalid value encountered in add Warning: invalid value encountered in not_equal Warning: invalid value encountered in absolute Warning: invalid value encountered in less Warning: invalid value encountered in multiply Warning: invalid value encountered in multiply Warning: invalid value encountered in equal Warning: invalid value encountered in multiply Warning: invalid value encountered in multiply Warning: invalid value encountered in multiply [lots more of this]

The odd thing is that all tests pass. I have looked, but can't find where this Warning is coming from in the code. Any thoughts on where this is coming from? What can I do to help debug this? I am not sure what revision introduced this issue.

The reason that you are seeing this now is that the default error state has been tightened up. There were some issues with tests failing as a result of this, but I believe I fixed those already and you're seeing this on import, not when running the tests correct? The first thing to do is figure out where the invalids are occurring, and the natural way to do that is to set the error state to raise, but you can't set the error state till you import it, so that's not going to help here.

I think the first thing that I would try is to throw in a seterr(all='raise', under='ignore') right after the call to _setdef in numeric.py. If you're lucky, this will point out where the invalids are popping up. As a sanity check, you could instead make this seterr(all='ignore'), which should make all the warnings go away, but won't tell you anything about why there are warnings to begin with.

Regards,

-tim

------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Numpy-discussion mailing list Numpy-discussion@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/numpy-discussion

Tim Hochberg

9:25 a.m.

Brian Granger wrote:

...

Also, when I use seterr(all='ignore') the the tests fail:

====================================================================== FAIL: Ticket #112 ---------------------------------------------------------------------- Traceback (most recent call last): File "/usr/common/homes/g/granger/usr/local/lib/python/numpy/core/tests/test_regression.py", line 219, in check_longfloat_repr assert(str(a)[1:9] == str(a[0])[:8]) AssertionError

---------------------------------------------------------------------- Ran 516 tests in 0.823s

FAILED (failures=1)

Thanks for helping out on this.

How recent is your version? I just a problem that was causing this same failure yesterday -- if you checkout is older than that, you may want to get the most recent stuff from SVN and see if that fixes this. -tim ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642

Brian Granger

9:30 a.m.

New subject: Problem introduced after 1.0rc2 on AIX with xlc

I have been doing these recent tests with 1.0rc3. I am building from trunk right now and we will see how that goes. Thanks for your help. Brian On 10/20/06, Tim Hochberg wrote:

...

Brian Granger wrote:

...
Also, when I use seterr(all='ignore') the the tests fail:

====================================================================== FAIL: Ticket #112 ---------------------------------------------------------------------- Traceback (most recent call last): File "/usr/common/homes/g/granger/usr/local/lib/python/numpy/core/tests/test_regression.py", line 219, in check_longfloat_repr assert(str(a)[1:9] == str(a[0])[:8]) AssertionError

---------------------------------------------------------------------- Ran 516 tests in 0.823s

FAILED (failures=1)

Thanks for helping out on this.

How recent is your version? I just a problem that was causing this same failure yesterday -- if you checkout is older than that, you may want to get the most recent stuff from SVN and see if that fixes this.

-tim

------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Numpy-discussion mailing list Numpy-discussion@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/numpy-discussion

Brian Granger

9:43 a.m.

New subject: Problem introduced after 1.0rc2 on AIX with xlc

Tim, I just tried everything with r3375. I set seterr(all='warn') and the tests passed. But all the floating point warning are still there. With seterr(all='ignore') the warnings go away and all the tests pass. should I worry about the warnings? thanks Brian On 10/20/06, Tim Hochberg wrote:

...

Brian Granger wrote:

...
Also, when I use seterr(all='ignore') the the tests fail:

====================================================================== FAIL: Ticket #112 ---------------------------------------------------------------------- Traceback (most recent call last): File "/usr/common/homes/g/granger/usr/local/lib/python/numpy/core/tests/test_regression.py", line 219, in check_longfloat_repr assert(str(a)[1:9] == str(a[0])[:8]) AssertionError

---------------------------------------------------------------------- Ran 516 tests in 0.823s

FAILED (failures=1)

Thanks for helping out on this.

How recent is your version? I just a problem that was causing this same failure yesterday -- if you checkout is older than that, you may want to get the most recent stuff from SVN and see if that fixes this.

-tim

------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Numpy-discussion mailing list Numpy-discussion@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/numpy-discussion

Tim Hochberg

9:51 a.m.

Brian Granger wrote:

...

Tim,

I just tried everything with r3375. I set seterr(all='warn') and the tests passed. But all the floating point warning are still there. With seterr(all='ignore') the warnings go away and all the tests pass. should I worry about the warnings?

Maybe. I just sent you some email on this. But my guess is that the code that checks for FP errors is broken on your particular system. Mainly I suspect this because I think you would have noticed by now if everything was as broken as the warnings seem to indicate. Assuming that's the case, and this will probably become clear if you test a bunch of computations that give correct (and non INF/NAN) results, but still spit out warnings, you have two choices: try to fix the warnings code or disable the warnings. The former would be preferable since then you could actually use the warnings code, but it may be a pain in the neck unless you can find some place to steal the relevant code from. -tim

...

thanks

Brian

On 10/20/06, Tim Hochberg wrote:

...
Brian Granger wrote:

...
Also, when I use seterr(all='ignore') the the tests fail:

====================================================================== FAIL: Ticket #112 ---------------------------------------------------------------------- Traceback (most recent call last): File "/usr/common/homes/g/granger/usr/local/lib/python/numpy/core/tests/test_regression.py", line 219, in check_longfloat_repr assert(str(a)[1:9] == str(a[0])[:8]) AssertionError

---------------------------------------------------------------------- Ran 516 tests in 0.823s

FAILED (failures=1)

Thanks for helping out on this.

How recent is your version? I just a problem that was causing this same failure yesterday -- if you checkout is older than that, you may want to get the most recent stuff from SVN and see if that fixes this.

-tim

------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Numpy-discussion mailing list Numpy-discussion@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/numpy-discussion

------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Numpy-discussion mailing list Numpy-discussion@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/numpy-discussion

Brian Granger

9:19 a.m.

New subject: Problem introduced after 1.0rc2 on AIX with xlc

When I set seterr(all='warn') I see the following: In [1]: import numpy /usr/common/homes/g/granger/usr/local/lib/python/numpy/lib/ufunclike.py:46: RuntimeWarning: invalid value encountered in log _log2 = umath.log(2) /usr/common/homes/g/granger/usr/local/lib/python/numpy/lib/scimath.py:19: RuntimeWarning: invalid value encountered in log _ln2 = nx.log(2.0) /usr/common/homes/g/granger/usr/local/lib/python/numpy/lib/machar.py:64: RuntimeWarning: invalid value encountered in add two = one + one /usr/common/homes/g/granger/usr/local/lib/python/numpy/lib/machar.py:65: RuntimeWarning: invalid value encountered in subtract zero = one - one /usr/common/homes/g/granger/usr/local/lib/python/numpy/lib/machar.py:71: RuntimeWarning: invalid value encountered in add a = a + a /usr/common/homes/g/granger/usr/local/lib/python/numpy/lib/machar.py:72: RuntimeWarning: invalid value encountered in add temp = a + one /usr/common/homes/g/granger/usr/local/lib/python/numpy/lib/machar.py:73: RuntimeWarning: invalid value encountered in subtract temp1 = temp - a /usr/common/homes/g/granger/usr/local/lib/python/numpy/lib/machar.py:74: RuntimeWarning: invalid value encountered in subtract if any(temp1 - one != zero): /usr/common/homes/g/granger/usr/local/lib/python/numpy/lib/machar.py:74: RuntimeWarning: invalid value encountered in not_equal if any(temp1 - one != zero): /usr/common/homes/g/granger/usr/local/lib/python/numpy/lib/machar.py:80: RuntimeWarning: invalid value encountered in add b = b + b /usr/common/homes/g/granger/usr/local/lib/python/numpy/lib/machar.py:81: RuntimeWarning: invalid value encountered in add temp = a + b /usr/common/homes/g/granger/usr/local/lib/python/numpy/lib/machar.py:82: RuntimeWarning: invalid value encountered in subtract itemp = int_conv(temp-a) /usr/common/homes/g/granger/usr/local/lib/python/numpy/lib/machar.py:83: RuntimeWarning: invalid value encountered in not_equal if any(itemp != 0): /usr/common/homes/g/granger/usr/local/lib/python/numpy/lib/machar.py:95: RuntimeWarning: invalid value encountered in multiply b = b * beta /usr/common/homes/g/granger/usr/local/lib/python/numpy/lib/machar.py:96: RuntimeWarning: invalid value encountered in add temp = b + one /usr/common/homes/g/granger/usr/local/lib/python/numpy/lib/machar.py:97: RuntimeWarning: invalid value encountered in subtract temp1 = temp - b /usr/common/homes/g/granger/usr/local/lib/python/numpy/lib/machar.py:98: RuntimeWarning: invalid value encountered in subtract if any(temp1 - one != zero): /usr/common/homes/g/granger/usr/local/lib/python/numpy/lib/machar.py:98: RuntimeWarning: invalid value encountered in not_equal if any(temp1 - one != zero): /usr/common/homes/g/granger/usr/local/lib/python/numpy/lib/machar.py:103: RuntimeWarning: invalid value encountered in divide betah = beta / two /usr/common/homes/g/granger/usr/local/lib/python/numpy/lib/machar.py:106: RuntimeWarning: invalid value encountered in add a = a + a /usr/common/homes/g/granger/usr/local/lib/python/numpy/lib/machar.py:107: RuntimeWarning: invalid value encountered in add temp = a + one /usr/common/homes/g/granger/usr/local/lib/python/numpy/lib/machar.py:108: RuntimeWarning: invalid value encountered in subtract temp1 = temp - a /usr/common/homes/g/granger/usr/local/lib/python/numpy/lib/machar.py:109: RuntimeWarning: invalid value encountered in subtract if any(temp1 - one != zero): /usr/common/homes/g/granger/usr/local/lib/python/numpy/lib/machar.py:109: RuntimeWarning: invalid value encountered in not_equal if any(temp1 - one != zero): /usr/common/homes/g/granger/usr/local/lib/python/numpy/lib/machar.py:113: RuntimeWarning: invalid value encountered in add temp = a + betah /usr/common/homes/g/granger/usr/local/lib/python/numpy/lib/machar.py:115: RuntimeWarning: invalid value encountered in subtract if any(temp-a != zero): /usr/common/homes/g/granger/usr/local/lib/python/numpy/lib/machar.py:115: RuntimeWarning: invalid value encountered in not_equal if any(temp-a != zero): /usr/common/homes/g/granger/usr/local/lib/python/numpy/lib/machar.py:117: RuntimeWarning: invalid value encountered in add tempa = a + beta /usr/common/homes/g/granger/usr/local/lib/python/numpy/lib/machar.py:118: RuntimeWarning: invalid value encountered in add temp = tempa + betah /usr/common/homes/g/granger/usr/local/lib/python/numpy/lib/machar.py:119: RuntimeWarning: invalid value encountered in subtract if irnd==0 and any(temp-tempa != zero): /usr/common/homes/g/granger/usr/local/lib/python/numpy/lib/machar.py:119: RuntimeWarning: invalid value encountered in not_equal if irnd==0 and any(temp-tempa != zero): /usr/common/homes/g/granger/usr/local/lib/python/numpy/lib/machar.py:124: RuntimeWarning: invalid value encountered in divide betain = one / beta /usr/common/homes/g/granger/usr/local/lib/python/numpy/lib/machar.py:127: RuntimeWarning: invalid value encountered in multiply a = a * betain /usr/common/homes/g/granger/usr/local/lib/python/numpy/lib/machar.py:130: RuntimeWarning: invalid value encountered in subtract temp = one - a /usr/common/homes/g/granger/usr/local/lib/python/numpy/lib/machar.py:131: RuntimeWarning: invalid value encountered in subtract if any(temp-one != zero): /usr/common/homes/g/granger/usr/local/lib/python/numpy/lib/machar.py:131: RuntimeWarning: invalid value encountered in not_equal if any(temp-one != zero): /usr/common/homes/g/granger/usr/local/lib/python/numpy/lib/machar.py:133: RuntimeWarning: invalid value encountered in multiply a = a * beta /usr/common/homes/g/granger/usr/local/lib/python/numpy/lib/machar.py:149: RuntimeWarning: invalid value encountered in add temp = one + a /usr/common/homes/g/granger/usr/local/lib/python/numpy/lib/machar.py:150: RuntimeWarning: invalid value encountered in subtract if any(temp-one != zero): /usr/common/homes/g/granger/usr/local/lib/python/numpy/lib/machar.py:150: RuntimeWarning: invalid value encountered in not_equal if any(temp-one != zero): /usr/common/homes/g/granger/usr/local/lib/python/numpy/lib/machar.py:152: RuntimeWarning: invalid value encountered in multiply a = a * beta /usr/common/homes/g/granger/usr/local/lib/python/numpy/lib/machar.py:160: RuntimeWarning: invalid value encountered in add temp = one + eps /usr/common/homes/g/granger/usr/local/lib/python/numpy/lib/machar.py:168: RuntimeWarning: invalid value encountered in add t = one + eps /usr/common/homes/g/granger/usr/local/lib/python/numpy/lib/machar.py:172: RuntimeWarning: invalid value encountered in multiply z = y*y /usr/common/homes/g/granger/usr/local/lib/python/numpy/lib/machar.py:173: RuntimeWarning: invalid value encountered in multiply a = z*one # Check here for underflow /usr/common/homes/g/granger/usr/local/lib/python/numpy/lib/machar.py:174: RuntimeWarning: invalid value encountered in multiply temp = z*t /usr/common/homes/g/granger/usr/local/lib/python/numpy/lib/machar.py:175: RuntimeWarning: invalid value encountered in add if any(a+a == zero) or any(abs(z)>=y): /usr/common/homes/g/granger/usr/local/lib/python/numpy/lib/machar.py:175: RuntimeWarning: invalid value encountered in equal if any(a+a == zero) or any(abs(z)>=y): /usr/common/homes/g/granger/usr/local/lib/python/numpy/lib/machar.py:175: RuntimeWarning: invalid value encountered in absolute if any(a+a == zero) or any(abs(z)>=y): /usr/common/homes/g/granger/usr/local/lib/python/numpy/lib/machar.py:175: RuntimeWarning: invalid value encountered in greater_equal if any(a+a == zero) or any(abs(z)>=y): /usr/common/homes/g/granger/usr/local/lib/python/numpy/lib/machar.py:177: RuntimeWarning: invalid value encountered in multiply temp1 = temp * betain /usr/common/homes/g/granger/usr/local/lib/python/numpy/lib/machar.py:178: RuntimeWarning: invalid value encountered in multiply if any(temp1*beta == z): /usr/common/homes/g/granger/usr/local/lib/python/numpy/lib/machar.py:178: RuntimeWarning: invalid value encountered in equal if any(temp1*beta == z): /usr/common/homes/g/granger/usr/local/lib/python/numpy/lib/machar.py:174: RuntimeWarning: underflow encountered in multiply temp = z*t /usr/common/homes/g/granger/usr/local/lib/python/numpy/lib/machar.py:184: RuntimeWarning: invalid value encountered in not_equal if ibeta != 10: /usr/common/homes/g/granger/usr/local/lib/python/numpy/lib/machar.py:198: RuntimeWarning: invalid value encountered in multiply y = y * betain /usr/common/homes/g/granger/usr/local/lib/python/numpy/lib/machar.py:199: RuntimeWarning: invalid value encountered in multiply a = y * one /usr/common/homes/g/granger/usr/local/lib/python/numpy/lib/machar.py:200: RuntimeWarning: invalid value encountered in multiply temp = y * t /usr/common/homes/g/granger/usr/local/lib/python/numpy/lib/machar.py:201: RuntimeWarning: invalid value encountered in add if any(a+a != zero) and any(abs(y) < xmin): /usr/common/homes/g/granger/usr/local/lib/python/numpy/lib/machar.py:201: RuntimeWarning: invalid value encountered in not_equal if any(a+a != zero) and any(abs(y) < xmin): /usr/common/homes/g/granger/usr/local/lib/python/numpy/lib/machar.py:201: RuntimeWarning: invalid value encountered in absolute if any(a+a != zero) and any(abs(y) < xmin): /usr/common/homes/g/granger/usr/local/lib/python/numpy/lib/machar.py:201: RuntimeWarning: invalid value encountered in less if any(a+a != zero) and any(abs(y) < xmin): /usr/common/homes/g/granger/usr/local/lib/python/numpy/lib/machar.py:203: RuntimeWarning: invalid value encountered in multiply temp1 = temp * betain /usr/common/homes/g/granger/usr/local/lib/python/numpy/lib/machar.py:204: RuntimeWarning: invalid value encountered in multiply if any(temp1*beta == y) and any(temp != y): /usr/common/homes/g/granger/usr/local/lib/python/numpy/lib/machar.py:204: RuntimeWarning: invalid value encountered in equal if any(temp1*beta == y) and any(temp != y): /usr/common/homes/g/granger/usr/local/lib/python/numpy/lib/machar.py:203: RuntimeWarning: underflow encountered in multiply temp1 = temp * betain /usr/common/homes/g/granger/usr/local/lib/python/numpy/lib/machar.py:204: RuntimeWarning: invalid value encountered in not_equal if any(temp1*beta == y) and any(temp != y): /usr/common/homes/g/granger/usr/local/lib/python/numpy/lib/machar.py:215: RuntimeWarning: invalid value encountered in not_equal if mx <= k + k - 3 and ibeta != 10: /usr/common/homes/g/granger/usr/local/lib/python/numpy/lib/machar.py:223: RuntimeWarning: invalid value encountered in equal if ibeta == 2 and not i: /usr/common/homes/g/granger/usr/local/lib/python/numpy/lib/machar.py:227: RuntimeWarning: invalid value encountered in not_equal if any(a != y): /usr/common/homes/g/granger/usr/local/lib/python/numpy/lib/machar.py:229: RuntimeWarning: invalid value encountered in subtract xmax = one - epsneg /usr/common/homes/g/granger/usr/local/lib/python/numpy/lib/machar.py:230: RuntimeWarning: invalid value encountered in multiply if any(xmax*one != xmax): /usr/common/homes/g/granger/usr/local/lib/python/numpy/lib/machar.py:230: RuntimeWarning: invalid value encountered in not_equal if any(xmax*one != xmax): /usr/common/homes/g/granger/usr/local/lib/python/numpy/lib/machar.py:232: RuntimeWarning: invalid value encountered in multiply xmax = xmax / (xmin*beta*beta*beta) /usr/common/homes/g/granger/usr/local/lib/python/numpy/lib/machar.py:232: RuntimeWarning: invalid value encountered in divide xmax = xmax / (xmin*beta*beta*beta) /usr/common/homes/g/granger/usr/local/lib/python/numpy/lib/machar.py:235: RuntimeWarning: invalid value encountered in equal if ibeta==2: /usr/common/homes/g/granger/usr/local/lib/python/numpy/lib/machar.py:236: RuntimeWarning: invalid value encountered in add xmax = xmax + xmax /usr/common/homes/g/granger/usr/local/lib/python/numpy/lib/machar.py:266: RuntimeWarning: invalid value encountered in add ten = two + two + two + two + two /usr/common/homes/g/granger/usr/local/lib/python/numpy/lib/machar.py:267: RuntimeWarning: invalid value encountered in power resolution = ten ** (-self.precision) On 10/20/06, Tim Hochberg wrote:

...

Brian Granger wrote:

...
Hi,

i am running numpy on aix compiling with xlc. Revision 1.0rc2 works fine and passes all tests. But 1.0rc3 and more recent give the following on import:

Warning: invalid value encountered in multiply Warning: invalid value encountered in multiply Warning: invalid value encountered in multiply Warning: invalid value encountered in add Warning: invalid value encountered in not_equal Warning: invalid value encountered in absolute Warning: invalid value encountered in less Warning: invalid value encountered in multiply Warning: invalid value encountered in multiply Warning: invalid value encountered in equal Warning: invalid value encountered in multiply Warning: invalid value encountered in multiply Warning: invalid value encountered in multiply Warning: invalid value encountered in add Warning: invalid value encountered in not_equal Warning: invalid value encountered in absolute Warning: invalid value encountered in less Warning: invalid value encountered in multiply Warning: invalid value encountered in multiply Warning: invalid value encountered in equal Warning: invalid value encountered in multiply Warning: invalid value encountered in multiply Warning: invalid value encountered in multiply [lots more of this]

The odd thing is that all tests pass. I have looked, but can't find where this Warning is coming from in the code. Any thoughts on where this is coming from? What can I do to help debug this? I am not sure what revision introduced this issue.

The reason that you are seeing this now is that the default error state has been tightened up. There were some issues with tests failing as a result of this, but I believe I fixed those already and you're seeing this on import, not when running the tests correct? The first thing to do is figure out where the invalids are occurring, and the natural way to do that is to set the error state to raise, but you can't set the error state till you import it, so that's not going to help here.

I think the first thing that I would try is to throw in a seterr(all='raise', under='ignore') right after the call to _setdef in numeric.py. If you're lucky, this will point out where the invalids are popping up. As a sanity check, you could instead make this seterr(all='ignore'), which should make all the warnings go away, but won't tell you anything about why there are warnings to begin with.

Regards,

-tim

------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Numpy-discussion mailing list Numpy-discussion@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/numpy-discussion

Tim Hochberg

9:43 a.m.

Brian Granger wrote:

...

When I set seterr(all='warn') I see the following:

In [1]: import numpy /usr/common/homes/g/granger/usr/local/lib/python/numpy/lib/ufunclike.py:46: RuntimeWarning: invalid value encountered in log _log2 = umath.log(2) /usr/common/homes/g/granger/usr/local/lib/python/numpy/lib/scimath.py:19: RuntimeWarning: invalid value encountered in log _ln2 = nx.log(2.0)

[etc, etc] Wow! That looks pretty bad. What do you get if you try just "numpy.log(2)" or "numpy.log(2.0)"? Is it producing sane results for scalars at all? I suppose another possibility is that the error reporting is broken on AIX for some reason. Hmmm. I'm betting that is is. The macro UFUNC_CHECK_STATUS is very platform dependent. There is a version from AIX (ufuncobject.h line 301), but perhaps it's broken on your particular configuration and as a result is spitting out all kinds of bogus errors. This is only coming to light now because the default error checking level got cranked up. I gotta call it a night and I'll be out tomorrow, so I won't be much more help, but here's something that you might look into: have you compiled numarray sucessfully? If you haven't you might want to try it. It uses the same default error checking that numpy is now using. If you have, you might want to look for the equivalent of UFUNC_CHECK_STATUS (it might even have the same name) and splice it into numpy and see if it fixes your problems. Of course, if numpy.log(2) is spitting out something bogus, there's something much worse going on, but I suspect you would have noticed that by now. Good luck, -tim ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642

Brian Granger

10:31 a.m.

New subject: Problem introduced after 1.0rc2 on AIX with xlc

Thanks, I will investigate more on these things and get back to you early in the week. But for now numpy seems to be functioning pretty normally (log(2) gives the correct answer). thanks again. It would be great to figure this stuff out before 1.0, but we might not have time. Brian On 10/20/06, Tim Hochberg wrote:

...

Brian Granger wrote:

...
When I set seterr(all='warn') I see the following:

In [1]: import numpy /usr/common/homes/g/granger/usr/local/lib/python/numpy/lib/ufunclike.py:46: RuntimeWarning: invalid value encountered in log _log2 = umath.log(2) /usr/common/homes/g/granger/usr/local/lib/python/numpy/lib/scimath.py:19: RuntimeWarning: invalid value encountered in log _ln2 = nx.log(2.0)

[etc, etc]

Wow! That looks pretty bad. What do you get if you try just "numpy.log(2)" or "numpy.log(2.0)"? Is it producing sane results for scalars at all? I suppose another possibility is that the error reporting is broken on AIX for some reason.

Hmmm.

I'm betting that is is. The macro UFUNC_CHECK_STATUS is very platform dependent. There is a version from AIX (ufuncobject.h line 301), but perhaps it's broken on your particular configuration and as a result is spitting out all kinds of bogus errors. This is only coming to light now because the default error checking level got cranked up.

I gotta call it a night and I'll be out tomorrow, so I won't be much more help, but here's something that you might look into: have you compiled numarray sucessfully? If you haven't you might want to try it. It uses the same default error checking that numpy is now using. If you have, you might want to look for the equivalent of UFUNC_CHECK_STATUS (it might even have the same name) and splice it into numpy and see if it fixes your problems.

Of course, if numpy.log(2) is spitting out something bogus, there's something much worse going on, but I suspect you would have noticed that by now.

Good luck,

-tim

------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Numpy-discussion mailing list Numpy-discussion@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/numpy-discussion

Travis Oliphant

11:37 a.m.

Brian Granger wrote:

...

Hi,

i am running numpy on aix compiling with xlc. Revision 1.0rc2 works fine and passes all tests. But 1.0rc3 and more recent give the following on import:

Most likely the error-detection code is not working on your platform. The platform dependent stuff is not that difficult. I tried to implement something for AIX, but very likely got it wrong (and don't have a platform to test it on). It is the UFUNC_CHECK_STATUS that must be implemented. Perhaps, we can do a simple check and disable the error modes: seterr(all='ignore') will work and "turn-off" error-detection on your platform. -Travis ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642

Brian Granger

23 Oct 23 Oct

3:07 a.m.

New subject: Problem introduced after 1.0rc2 on AIX with xlc

...

Most likely the error-detection code is not working on your platform. The platform dependent stuff is not that difficult. I tried to implement something for AIX, but very likely got it wrong (and don't have a platform to test it on). It is the UFUNC_CHECK_STATUS that must be implemented. Perhaps, we can do a simple check and disable the error modes:

I looked at the UFUNC_CHECK_STATUS implementation for AIX and put in some print statements. The the fpstatus returned to fp_read_flag is always indicating an FP_INVALID so UFUNC_CHECK_STATUS return 8. But the code looks fine to me. It seems a little odd that it would always indicate this flag. Where else can I look to try to see what it goiing on? Do you think this is worth worrying about, or should we just have use seterr(all='ignore')? I am willing to try to hunt this down, but I don't know much about the internals of numpy. Thanks Brian

...

seterr(all='ignore')

will work and "turn-off" error-detection on your platform.

-Travis

------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Numpy-discussion mailing list Numpy-discussion@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/numpy-discussion

Brian Granger

3:49 a.m.

New subject: Problem introduced after 1.0rc2 on AIX with xlc

So, I have figured out the problem and have a solution. I have submitted a ticket for this: http://projects.scipy.org/scipy/numpy/ticket/362 That describes the problem and solution. Thanks for everyones ideas on this. Brian On 10/21/06, Travis Oliphant wrote:

...

Brian Granger wrote:

...
Hi,

i am running numpy on aix compiling with xlc. Revision 1.0rc2 works fine and passes all tests. But 1.0rc3 and more recent give the following on import:

Most likely the error-detection code is not working on your platform. The platform dependent stuff is not that difficult. I tried to implement something for AIX, but very likely got it wrong (and don't have a platform to test it on). It is the UFUNC_CHECK_STATUS that must be implemented. Perhaps, we can do a simple check and disable the error modes:

seterr(all='ignore')

will work and "turn-off" error-detection on your platform.

-Travis

------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Numpy-discussion mailing list Numpy-discussion@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/numpy-discussion

6389

Age (days ago)

6390

Last active (days ago)

List overview

Download

13 comments

3 participants

participants (3)

Brian Granger
Tim Hochberg
Travis Oliphant

Problem introduced after 1.0rc2 on AIX with xlc

tags

participants (3)