[SciPy-user] Problems testing SciPy 0.3.2

Francesc Alted falted at pytables.org
Sat Oct 16 04:31:14 CDT 2004


A Divendres 15 Octubre 2004 19:40, Pearu Peterson va escriure:
> Could you try building scipy against the following ATLAS library:
> 
>    http://www.scipy.org/download/atlasbinaries/linux/atlas3.6.0_Linux_P4SSE2.tgz
> 
> (it contains complete lapack, so just unpack the .tgz file and point 
> ATLAS environment variable to the lib directory)?
> 

Yes, that works much better. Only 2 errors now:

======================================================================
ERROR: check_random (scipy.linalg.basic.test_basic.test_det)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/users/exp/alted/bin-i686//lib/python/scipy/linalg/tests/test_basic.py", line 282, in check_random
    Numeric_det = LinearAlgebra.determinant
AttributeError: 'module' object has no attribute 'determinant'

======================================================================
ERROR: check_random_complex (scipy.linalg.basic.test_basic.test_det)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/users/exp/alted/bin-i686//lib/python/scipy/linalg/tests/test_basic.py", line 292, in check_random_complex
    Numeric_det = LinearAlgebra.determinant
AttributeError: 'module' object has no attribute 'determinant'

----------------------------------------------------------------------
Ran 695 tests in 1.552s

FAILED (errors=2)
<unittest.TextTestRunner object at 0xb72758cc>
-----------

Curiously enough, if I change the directory to scipy/Lib/linalg, start the
python interpreter and run the tests there, everything goes well:

----------------------------------------------------------------------
Ran 600 tests in 1.333s

OK
<unittest.TextTestRunner object at 0xb727e7cc>
-----------

You can note, however, that only 600 tests were executed there.

So, it seems that my ATLAS libraries were bad. Uh, I don't know what I was
doing wrong, but apparently I repeteated the error twice. That's strange
because your instructions in INSTALL.txt were clear enough :-/ Perhaps
something wrong with my software versions?

gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-42)
LAPACK, Version 3.0 (update) Date: May 31, 2000
ATLAS 3.6.0

> Also, do the  following commands work?
> 
> cd Lib/lapack
> python setup_atlas_version.py build_ext --inplace
> python -c 'import atlas_version'

Here you are:

[alted at api linalg]$ python -c 'import atlas_version'
ATLAS version 3.6.0 built by pearu on Sat Apr 10 13:28:37 CDT 2004:
   UNAME    : Linux xp 2.4.25-1-686 #1 Tue Feb 24 10:55:59 EST 2004 i686 GNU/Linux
   INSTFLG  :
   MMDEF    : /home/pearu/src/ATLAS/CONFIG/ARCHS/P4SSE2/gcc/gemm
   ARCHDEF  : /home/pearu/src/ATLAS/CONFIG/ARCHS/P4SSE2/gcc/misc
   F2CDEFS  : -DAdd_ -DStringSunStyle
   CACHEEDGE: 1048576
   F77      : /usr/bin/g77, version GNU Fortran (GCC) 3.3.3 (Debian 20040401)
   F77FLAGS : -fomit-frame-pointer -O -fno-second-underscore
   CC       : /usr/bin/gcc, version gcc (GCC) 3.3.3 (Debian 20040401)
   CC FLAGS : -fomit-frame-pointer -O3 -funroll-all-loops
   MCC      : /usr/bin/gcc, version gcc (GCC) 3.3.3 (Debian 20040401)
   MCCFLAGS : -fomit-frame-pointer -O

Now, with my own generated ATLAS libs:

[alted at api linalg]$ python -c 'import atlas_version'
ATLAS version 3.6.0 built by alted on vie oct 15 17:02:42 CEST 2004:
   UNAME    : Linux api.uji.es 2.4.21-20.ELsmp #1 SMP Wed Aug 18 20:46:40 EDT 2004 i686 i686 i386 GNU/Linux
   INSTFLG  :
   MMDEF    : /scratch1/alted/ATLAS/CONFIG/ARCHS/P4SSE2/gcc/gemm
   ARCHDEF  : /scratch1/alted/ATLAS/CONFIG/ARCHS/P4SSE2/gcc/misc
   F2CDEFS  : -DAdd__ -DStringSunStyle
   CACHEEDGE: 1048576
   F77      : /usr/bin/g77, version GNU Fortran (GCC 3.2.3 20030502 (Red Hat Linux 3.2.3-42)) 3.2.3 20030502 (Red Hat Linux 3.2.3-42)
   F77FLAGS : -fomit-frame-pointer -O
   CC       : /usr/bin/gcc, version gcc (GCC) 3.2.3 20030502 (Red Hat Linux 3.2.3-42)
   CC FLAGS : -fomit-frame-pointer -O3 -funroll-all-loops
   MCC      : /usr/bin/gcc, version gcc (GCC) 3.2.3 20030502 (Red Hat Linux 3.2.3-42)
   MCCFLAGS : -fomit-frame-pointer -O


At first sigth, I can see a difference: the "-fno-second-underscore" flag
that you put when compiling, while I didn't put this. Can this account for
the problems?

Thanks for your help!

-- 
Francesc Alted



More information about the SciPy-user mailing list