Mailman 3 April 2006 - SciPy-User

Help required regding Eigenvectors
by Sudheer Phani 14 Mar '22

14 Mar '22

Hello All, I have been encountering some strange problems with the calculation of eigen vectors using python. The problem is with the sign of the eigen vectors calculated. On Very few occasions the eigen vectors calculated using python have an opposite sign than the actual eigenvectors, though the magnitude is correct. Can any one of you plz help me in this regard and suggest me some solution if you have encoutered similar problems . Any help in this regd is appreciated Thanks in Advace regds Sudheer

5 5

3D plotting
by Robert Cimrman 10 Sep '09

10 Sep '09

Hi, I need to do some simple 3D plots, so I tried the two Cookbook recipes (xplt, mplot3d) and failed: * xplt: does not work when using a custom installation directory such as python setup.py install --root=/home/share/software apparently the gistdata directory path is wrong: gist.error: failed to create drawing -- Gist work.gs style sheet missing * mplot3d: does not work with my version of matplotlib (0.80). I have made the changes mentioned in the Cookbook to no avail. (Axes.__init__() args apparently changed, as well as some other matplotlib object attributes) Any ideas? mplot3d looks great, I would really like to use it! thanks, r.

6 6

weave.inline : resize an array in c++
by Samuel GARCIA 03 May '06

03 May '06

Hi, how to resize a array in the c++ code with weave.inline() I try : from scipy import * from scipy import weave from scipy.weave import converters c = ones((3,6)) code = """ PyArray_Dims dims; dims.len = 2; dims.ptr = new int[2]; dims.ptr[0] = 4; dims.ptr[1] = 7; PyArray_Resize(&c,&dims); """ err = weave.inline(code, ['c'], type_converters=converters.blitz) print c.shape #I want (4,7) !!! but it does'nt work because c is not a PyArray_Object. Is there a easier (and working) way ? Thanks Samuel

2 5

Re: [SciPy-user] install - floating point exception (sc
by python＠axtom.com 30 Apr '06

30 Apr '06

Hi, After have installed the patched libraries, the FP exceptions have gone. Thanks again, Jean Pierre Jean Pierre DENYS wrote >The processor is used in 32-bit mode. Andrew Straw wrote >>Hmm. Are you running with amd64 architecture or the i386? I haven't >>found that patch to be necessary on amd64. If it is, you'd have to >>rebuild the .debs -- the binaries are only compiled for i386. (The bug >>certainly does affect the i386 architecture, though...) -- Jean Pierre

1 0

Re: [SciPy-user] install - floating point exception (sc
by python＠axtom.com 29 Apr '06

29 Apr '06

Hi all, The processor is used in 32-bit mode. Andrew Straw wrote >Hmm. Are you running with amd64 architecture or the i386? I haven't >found that patch to be necessary on amd64. If it is, you'd have to >rebuild the .debs -- the binaries are only compiled for i386. (The bug >certainly does affect the i386 architecture, though...) Jean Pierre

1 0

(no subject)
by adiril 29 Apr '06

29 Apr '06

  ____________________________________________________________________________ İnternete Taşınmak İçin Yeterince Beklemediniz mi? Alan Adı + 10 MB Web Alanı + 3 Email Adresi Yıllık Sadece 79 YTL

1 0

scipy fails on OS X 10.4
by Tony Mannucci 29 Apr '06

29 Apr '06

I downloaded the binary version of scipy from www.scipy.org/Download for OS X 10.4. I installed in the usual OS X way (from .dmg package file). I get the "old" error I used to see: >>> import scipy >>> scipy.test(level=1) import signal -> failed: Failure linking new module: /Library/Frameworks/Python.framework/Versions/2.4/lib/python2.4/site-packages/scipy/fftpack/_fftpack.so: Symbol not found: _fprintf$LDBLStub Referenced from: /Library/Frameworks/Python.framework/Versions/2.4/lib/python2.4/site-packages/scipy/fftpack/_fftpack.so Expected in: dynamic lookup Versions: >>> scipy.__version__ '0.4.8' >>> scipy.__numpy_version__ '0.9.6' I have selected gcc 3.3 using gcc_select. I had this problem before when I built from source, and it had to do with the gcc version I was using along with g77. Thanks for your help. -Tony -- Tony Mannucci Supervisor, Ionospheric and Atmospheric Remote Sensing Group Mail-Stop 138-308, Tel > (818) 354-1699 Jet Propulsion Laboratory, Fax > (818) 393-5115 California Institute of Technology, Email > Tony.Mannucci(a)jpl.nasa.gov 4800 Oak Grove Drive, http://genesis.jpl.nasa.gov Pasadena, CA 91109

1 0

marching cubes / isosurface in scipy?
by Gennan Chen 28 Apr '06

28 Apr '06

Hi! Is there a algorithm like machine cubes or isosurface in scipy? If not, is anyone working on this type of algorithms? Since my levelset algorithms depends on that, I might need to DIY if no one is working on that. Gen-Nan Chen, PhD Chief Scientist Research and Development Group CorTechs Labs Inc (www.cortechs.net) 1020 Prospect St., #304, La Jolla, CA, 92037 Tel: 1-858-459-9700 ext 16 Fax: 1-858-459-9705 Email: gnchen(a)cortechs.net

4 4

Re: [SciPy-user] install - floating point exception (scipy-tests)
by python＠axtom.com 28 Apr '06

28 Apr '06

Hi all, Thank you Andrew, my processor has indeed SSE support. It is an AMD Opteron 64-bit. I will install a patched libc6 debian package from your site, and let you know. Jean Pierre python(a)axtom.com wrote: >Hi all, > >I have installed scipy, and have some fp exceptions when running the tests. >Does anyone else experiment the same thing? > > GNU libc version 2.3.2 has a bug "feclearexcept() error on CPUs with SSE" (fixed in 2.3.3) which has been submitted to Debian but not fixed in sarge. See the following URL for more info, including links to the above bug reports and patched .debs: http://www.its.caltech.edu/~astraw/coding.html#id3 -- Jean Pierre

3 2

test runnig error
by Hugo Siles 28 Apr '06

28 Apr '06

HI, I am trying to make a correct instalation of the last version of scipython (for the first time of any), during rhe instalation every thing seems to go quite well, when I run de test >>>import scipy >>>scipy.test(level=1, verbosity=2) and after 700 tests or more (ok) gives the import clapack error, not defined clapack_sgesv I am using complete libraries for laplack and atlas all compiled with intel fortran, I also have teh last version of numpy. I get the same error for all levels ( from 1 to 10) and usually after about 700 test ok. I will appreciate any help Hugo Siles

1 0