Mailman 3 February 2003 - SciPy-Dev

RE: [Scipy-cvs] world/scipy/scipy_distutils mingw32_support.py,1.9,1.10
by eric jones 06 Mar '03

06 Mar '03

Looks like this fixed things. The vq build is dying on my desktop which has mingw gcc 3.2 on it. It is the dllwrap call that is failing. It needs dllwrap.exe --driver-name g++ ... specified so that it links in the correct C++ libraries. How was this working before? Maybe 2.95.3 didn't have the problem?? Anyway, I'll build the vq version by hand for the moment. Thanks for the fix, eric ---------------------------------------------- eric jones 515 Congress Ave www.enthought.com Suite 1614 512 536-1057 Austin, Tx 78701 > -----Original Message----- > From: scipy-cvs-admin(a)scipy.org [mailto:scipy-cvs-admin@scipy.org] On > Behalf Of pearu(a)scipy.org > Sent: Friday, February 28, 2003 5:33 PM > To: scipy-cvs(a)scipy.org > Subject: [Scipy-cvs] world/scipy/scipy_distutils > mingw32_support.py,1.9,1.10 > > Update of /home/cvsroot/world/scipy/scipy_distutils > In directory scipy.org:/tmp/cvs-serv23974 > > Modified Files: > mingw32_support.py > Log Message: > Enabled use_gcc,g77 again in mingw32_support.py as calling them in > build_flib may be too late. Not sure if this was the cause of building > failures on win32.. > > > Index: mingw32_support.py > =================================================================== > RCS file: /home/cvsroot/world/scipy/scipy_distutils/mingw32_support.py,v > retrieving revision 1.9 > retrieving revision 1.10 > diff -C2 -d -r1.9 -r1.10 > *** mingw32_support.py 27 Feb 2003 16:21:00 -0000 1.9 > --- mingw32_support.py 28 Feb 2003 23:33:15 -0000 1.10 > *************** > *** 68,72 **** > # raise DistutilsPlatformError, msg > > ! if 0: > # See build_flib.finalize_options method in build_flib.py > # where set_windows_compiler is called with proper > --- 68,72 ---- > # raise DistutilsPlatformError, msg > > ! if 1: > # See build_flib.finalize_options method in build_flib.py > # where set_windows_compiler is called with proper > > > _______________________________________________ > Scipy-cvs mailing list > Scipy-cvs(a)scipy.org > http://scipy.net/mailman/listinfo/scipy-cvs

1 2

Problem in linalg functions with overwrite check
by Travis Oliphant 01 Mar '03

01 Mar '03

I've found a potential problem in the linear algebra functions related to the overwrite_a parameter. Many routines alter the overwrite_a parameter after conversion of the input object to an array. The check is not very robust however when the input is an object that uses an array as it's main core (like a Matrix object). For example. Code looks something like this a1 = asarray(a) # Convert a to an array object overwrite_a = overwrite_a or (a1 is not a) So, if a was not already an array then overwrite_a is modified to overwrite the a1 array (which is presumed to be a copy anyway). The problem with this strategy is that if a is an object that has an __array__ method. The asarray function will call it to obtain the object a as an array. Often, this call does not return a new copy of the data but just a reference to the array forming the underlying storage of a. So, while a and a1 are different objects and so a1 is not a, they use the same storage space, so overwriting a1 changes the object a leading to strange, unexpected behavior. I got caught while passing Matrix objects to the linalg.det routine and getting different answers everytime the function ran (because the underlying matrix was being changed everytime). I'm asking for suggestions on how to fix this. We could for example, try to call the __array__ method on our own and then if it succeeds never alter the overwrite_a parameter. Or more elegantly perhaps we could try to write some function share_storage(a1,a) --- maybe partly in C that tries to determine whether or not a1 and a actually share the same storage. Comments welcome. -Travis Oliphant

2 1

Question on GA lab in Python
by Shi, Weimin 01 Mar '03

01 Mar '03

Hi, Eric, I am an new user in Python and are trying to use the GA do some design experiment, but could not even get the example in ga work. Could you please tell me where can I get help? (It is on WinXP.) Thanks, Weimin Shi Platform Tech Operation, DPG, Intel Corp. (503) 712-2790 (503) 712-2823 (Fax)

1 0

[ANN] imv.py: interactive 3D plots with MayaVi.
by Prabhu Ramachandran 28 Feb '03

28 Feb '03

hi, imv.py is a module that lets you sample surfaces and arrays from the Python interpreter via convenient one line functions. It requires MayaVi (version 1.2) to be installed and running as a Python module i.e. the binary installs will not be able to use this. imv provides three useful functions: surf -- Creates a surface given regularly spaced values of x, y and the corresponding z as arrays. Also works if z is a function. view -- Allows one to view a 2D Numeric array. Note that the view will be set to the way we normally think of matrices with with 0, 0 at the top left of the screen. Works best for smaller arrays (size < 512x512). viewi -- Allows one to view a 2D Numeric array as an image. This works best for very large arrays (like 1024x1024 or larger arrays). The code is well documented and has an illustrative example in the function 'main' at the end of the file. To see the example simply run imv.py. The module is available here: http://www.ae.iitm.ac.in/~prabhu/software/mayavi.html or http://www.aero.iitm.ernet.in/~prabhu/software/mayavi.html Additionally, the module has some code that lets you easily convert Numeric Arrays into vtkDataArrays. So if you are interested in doing that you might want to take a look at the code. Have fun! prabhu p.s. Sorry about the cross-posting.

1 0

Error compiling on Sun Solaris
by tjlahey 27 Feb '03

27 Feb '03

Hi, I've just tried compiling from CVS, and I ran into the following problem. The Sun compiler uses CC to compile C++, and cc to compile C code. Scipy uses cc to compile all the C and C++ code. There only appears to be 1 C++ file, vq_wrap.cpp and the cc compiler chokes on it. Hand compiling with CC works and restarting the compile process appears to work. Cheers, Tim Lahey

1 0

Prebuilt ATLAS libraries available
by Pearu Peterson 26 Feb '03

26 Feb '03

Hi! An initial list of prebuilt ATLAS libraries for various platforms (currently only for unices, though) with various C compiler combinations is available at http://www.scipy.org/site_content/downloads/atlas_binaries This list will be used for regression testing of scipy but it can be useful for those users who choose not to build ATLAS libraries them self. And the list will probably grow in future.. Regards, Pearu

3 2

[Fwd: [SciPy-user] ValueError: I/O operation on closed file]
by Nils Wagner 22 Feb '03

22 Feb '03

1 0

Unable to install SciPy 0.2.0
by Yves Moisan 20 Feb '03

20 Feb '03

Hi, I have downloaded SciPy and can't install it on my Win 2K system. I have Python 2.2 in C:\Python22 but I want to stuff it with a Python 2.1 that comes with Zope. I don't know if it is the potential conflict between the two Python versions (or the fact that I have no Python environment variables?), but the 2nd window of the installer 9see attached) does not let me specify a Python implementation. What do I do ? Thanx, Yves Moisan

2 1

segmentation fault
by baecker＠physik.tu-dresden.de 18 Feb '03

18 Feb '03

Hi, with the current CVS version I get for scipy.test(10) after a while "[...] function f6 cc.bisect : 0.480 cc.ridder : 0.560 cc.brenth : 0.520 cc.brentq : 0.530 ..zsh: 4347 segmentation fault python " (Several lines before it says "TESTING SPEED".) I managed to find the routine which produces the above output (namely: scipy.optimize.test(), apart from the segmentation fault ..., so that one must occur afterwards.) My question is: How can I find out which of the routines being tested leads to the segmentation fault? For example is there a way to make the testing more verbose in telling me what it is just about to test ? (I tried to figure out which packages are included in the unit test, but got lost quickly ...) ((In any case the reason for this fault has to do with my installation/setup as on a different machine scipy just installs fine ...)) Many thanks, Arnd

1 0

Bug in Mplot.py
by Fernando Perez 18 Feb '03

18 Feb '03

Hi all, In [16]: xplt.imagesc_cb(K,palette=array([0,1])) --------------------------------------------------------------------------- NameError Traceback (most recent call last) ? /usr/lib/python2.2/site-packages/scipy/xplt/Mplot.py in imagesc_cb(z, cmin, cmax, xryr, _style, zlabel, font, fontsize, color, palette) 928 cmin = float(cmin) 929 --> 930 change_palette(palette) 931 932 byteimage = gist.bytscl(z,cmin=cmin,cmax=cmax) /usr/lib/python2.2/site-packages/scipy/xplt/Mplot.py in change_palette(pal) 603 else: 604 data = Numeric.asarray(pal) --> 605 write_palette('/tmp/_temp.gp',data) 606 gist.palette('/tmp/_temp.gp') 607 /usr/lib/python2.2/site-packages/scipy/xplt/Mplot.py in write_palette(tofile, pal) 549 palsize = pal.shape 550 if len(palsize) == 1: --> 551 pal = multiply.outer(pal,ones((3,),pal.typecode())) 552 palsize = pal.shape 553 if not (palsize[1] == 3 or palsize[0] == 3): NameError: global name 'multiply' is not defined It seems that this code was written thinking of a from Numeric import * and later was changed without testing. I added 'multiply,ones' to the from Numeric import ... line and it fixed the crashes I saw, but there may be other problems lurking. A pychecker run on all the scipy codes would probably be a good idea... Cheers, f.

2 1