Hi, I've just tested the latest numpy with my new configuration (Opteron 2220, 64bits with RH5.2, compiled with ICC 10.1.018) and I got this failure. ====================================================================== FAIL: test_umath.TestLogAddExp2.test_logaddexp2_values [...] assert_almost_equal(np.logaddexp2(xf, yf), zf, decimal=dec) [...] raise AssertionError(msg) AssertionError: Arrays are not almost equal (mismatch 80.0%) x: array([ 2.32090838, 2.00127574, 2.5849625 , 2.00127574, 2.32090838]) y: array([ 2.5849625, 2.5849625, 2.5849625, 2.5849625, 2.5849625]) Is it fixed in the current trunk? Matthieu -- Information System Engineer, Ph.D. Website: http://matthieu-brucher.developpez.com/ Blogs: http://matt.eifelle.com and http://blog.developpez.com/?blog=92 LinkedIn: http://www.linkedin.com/in/matthieubrucher
On Wed, May 27, 2009 at 7:51 AM, Matthieu Brucher < matthieu.brucher@gmail.com> wrote:
Hi,
I've just tested the latest numpy with my new configuration (Opteron 2220, 64bits with RH5.2, compiled with ICC 10.1.018) and I got this failure.
====================================================================== FAIL: test_umath.TestLogAddExp2.test_logaddexp2_values [...] assert_almost_equal(np.logaddexp2(xf, yf), zf, decimal=dec) [...] raise AssertionError(msg) AssertionError: Arrays are not almost equal
(mismatch 80.0%) x: array([ 2.32090838, 2.00127574, 2.5849625 , 2.00127574, 2.32090838]) y: array([ 2.5849625, 2.5849625, 2.5849625, 2.5849625, 2.5849625])
Is it fixed in the current trunk?
This is the first report. I'll guess it is related to icc. What happens if you use gcc? Chuck
This is the first report. I'll guess it is related to icc. What happens if you use gcc?
Indeed, with gcc4.1, the error isn't there. Matthieu -- Information System Engineer, Ph.D. Website: http://matthieu-brucher.developpez.com/ Blogs: http://matt.eifelle.com and http://blog.developpez.com/?blog=92 LinkedIn: http://www.linkedin.com/in/matthieubrucher
participants (2)
-
Charles R Harris
-
Matthieu Brucher