Re: [Numpy-discussion] Problem introduced after 1.0rc2 on AIX with xlc

2006-10-22 Thread Brian Granger
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 [EMAIL PROTECTED] 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=lnkkid=120709bid=263057dat=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=lnkkid=120709bid=263057dat=121642
___
Numpy-discussion mailing list
Numpy-discussion@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/numpy-discussion


Re: [Numpy-discussion] Problem introduced after 1.0rc2 on AIX with xlc

2006-10-21 Thread Travis Oliphant
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=lnkkid=120709bid=263057dat=121642
___
Numpy-discussion mailing list
Numpy-discussion@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/numpy-discussion


[Numpy-discussion] Problem introduced after 1.0rc2 on AIX with xlc

2006-10-20 Thread Brian Granger
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=lnkkid=120709bid=263057dat=121642
___
Numpy-discussion mailing list
Numpy-discussion@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/numpy-discussion


Re: [Numpy-discussion] Problem introduced after 1.0rc2 on AIX with xlc

2006-10-20 Thread Tim Hochberg
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=lnkkid=120709bid=263057dat=121642
___
Numpy-discussion mailing list
Numpy-discussion@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/numpy-discussion


Re: [Numpy-discussion] Problem introduced after 1.0rc2 on AIX with xlc

2006-10-20 Thread Brian Granger
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 [EMAIL PROTECTED] 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=lnkkid=120709bid=263057dat=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=lnkkid=120709bid=263057dat=121642
___
Numpy-discussion mailing list
Numpy-discussion@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/numpy-discussion


Re: [Numpy-discussion] Problem introduced after 1.0rc2 on AIX with xlc

2006-10-20 Thread Brian Granger
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

Re: [Numpy-discussion] Problem introduced after 1.0rc2 on AIX with xlc

2006-10-20 Thread Tim Hochberg
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=lnkkid=120709bid=263057dat=121642
___
Numpy-discussion mailing list
Numpy-discussion@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/numpy-discussion


Re: [Numpy-discussion] Problem introduced after 1.0rc2 on AIX with xlc

2006-10-20 Thread Brian Granger
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 [EMAIL PROTECTED] 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=lnkkid=120709bid=263057dat=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=lnkkid=120709bid=263057dat=121642
___
Numpy-discussion mailing list
Numpy-discussion@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/numpy-discussion


Re: [Numpy-discussion] Problem introduced after 1.0rc2 on AIX with xlc

2006-10-20 Thread Tim Hochberg
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=lnkkid=120709bid=263057dat=121642
___
Numpy-discussion mailing list
Numpy-discussion@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/numpy-discussion


Re: [Numpy-discussion] Problem introduced after 1.0rc2 on AIX with xlc

2006-10-20 Thread Tim Hochberg
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 [EMAIL PROTECTED] 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=lnkkid=120709bid=263057dat=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=lnkkid=120709bid=263057dat=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=lnkkid=120709bid=263057dat=121642
___
Numpy-discussion mailing list
Numpy-discussion@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/numpy-discussion


Re: [Numpy-discussion] Problem introduced after 1.0rc2 on AIX with xlc

2006-10-20 Thread Brian Granger
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 [EMAIL PROTECTED] 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=lnkkid=120709bid=263057dat=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=lnkkid=120709bid=263057dat=121642
___
Numpy-discussion mailing list
Numpy-discussion@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/numpy-discussion