Gennan Chen | 1 Feb 03:14

something like GTS??

Hi!

Is there something like GTS (GNU Triangulated Surface Library: http://gts.sourceforge.net/)  in Scipy? I hate to cook my own for all those bookkeeping of vertices and surfaces. Any recommendation will be welcomed..

Gen-Nan Chen


_______________________________________________
SciPy-user mailing list
SciPy-user <at> scipy.org
http://projects.scipy.org/mailman/listinfo/scipy-user
David Cournapeau | 1 Feb 04:54
Picon
Picon

Re: Release 0.6.1 of pyaudio, renamed pyaudiolab

Rob Hetland wrote:
> pyaudiolab works on Mac OS X, but the library needs to point to  
> libsndfile.dylab instead of libsndfile.so.1.
>
Argh, I thought I solved the problem.
> This seems to be hardwired in the setup, and I needed to change the  
> pysndfile.py in the actual python site-packages after the install.
It is not hardcoded: the setup.py is supposed to detect the library 
extension used on the platform, and build the name of the library 
accordingly (on Mac OS X, libsndfile.dylib.1):

If you have time, I would appreciate to have the mac os X library name 
problem fixed. This is not difficult to fix, but I don't have easy 
access to mac os X, and this kind of info is not easy to find with 
simple googling. Helpful info (you can post me privately) are:

- what does python -c "from numpy.distutils.system_info import so_ext; 
print so_ext" return ?
- the name of compiled libsndfile (my understanding is that under mac os 
X, for the equivalent of shared , not dynamically loaded libraries, the 
convention is 'lib' + library_name + so_ext + '.' + 'major version', 
where library_name is sndfile, major version is 1, and so_ext '.dylib')

>
> Also, the example on the web page does not work exactly right.   
> setting frames to 1e4 does not work, as 1e4 is a float, not an int.   
> I think that it would make sense to coerce the frames input to an  
> integer before calling libsndfile.
Are you sure you are using the version posted on the website ? Because 
nframes are coerced into 64 bits integers for some time, now (actually, 
that was exactly the problem related to ctypes and ubuntu, where long 
long were 32 bits instead of 64).

David
Robert Kern | 1 Feb 05:22
Picon
Gravatar

Re: something like GTS??

Gennan Chen wrote:
> Hi!
> 
> Is there something like GTS (GNU Triangulated Surface Library:
> http://gts.sourceforge.net/)  in Scipy? I hate to cook my own for all
> those bookkeeping of vertices and surfaces. Any recommendation will be
> welcomed..

Not currently in scipy, no. At Enthought, we have written a library that does
much the same thing (Boolean operations on triangulated-surface-bounded volumes)
somewhat more robustly (in our experience). It is not, at the moment, open
source although we've talked about opening it. Offers to help develop and
maintain it would go a long way towards that end.

--

-- 
Robert Kern

"I have come to believe that the whole world is an enigma, a harmless enigma
 that is made terrible by our own mad attempt to interpret it as though it had
 an underlying truth."
  -- Umberto Eco
Jerry | 1 Feb 05:52
Favicon

Re: What it the best way to install on a Mac?

Thanks for all the comments. I've already downloaded Chris's package  
and will see how that goes--this isn't a high priority at the moment-- 
just planning ahead.

I have nothing but respect for you guys who make all of this happen,  
and I'm not trying to start a flame war. (I've unintentionally done  
that before, if not on this list, then on another, by suggesting that  
the installation process should be easy.)

First, I have installed a number of programs from source and it's  
usually a pain in the ass. If all that's required is one cycle of tar- 
cd-configure-make, that's OK by me, but it's not usually that easy,  
it seems. In the OS X world, it is customary that all of those  
convenient installation instructions such as were provided elsewhere  
in this thread to be codified into an installer.

(Pedantic comments follow--sorry.) On OS X, there are two kinds of  
installation methods (for mainstream software, that is). One is a  
single drag-and-drop operation from a disk image to the package's  
final destination. (Apple's "package" is a directory that acts like a  
double-clickable application program.) The other way (more  
appropriate for a lot of the open source stuff, probably) is an  
automated installer that "just works" and performs any necessary  
operations and then puts any number of files wherever they need to  
go, leaving a receipt file in a special place to aid uninstalling.  
Even installation from source could be wrapped up into such an  
installer.

There are a great many very smart people who would benefit from using  
Python and its accessories in a technical computing environment but  
who have no inclination (in fact, a great disinclination) to install  
from source. Many of these folks use Macs and simply won't stand for  
a difficult installation because it's not the Mac culture to do so.  
And let me tell you that "difficult installation" for a Mac user is a  
low bar indeed.

I would guess that four out of five technically-oriented Mac users  
would turn and run if they were considering using Python and its  
friends for their technical computing needs and encountered  
instructions to install from source. Fortunately, Chris's installer  
seems to be the answer. By the way, Chris, if you haven't done so  
already, you might post a notice over at http://www.macresearch.org/.  
I think it's a pretty new site but they passed the 10000-registered- 
user mark some time back and the rate of news postings has increased  
a lot lately. Also, a notice to Apple's ADC page about the installer  
would probably get some notice because they send e-mails to all the  
ADC folks every month or so with links to open source software.

Thanks again for the helpful comments.

Jerry

On Jan 31, 2007, at 11:28 AM, Robert Kern wrote:

> joris <at> ster.kuleuven.ac.be wrote:
>> On Wednesday 31 January 2007 01:27, Robert Kern wrote:
>>
>>> Learn to build from source. Because of the dependency on FORTRAN  
>>> runtime
>>> libraries, this is the lowest-hassle method.
>>
>> This may be true at the moment, but I hope this will not be the  
>> general
>> philosophy for the future?
>
> It's not a philosophy; it's a technical problem. If you can solve  
> the technical
> problem, building from source will no longer be the lowest-hassle  
> method.
>
>> Having to build from source may scare off potential
>> numpy/scipy/matplotlib users... Yesterday someone said that he was  
>> trying to
>> install scipy from source for about 2 weeks now.
>
> I mean no disrespect to all the parties involved, but the common  
> problem that I
> see between all of the people who take such a long time to build  
> scipy is that
> they tend to thrash around, trying everything, without  
> understanding what
> they're doing. Going back and forth on a mailing list trying to  
> diagnose a
> problem naturally takes a long time. It's such a grossly  
> inefficient way to
> troubleshoot.
>
> But when there's a problem with the binary package, the same exact  
> thing
> happens. There is no substitute for learning.
>
>> It's not that I demand other people to make easy-to-install  
>> packages, but I
>> think that we're heading in the wrong direction if we don't even  
>> think that
>> easy-to-install packages are really necessary and that installing  
>> from source
>> works just fine.
>
> We're not. Solve the technical problem, and the whole issue will go  
> away.
>
> -- 
> Robert Kern
>
> "I have come to believe that the whole world is an enigma, a  
> harmless enigma
>  that is made terrible by our own mad attempt to interpret it as  
> though it had
>  an underlying truth."
>   -- Umberto Eco
> _______________________________________________
> SciPy-user mailing list
> SciPy-user <at> scipy.org
> http://projects.scipy.org/mailman/listinfo/scipy-user
>
Chiara Caronna | 1 Feb 17:46
Picon

error importing scipy

Hello,
since a couple of days I got an error when I try to run "from scipy import 
*"
here is the error message....

" Traceback (most recent call last):
  File "<stdin>", line 1, in ?
  File "/usr/local/lib/python2.4/site-packages/scipy/linalg/__init__.py", 
line 8, in ?
    from basic import *
  File "/usr/local/lib/python2.4/site-packages/scipy/linalg/basic.py", line 
227, in ?
    import decomp
  File "/usr/local/lib/python2.4/site-packages/scipy/linalg/decomp.py", line 
21, in ?
    from blas import get_blas_funcs
  File "/usr/local/lib/python2.4/site-packages/scipy/linalg/blas.py", line 
14, in ?
    from scipy.linalg import fblas
ImportError: /usr/local/lib/python2.4/site-packages/scipy/linalg/fblas.so: 
undefined symbol: srotmg_"

does anyone have a clue?!

thanks,
Chiara

_________________________________________________________________
Express yourself instantly with MSN Messenger! Download today it's FREE! 
http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
Robert Kern | 1 Feb 17:56
Picon
Gravatar

Re: error importing scipy

Chiara Caronna wrote:
> Hello,
> since a couple of days I got an error when I try to run "from scipy import 
> *"
> here is the error message....
> 
> 
> " Traceback (most recent call last):
>   File "<stdin>", line 1, in ?
>   File "/usr/local/lib/python2.4/site-packages/scipy/linalg/__init__.py", 
> line 8, in ?
>     from basic import *
>   File "/usr/local/lib/python2.4/site-packages/scipy/linalg/basic.py", line 
> 227, in ?
>     import decomp
>   File "/usr/local/lib/python2.4/site-packages/scipy/linalg/decomp.py", line 
> 21, in ?
>     from blas import get_blas_funcs
>   File "/usr/local/lib/python2.4/site-packages/scipy/linalg/blas.py", line 
> 14, in ?
>     from scipy.linalg import fblas
> ImportError: /usr/local/lib/python2.4/site-packages/scipy/linalg/fblas.so: 
> undefined symbol: srotmg_"
> 
> does anyone have a clue?!

Your scipy was not linked to a BLAS library correctly. What BLAS library were
you trying to link against? Where are its files located on your system? Did you
use a site.cfg file to configure scipy? Can you show us the output of

  $ cd ~/src/scipy  # or whatever
  $ python setup.py configure

--

-- 
Robert Kern

"I have come to believe that the whole world is an enigma, a harmless enigma
 that is made terrible by our own mad attempt to interpret it as though it had
 an underlying truth."
  -- Umberto Eco
Chiara Caronna | 1 Feb 18:31
Picon

Re: error importing scipy


>From: Robert Kern <robert.kern <at> gmail.com>
>Reply-To: SciPy Users List <scipy-user <at> scipy.org>
>To: SciPy Users List <scipy-user <at> scipy.org>
>Subject: Re: [SciPy-user] error importing scipy
>Date: Thu, 01 Feb 2007 10:56:14 -0600
>
>Chiara Caronna wrote:
> > Hello,
> > since a couple of days I got an error when I try to run "from scipy 
>import
> > *"
> > here is the error message....
> >
> >
> > " Traceback (most recent call last):
> >   File "<stdin>", line 1, in ?
> >   File 
>"/usr/local/lib/python2.4/site-packages/scipy/linalg/__init__.py",
> > line 8, in ?
> >     from basic import *
> >   File "/usr/local/lib/python2.4/site-packages/scipy/linalg/basic.py", 
>line
> > 227, in ?
> >     import decomp
> >   File "/usr/local/lib/python2.4/site-packages/scipy/linalg/decomp.py", 
>line
> > 21, in ?
> >     from blas import get_blas_funcs
> >   File "/usr/local/lib/python2.4/site-packages/scipy/linalg/blas.py", 
>line
> > 14, in ?
> >     from scipy.linalg import fblas
> > ImportError: 
>/usr/local/lib/python2.4/site-packages/scipy/linalg/fblas.so:
> > undefined symbol: srotmg_"
> >
> > does anyone have a clue?!
>
>Your scipy was not linked to a BLAS library correctly. What BLAS library 
>were
>you trying to link against?

'_' ... I have never tried to do that... at least I am not aware of...

Where are its files located on your system?

I don't know it, how can I find that out?

>Did you use a site.cfg file to configure scipy?

I am not sure I understood the question... I download the file 
scipy-0.5.2.tar.gz, extracted it and followed the instructions... so I guess 
the answer is "no, I didn't"

Can you show us the output of
>
>   $ cd ~/src/scipy  # or whatever
>   $ python setup.py configure

I did this:

cd /usr/local/lib/python2.4/site-packages/scipy
python setup.py configure

here is the output:

non-existing path in 'cluster': 'src/vq_wrap.cpp'
Appending scipy.cluster configuration to scipy
Ignoring attempt to set 'name' (from 'scipy' to 'scipy.cluster')
mkl_info:
  libraries mkl,vml,guide not found in /usr/local/lib
  libraries mkl,vml,guide not found in /usr/lib
  NOT AVAILABLE

fftw3_info:
  libraries fftw3 not found in /usr/local/lib
  libraries fftw3 not found in /usr/lib
  fftw3 not found
  NOT AVAILABLE

fftw2_info:
  libraries rfftw,fftw not found in /usr/local/lib
  libraries rfftw,fftw not found in /usr/lib
  fftw2 not found
  NOT AVAILABLE

dfftw_info:
  libraries drfftw,dfftw not found in /usr/local/lib
  libraries drfftw,dfftw not found in /usr/lib
  dfftw not found
  NOT AVAILABLE

djbfft_info:
  NOT AVAILABLE

could not resolve pattern in 'fftpack': 'dfftpack/*.f'
non-existing path in 'fftpack': 'fftpack.pyf'
non-existing path in 'fftpack': 'src/zfft.c'
non-existing path in 'fftpack': 'src/drfft.c'
non-existing path in 'fftpack': 'src/zrfft.c'
non-existing path in 'fftpack': 'src/zfftnd.c'
non-existing path in 'fftpack': 'convolve.pyf'
non-existing path in 'fftpack': 'src/convolve.c'
Appending scipy.fftpack configuration to scipy
Ignoring attempt to set 'name' (from 'scipy' to 'scipy.fftpack')
blas_opt_info:
blas_mkl_info:
  libraries mkl,vml,guide not found in /usr/local/lib
  libraries mkl,vml,guide not found in /usr/lib
  NOT AVAILABLE

atlas_blas_threads_info:
Setting PTATLAS=ATLAS
  libraries lapack,blas not found in /usr/local/lib
Setting PTATLAS=ATLAS
Setting PTATLAS=ATLAS
  FOUND:
    libraries = ['lapack', 'blas']
    library_dirs = ['/usr/lib']
    language = c

Could not locate executable gfortran
Could not locate executable f95
customize GnuFCompiler
invalid command 'configure'
Could not locate executable ifort
Could not locate executable ifc
Could not locate executable ifort
Could not locate executable efort
Could not locate executable efc
Could not locate executable ifort
Could not locate executable efort
Could not locate executable efc
customize IntelFCompiler
invalid command 'configure'
customize LaheyFCompiler
invalid command 'configure'
customize PGroupFCompiler
invalid command 'configure'
customize AbsoftFCompiler
invalid command 'configure'
customize NAGFCompiler
invalid command 'configure'
customize VastFCompiler
invalid command 'configure'
customize CompaqFCompiler
invalid command 'configure'
customize IntelItaniumFCompiler
invalid command 'configure'
customize IntelEM64TFCompiler
invalid command 'configure'
customize Gnu95FCompiler
invalid command 'configure'
customize G95FCompiler
invalid command 'configure'
customize GnuFCompiler
invalid command 'configure'
customize Gnu95FCompiler
invalid command 'configure'
customize GnuFCompiler
customize GnuFCompiler using config
  FOUND:
    libraries = ['lapack', 'blas']
    library_dirs = ['/usr/lib']
    language = c
    define_macros = [('ATLAS_INFO', '"\\"?.?.?\\""')]

could not resolve pattern in 'integrate': 'linpack_lite/*.f'
could not resolve pattern in 'integrate': 'mach/*.f'
could not resolve pattern in 'integrate': 'quadpack/*.f'
could not resolve pattern in 'integrate': 'odepack/*.f'
non-existing path in 'integrate': '_quadpackmodule.c'
non-existing path in 'integrate': '_odepackmodule.c'
non-existing path in 'integrate': 'vode.pyf'
Appending scipy.integrate configuration to scipy
Ignoring attempt to set 'name' (from 'scipy' to 'scipy.integrate')
could not resolve pattern in 'interpolate': 'fitpack/*.f'
non-existing path in 'interpolate': '_fitpackmodule.c'
non-existing path in 'interpolate': 'fitpack.pyf'
Appending scipy.interpolate configuration to scipy
Ignoring attempt to set 'name' (from 'scipy' to 'scipy.interpolate')
non-existing path in 'io': 'numpyiomodule.c'
Appending scipy.io configuration to scipy
Ignoring attempt to set 'name' (from 'scipy' to 'scipy.io')
ATLAS version ?.?.?
non-existing path in 'lib/blas': 'fblas.pyf.src'
non-existing path in 'lib/blas': 'fblaswrap.f.src'
could not resolve pattern in 'lib/blas': 'fblas_l?.pyf.src'
non-existing path in 'lib/blas': 'cblas.pyf.src'
could not resolve pattern in 'lib/blas': 'cblas_l?.pyf.src'
Appending scipy.lib.blas configuration to scipy.lib
Ignoring attempt to set 'name' (from 'scipy.lib' to 'scipy.lib.blas')
lapack_opt_info:
lapack_mkl_info:
  NOT AVAILABLE

atlas_threads_info:
Setting PTATLAS=ATLAS
  libraries lapack,blas not found in /usr/local/lib
  libraries lapack_atlas not found in /usr/local/lib
  libraries lapack_atlas not found in /usr/lib
numpy.distutils.system_info.atlas_threads_info
Setting PTATLAS=ATLAS
Setting PTATLAS=ATLAS
  FOUND:
    libraries = ['lapack', 'lapack', 'blas']
    library_dirs = ['/usr/lib']
    language = f77

customize GnuFCompiler
invalid command 'configure'
customize IntelFCompiler
invalid command 'configure'
customize LaheyFCompiler
invalid command 'configure'
customize PGroupFCompiler
invalid command 'configure'
customize AbsoftFCompiler
invalid command 'configure'
customize NAGFCompiler
invalid command 'configure'
customize VastFCompiler
invalid command 'configure'
customize CompaqFCompiler
invalid command 'configure'
customize IntelItaniumFCompiler
invalid command 'configure'
customize IntelEM64TFCompiler
invalid command 'configure'
customize Gnu95FCompiler
invalid command 'configure'
customize G95FCompiler
invalid command 'configure'
customize GnuFCompiler
invalid command 'configure'
customize Gnu95FCompiler
invalid command 'configure'
customize GnuFCompiler
customize GnuFCompiler using config
  FOUND:
    libraries = ['lapack', 'lapack', 'blas']
    library_dirs = ['/usr/lib']
    language = f77
    define_macros = [('ATLAS_INFO', '"\\"?.?.?\\""')]

ATLAS version ?.?.?
non-existing path in 'lib/lapack': 'flapack.pyf.src'
could not resolve pattern in 'lib/lapack': 'flapack_*.pyf.src'
non-existing path in 'lib/lapack': 'clapack.pyf.src'
non-existing path in 'lib/lapack': 'calc_lwork.f'
non-existing path in 'lib/lapack': 'atlas_version.c'
Appending scipy.lib.lapack configuration to scipy.lib
Ignoring attempt to set 'name' (from 'scipy.lib' to 'scipy.lib.lapack')
Appending scipy.lib configuration to scipy
Ignoring attempt to set 'name' (from 'scipy' to 'scipy.lib')
ATLAS version ?.?.?
non-existing path in 'linalg': 'src/fblaswrap.f'
non-existing path in 'linalg': 'generic_fblas.pyf'
non-existing path in 'linalg': 'generic_fblas1.pyf'
non-existing path in 'linalg': 'generic_fblas2.pyf'
non-existing path in 'linalg': 'generic_fblas3.pyf'
non-existing path in 'linalg': 'generic_cblas.pyf'
non-existing path in 'linalg': 'generic_cblas1.pyf'
non-existing path in 'linalg': 'generic_flapack.pyf'
non-existing path in 'linalg': 'flapack_user_routines.pyf'
non-existing path in 'linalg': 'generic_clapack.pyf'
non-existing path in 'linalg': 'src/det.f'
non-existing path in 'linalg': 'src/lu.f'
non-existing path in 'linalg': 'src/calc_lwork.f'
non-existing path in 'linalg': 'atlas_version.c'
non-existing path in 'linalg': 'iterative/STOPTEST2.f.src'
non-existing path in 'linalg': 'iterative/getbreak.f.src'
non-existing path in 'linalg': 'iterative/BiCGREVCOM.f.src'
non-existing path in 'linalg': 'iterative/BiCGSTABREVCOM.f.src'
non-existing path in 'linalg': 'iterative/CGREVCOM.f.src'
non-existing path in 'linalg': 'iterative/CGSREVCOM.f.src'
non-existing path in 'linalg': 'iterative/GMRESREVCOM.f.src'
non-existing path in 'linalg': 'iterative/QMRREVCOM.f.src'
non-existing path in 'linalg': 'iterative/_iterative.pyf.src'
Appending scipy.linalg configuration to scipy
Ignoring attempt to set 'name' (from 'scipy' to 'scipy.linalg')
could not resolve pattern in 'linsolve': 'SuperLU/SRC/*.c'
non-existing path in 'linsolve': '_zsuperlumodule.c'
non-existing path in 'linsolve': '_superlu_utils.c'
non-existing path in 'linsolve': '_superluobject.c'
non-existing path in 'linsolve': '_dsuperlumodule.c'
non-existing path in 'linsolve': '_superlu_utils.c'
non-existing path in 'linsolve': '_superluobject.c'
non-existing path in 'linsolve': '_csuperlumodule.c'
non-existing path in 'linsolve': '_superlu_utils.c'
non-existing path in 'linsolve': '_superluobject.c'
non-existing path in 'linsolve': '_ssuperlumodule.c'
non-existing path in 'linsolve': '_superlu_utils.c'
non-existing path in 'linsolve': '_superluobject.c'
umfpack_info:
  libraries umfpack not found in /usr/local/lib
  libraries umfpack not found in /usr/lib
/usr/local/lib/python2.4/site-packages/numpy/distutils/system_info.py:401: 
UserWarning:
    UMFPACK sparse solver (http://www.cise.ufl.edu/research/sparse/umfpack/)
    not found. Directories to search for the libraries can be specified in 
the
    numpy/distutils/site.cfg file (section [umfpack]) or by setting
    the UMFPACK environment variable.
  warnings.warn(self.notfounderror.__doc__)
  NOT AVAILABLE

non-existing path in 'linsolve/umfpack': 'umfpack.i'
non-existing path in 'linsolve/umfpack': 'umfpack.i'
Appending scipy.linsolve.umfpack configuration to scipy.linsolve
Ignoring attempt to set 'name' (from 'scipy.linsolve' to 
'scipy.linsolve.umfpack')
Appending scipy.linsolve configuration to scipy
Ignoring attempt to set 'name' (from 'scipy' to 'scipy.linsolve')
non-existing path in 'maxentropy': 'doc'
Appending scipy.maxentropy configuration to scipy
Ignoring attempt to set 'name' (from 'scipy' to 'scipy.maxentropy')
Appending scipy.misc configuration to scipy
Ignoring attempt to set 'name' (from 'scipy' to 'scipy.misc')
non-existing path in 'odr': 'odrpack/d_odr.f'
non-existing path in 'odr': 'odrpack/d_mprec.f'
non-existing path in 'odr': 'odrpack/dlunoc.f'
non-existing path in 'odr': 'odrpack/d_lpk.f'
non-existing path in 'odr': '__odrpack.c'
Appending scipy.odr configuration to scipy
Ignoring attempt to set 'name' (from 'scipy' to 'scipy.odr')
could not resolve pattern in 'optimize': 'minpack/*f'
non-existing path in 'optimize': '_minpackmodule.c'
could not resolve pattern in 'optimize': 'Zeros/*.c'
non-existing path in 'optimize': 'zeros.c'
non-existing path in 'optimize': 'lbfgsb/lbfgsb.pyf'
non-existing path in 'optimize': 'lbfgsb/routines.f'
non-existing path in 'optimize': 'tnc/moduleTNC.c'
non-existing path in 'optimize': 'tnc/tnc.c'
non-existing path in 'optimize': 'cobyla/cobyla.pyf'
non-existing path in 'optimize': 'cobyla/cobyla2.f'
non-existing path in 'optimize': 'cobyla/trstlp.f'
non-existing path in 'optimize': 'minpack2/minpack2.pyf'
non-existing path in 'optimize': 'minpack2/dcsrch.f'
non-existing path in 'optimize': 'minpack2/dcstep.f'
Appending scipy.optimize configuration to scipy
Ignoring attempt to set 'name' (from 'scipy' to 'scipy.optimize')
Appending scipy.sandbox configuration to scipy
Ignoring attempt to set 'name' (from 'scipy' to 'scipy.sandbox')
non-existing path in 'signal': 'sigtoolsmodule.c'
non-existing path in 'signal': 'firfilter.c'
non-existing path in 'signal': 'medianfilter.c'
non-existing path in 'signal': 'sigtools.h'
non-existing path in 'signal': 'splinemodule.c'
non-existing path in 'signal': 'S_bspline_util.c'
non-existing path in 'signal': 'D_bspline_util.c'
non-existing path in 'signal': 'C_bspline_util.c'
non-existing path in 'signal': 'Z_bspline_util.c'
non-existing path in 'signal': 'bspline_util.c'
Appending scipy.signal configuration to scipy
Ignoring attempt to set 'name' (from 'scipy' to 'scipy.signal')
non-existing path in 'sparse': 'sparsetools/spblas.f.src'
non-existing path in 'sparse': 'sparsetools/spconv.f.src'
non-existing path in 'sparse': 'sparsetools/sparsetools.pyf.src'
Appending scipy.sparse configuration to scipy
Ignoring attempt to set 'name' (from 'scipy' to 'scipy.sparse')
could not resolve pattern in 'special': 'c_misc/*.c'
could not resolve pattern in 'special': 'cephes/*.c'
could not resolve pattern in 'special': 'mach/*.f'
could not resolve pattern in 'special': 'amos/*.f'
could not resolve pattern in 'special': 'toms/*.f'
could not resolve pattern in 'special': 'cdflib/*.f'
could not resolve pattern in 'special': 'specfun/*.f'
non-existing path in 'special': '_cephesmodule.c'
non-existing path in 'special': 'amos_wrappers.c'
non-existing path in 'special': 'specfun_wrappers.c'
non-existing path in 'special': 'toms_wrappers.c'
non-existing path in 'special': 'cdf_wrappers.c'
non-existing path in 'special': 'ufunc_extras.c'
non-existing path in 'special': 'specfun.pyf'
Appending scipy.special configuration to scipy
Ignoring attempt to set 'name' (from 'scipy' to 'scipy.special')
could not resolve pattern in 'stats': 'statlib/*.f'
non-existing path in 'stats': 'statlib.pyf'
non-existing path in 'stats': 'futil.f'
non-existing path in 'stats': 'mvn.pyf'
non-existing path in 'stats': 'mvndst.f'
Appending scipy.stats configuration to scipy
Ignoring attempt to set 'name' (from 'scipy' to 'scipy.stats')
non-existing path in 'ndimage': 'src/nd_image.c'
non-existing path in 'ndimage': 'src/ni_filters.c'
non-existing path in 'ndimage': 'src/ni_fourier.c'
non-existing path in 'ndimage': 'src/ni_interpolation.c'
non-existing path in 'ndimage': 'src/ni_measure.c'
non-existing path in 'ndimage': 'src/ni_morphology.c'
non-existing path in 'ndimage': 'src/ni_support.c'
non-existing path in 'ndimage': 'src'
Appending scipy.ndimage configuration to scipy
Ignoring attempt to set 'name' (from 'scipy' to 'scipy.ndimage')
Warning: Assuming default configuration 
(stsci/convolve/{setup_convolve,setup}.py was not
found)
Traceback (most recent call last):
  File "setup.py", line 31, in ?
    setup(**configuration(top_path='').todict())
  File "setup.py", line 23, in configuration
    config.add_subpackage('stsci')
  File 
"/usr/local/lib/python2.4/site-packages/numpy/distutils/misc_util.py", line 
765, in add_subpackage
    caller_level = 2)
  File 
"/usr/local/lib/python2.4/site-packages/numpy/distutils/misc_util.py", line 
748, in get_subpackage
    caller_level = caller_level + 1)
  File 
"/usr/local/lib/python2.4/site-packages/numpy/distutils/misc_util.py", line 
695, in _get_configuration_from_setup_py
    config = setup_module.configuration(*args)
  File "/usr/local/lib/python2.4/site-packages/scipy/stsci/setup.py", line 
5, in configuration
    config.add_subpackage('convolve')
  File 
"/usr/local/lib/python2.4/site-packages/numpy/distutils/misc_util.py", line 
765, in add_subpackage
    caller_level = 2)
  File 
"/usr/local/lib/python2.4/site-packages/numpy/distutils/misc_util.py", line 
741, in get_subpackage
    caller_level = caller_level+1)
  File 
"/usr/local/lib/python2.4/site-packages/numpy/distutils/misc_util.py", line 
541, in __init__
    raise ValueError("%r is not a directory" % (package_path,))
ValueError: 'stsci/convolve' is not a directory

>
>--
>Robert Kern
>
>"I have come to believe that the whole world is an enigma, a harmless 
>enigma
>  that is made terrible by our own mad attempt to interpret it as though it 
>had
>  an underlying truth."
>   -- Umberto Eco
>_______________________________________________
>SciPy-user mailing list
>SciPy-user <at> scipy.org
>http://projects.scipy.org/mailman/listinfo/scipy-user

_________________________________________________________________
Don't just search. Find. Check out the new MSN Search! 
http://search.msn.com/
Robert Kern | 1 Feb 18:41
Picon
Gravatar

Re: error importing scipy

Chiara Caronna wrote:
>> From: Robert Kern <robert.kern <at> gmail.com>

>> Your scipy was not linked to a BLAS library correctly. What BLAS library 
>> were
>> you trying to link against?
> 
> '_' ... I have never tried to do that... at least I am not aware of...

Okay, what kind of system are you on? If Linux, what distribution? What LAPACK
and BLAS packages do you have installed?

--

-- 
Robert Kern

"I have come to believe that the whole world is an enigma, a harmless enigma
 that is made terrible by our own mad attempt to interpret it as though it had
 an underlying truth."
  -- Umberto Eco
Chiara Caronna | 1 Feb 18:49
Picon

Re: error importing scipy


>From: Robert Kern <robert.kern <at> gmail.com>
>Reply-To: SciPy Users List <scipy-user <at> scipy.org>
>To: SciPy Users List <scipy-user <at> scipy.org>
>Subject: Re: [SciPy-user] error importing scipy
>Date: Thu, 01 Feb 2007 11:41:46 -0600
>
>Chiara Caronna wrote:
> >> From: Robert Kern <robert.kern <at> gmail.com>
>
> >> Your scipy was not linked to a BLAS library correctly. What BLAS 
>library
> >> were
> >> you trying to link against?
> >
> > '_' ... I have never tried to do that... at least I am not aware of...
>
>Okay, what kind of system are you on? If Linux, what distribution?

I have Linux, Suse 8.4 (quite old, I know, but I can't change it, it's my 
office pc...)

>What LAPACK and BLAS packages do you have installed?
I have never installed them... how can I check which I have?

>
>--
>Robert Kern
>
>"I have come to believe that the whole world is an enigma, a harmless 
>enigma
>  that is made terrible by our own mad attempt to interpret it as though it 
>had
>  an underlying truth."
>   -- Umberto Eco
>_______________________________________________
>SciPy-user mailing list
>SciPy-user <at> scipy.org
>http://projects.scipy.org/mailman/listinfo/scipy-user

_________________________________________________________________
Express yourself instantly with MSN Messenger! Download today it's FREE! 
http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
Russell E. Owen | 1 Feb 19:21
Favicon

Re: What it the best way to install on a Mac?

In article <20070131223800.GA20121 <at> avicenna.cc.columbia.edu>,
 Lev Givon <lev <at> columbia.edu> wrote:

> ...It might be desirable to encourage a matplotlib person to add some
> information regarding the installation of that package, as I suspect
> that many folks in need of installation wisdom think in terms of the
> tetrad ipython/numpy/scipy/matplotlib.

My instructions for building a universal matplotlib for MacOS X from 
source are here (google for "build matplotlib for mac"):
http://www.astro.washington.edu/owen/BuildingMatplotlibForMac.html

I would be happy to move this to a wiki if anyone can suggest an 
appropriate one.

Having good instructions for building complex packages like matplotlib 
is very important. It should be kept current and readily available. That 
said, building matplotlib is tricky enough that few users will want to 
bother. And they shouldn't have to. Most people will be much happier 
with downloadable packages.

-- Russell

Gmane