[Numpy-discussion] Numpy v1.3.0b1 on Linux w/ Intel compilers - unknown file type

Fri Mar 27 08:42:45 EDT 2009

Error messages? Sure;-) 

python -c 'import numpy; numpy.test()' 
Running unit tests for numpy 
NumPy version 1.3.0b1 
NumPy is installed in /opt/apps/lib/python2.5/site-packages/numpy 
Python version 2.5.2 (r252:60911, Aug 31 2008, 15:16:34) [GCC Intel(R) C++ gcc 4.2 mode] 
nose version 0.10.4 
.......................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................K.........................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................FF..............FF.......................................................................................................................................................................................................................................................................................................................................................................... 
====================================================================== 
FAIL: test_cdouble (test_linalg.TestEigh) 
---------------------------------------------------------------------- 
Traceback (most recent call last): 
File "/opt/apps/lib/python2.5/site-packages/numpy/linalg/tests/test_linalg.py", line 221, in test_cdouble 
self.do(a) 
File "/opt/apps/lib/python2.5/site-packages/numpy/linalg/tests/test_linalg.py", line 259, in do 
assert_almost_equal(ev, evalues) 
File "/opt/apps/lib/python2.5/site-packages/numpy/linalg/tests/test_linalg.py", line 23, in assert_almost_equal 
old_assert_almost_equal(a, b, decimal=decimal, **kw) 
File "/opt/apps/lib/python2.5/site-packages/numpy/testing/utils.py", line 215, in assert_almost_equal 
return assert_array_almost_equal(actual, desired, decimal, err_msg) 
File "/opt/apps/lib/python2.5/site-packages/numpy/testing/utils.py", line 321, in assert_array_almost_equal 
header='Arrays are not almost equal') 
File "/opt/apps/lib/python2.5/site-packages/numpy/testing/utils.py", line 302, in assert_array_compare 
raise AssertionError(msg) 
AssertionError: 
Arrays are not almost equal 

(mismatch 100.0%) 
x: array([ 4.60555128, -2.60555128]) 
y: array([-2.60555128 +1.11022302e-16j, 4.60555128 -1.11022302e-16j]) 

====================================================================== 
FAIL: test_csingle (test_linalg.TestEigh) 
---------------------------------------------------------------------- 
Traceback (most recent call last): 
File "/opt/apps/lib/python2.5/site-packages/numpy/linalg/tests/test_linalg.py", line 217, in test_csingle 
self.do(a) 
File "/opt/apps/lib/python2.5/site-packages/numpy/linalg/tests/test_linalg.py", line 259, in do 
assert_almost_equal(ev, evalues) 
File "/opt/apps/lib/python2.5/site-packages/numpy/linalg/tests/test_linalg.py", line 23, in assert_almost_equal 
old_assert_almost_equal(a, b, decimal=decimal, **kw) 
File "/opt/apps/lib/python2.5/site-packages/numpy/testing/utils.py", line 215, in assert_almost_equal 
return assert_array_almost_equal(actual, desired, decimal, err_msg) 
File "/opt/apps/lib/python2.5/site-packages/numpy/testing/utils.py", line 321, in assert_array_almost_equal 
header='Arrays are not almost equal') 
File "/opt/apps/lib/python2.5/site-packages/numpy/testing/utils.py", line 302, in assert_array_compare 
raise AssertionError(msg) 
AssertionError: 
Arrays are not almost equal 

(mismatch 100.0%) 
x: array([ 4.60555124, -2.60555124], dtype=float32) 
y: array([-2.60555124 +1.11022302e-16j, 4.60555124 -1.11022302e-16j], dtype=complex64) 

====================================================================== 
FAIL: test_cdouble (test_linalg.TestEigvalsh) 
---------------------------------------------------------------------- 
Traceback (most recent call last): 
File "/opt/apps/lib/python2.5/site-packages/numpy/linalg/tests/test_linalg.py", line 221, in test_cdouble 
self.do(a) 
File "/opt/apps/lib/python2.5/site-packages/numpy/linalg/tests/test_linalg.py", line 249, in do 
assert_almost_equal(ev, evalues) 
File "/opt/apps/lib/python2.5/site-packages/numpy/linalg/tests/test_linalg.py", line 23, in assert_almost_equal 
old_assert_almost_equal(a, b, decimal=decimal, **kw) 
File "/opt/apps/lib/python2.5/site-packages/numpy/testing/utils.py", line 215, in assert_almost_equal 
return assert_array_almost_equal(actual, desired, decimal, err_msg) 
File "/opt/apps/lib/python2.5/site-packages/numpy/testing/utils.py", line 321, in assert_array_almost_equal 
header='Arrays are not almost equal') 
File "/opt/apps/lib/python2.5/site-packages/numpy/testing/utils.py", line 302, in assert_array_compare 
raise AssertionError(msg) 
AssertionError: 
Arrays are not almost equal 

(mismatch 100.0%) 
x: array([ 4.60555128+0.j, -2.60555128+0.j]) 
y: array([-2.60555128 +1.11022302e-16j, 4.60555128 -1.11022302e-16j]) 

====================================================================== 
FAIL: test_csingle (test_linalg.TestEigvalsh) 
---------------------------------------------------------------------- 
Traceback (most recent call last): 
File "/opt/apps/lib/python2.5/site-packages/numpy/linalg/tests/test_linalg.py", line 217, in test_csingle 
self.do(a) 
File "/opt/apps/lib/python2.5/site-packages/numpy/linalg/tests/test_linalg.py", line 249, in do 
assert_almost_equal(ev, evalues) 
File "/opt/apps/lib/python2.5/site-packages/numpy/linalg/tests/test_linalg.py", line 23, in assert_almost_equal 
old_assert_almost_equal(a, b, decimal=decimal, **kw) 
File "/opt/apps/lib/python2.5/site-packages/numpy/testing/utils.py", line 215, in assert_almost_equal 
return assert_array_almost_equal(actual, desired, decimal, err_msg) 
File "/opt/apps/lib/python2.5/site-packages/numpy/testing/utils.py", line 321, in assert_array_almost_equal 
header='Arrays are not almost equal') 
File "/opt/apps/lib/python2.5/site-packages/numpy/testing/utils.py", line 302, in assert_array_compare 
raise AssertionError(msg) 
AssertionError: 
Arrays are not almost equal 

(mismatch 100.0%) 
x: array([ 4.60555124+0.j, -2.60555124+0.j], dtype=complex64) 
y: array([-2.60555124 +1.11022302e-16j, 4.60555124 -1.11022302e-16j], dtype=complex64) 

---------------------------------------------------------------------- 
Ran 2029 tests in 19.729s 

FAILED (KNOWNFAIL=1, failures=4) 
MEDEA /home/marq> 

----- "Charles R Harris" <charlesr.harris at gmail.com> wrote: 
> 
> 
> 
> On Thu, Mar 26, 2009 at 9:06 PM, Charles R Harris < charlesr.harris at gmail.com > wrote: 
> 

> 
> 
> 
> 2009/3/26 Christian Marquardt < christian at marquardt.sc > 
> 

> Oh sorry - you are right (too late in the night here in Europe). 
> 
> 
> The output is similar in all four cases - it looks like 
> 
> AssertionError: 
> Arrays are not almost equal 
> 
> (mismatch 100.0%) 
> x: array([ 4.60555124+0.j, -2.60555124+0.j], dtype=complex64) 
> y: array([-2.60555124 +1.11022302e-16j, 4.60555124 -1.11022302e-16j], dtype=complex64) 
> 
> Are x and y the expected and actual results? That would just show that there 
> are small rounding errors in the imaginary part, and that MKL returns the results 
> in another order, no? 

> Looks like a sorting error, the eigen values should be sorted. So it looks like a buggy test from here. Having an imaginary part to the eigenvalues returned by a routine that is supposed to process Hermitean matrices doesn't look right, but the errors are in the double precision range, which is pretty good for float32. 
> 
> I think we need a ticket to fix those tests. 
> 

> Can you post the actual error messages? It will make it easier to find where the failure is. 
> 
> Chuck 
> 
> 
> 
> _______________________________________________ Numpy-discussion mailing list Numpy-discussion at scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion 

-- 
Dr. Christian Marquardt Email: christian at marquardt.sc 
Wilhelm-Leuschner-Str. 27 Tel.: +49 (0) 6151 95 13 776 
64293 Darmstadt Mobile: +49 (0) 179 290 84 74 
Germany Fax: +49 (0) 6151 95 13 885 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/numpy-discussion/attachments/20090327/7b90ea2e/attachment.html>