Mailman 3 December 2002 - SciPy-User

Building VTK from source
by Stefan Mogck Dec. 9, 2002

Dec. 9, 2002

Hallo scipy users! I'd like to install MayaVi under linux. For that I have to install VTK first. I have problems to get the Python bindings into VTK. I hope I configured cmake correctly to bind tk, tcl and python. After the configuration I started make and I got the following error message: mk39:/home/stefan/pythonsource/VTK # make cmake.depends is up-to-date /home/stefan/pythonsource/VTK/Wrapping: building default_target /usr/bin/cmake -S/home/stefan/pythonsource/VTK/Wrapping -O/home/stefan/pythonsource/VTK/Wrapping -H/home/stefan/pythonsource/VTK -B/home/stefan/pythonsource/VTK CMake Error: Invalid escape sequence \I in argument [HKEY_LOCAL_MACHINE\\SOFTWARE\\Python\\PythonCore\\2.2\InstallPath]/include make[3]: *** [cmake.depends] Error 255 make[2]: *** [default_target] Error 2 make[1]: *** [default_target_Wrapping] Error 2 make: *** [default_target] Error 2 Has anybody an idea what I have to modify. Probably in FindPythonLibs.cmake? (I am using python2.2 under linux Suse 7.3) Thanks, Stefan Mogck

2 1

Re: (long) Weave installation problems on Linux
by Leighton Pritchard Dec. 9, 2002

Dec. 9, 2002

At 12:00 06/12/2002, you wrote: >All errors that you saw from weave tests are due to using a >"wrong" compiler. I believe that the current weave fully supports gcc 2.95 >compiler. When using gcc 3.x compilers, some weave test are known to fail. >You may try weave-3.0 from its CVS, it has less issues when using gcc >3.x compilers. Thanks for the help. I've obtained weave from cvs using cvs -d :pserver:anonymous@scipy.org:/home/cvsroot checkout weave Is there another source for this, as I'm still getting errors of: ================================================== /usr/local/lib/python2.2/site-packages/weave/blitz-20001213/blitz/ops.h:220: no match for `std::complex<float>& / double&' operator =================================================== /home/lep/.python22_compiled/211372/sc_a6df888dc732b38ae7a4c5fa1063b4251.cpp: In function `PyObject* compiled_func(PyObject*, PyObject*)': /home/lep/.python22_compiled/211372/sc_a6df888dc732b38ae7a4c5fa1063b4251.cpp:649: no match for `std::string& < int' operator /home/lep/.python22_compiled/211372/sc_a6df888dc732b38ae7a4c5fa1063b4251.cpp:653: no match for `std::string& + int' operator /usr/include/g++-v3/bits/stl_bvector.h:267: candidates are: std::_Bit_const_iterator std::operator+(int, const std::_Bit_const_iterator&) /usr/include/g++-v3/bits/stl_bvector.h:208: std::_Bit_iterator std::operator+(int, const std::_Bit_iterator&) ===================================================== ERROR: result[1:-1,1:-1] = (b[1:-1,1:-1] + b[2:,1:-1] + b[:-2,1:-1] ---------------------------------------------------------------------- Traceback (most recent call last): File "/usr/local/lib/python2.2/site-packages/weave/tests/test_blitz_tools.py", line 150, in check_5point_avg_2d self.generic_2d(expr) File "/usr/local/lib/python2.2/site-packages/weave/tests/test_blitz_tools.py", line 124, in generic_2d mod_location) File "/usr/local/lib/python2.2/site-packages/weave/tests/test_blitz_tools.py", line 80, in generic_test blitz_tools.blitz(expr,arg_dict,{},verbose=0) #, File "/usr/local/lib/python2.2/site-packages/weave/blitz_tools.py", line 72, in blitz type_converters = converters.blitz, File "/usr/local/lib/python2.2/site-packages/weave/inline_tools.py", line 439, in compile_function verbose=verbose, **kw) File "/usr/local/lib/python2.2/site-packages/weave/ext_tools.py", line 332, in compile verbose = verbose, **kw) File "/usr/local/lib/python2.2/site-packages/weave/build_tools.py", line 221, in build_extension setup(name = module_name, ext_modules = [ext],verbose=verb) File "/usr/local/lib/python2.2/distutils/core.py", line 157, in setup raise SystemExit, "error: " + str(msg) CompileError: error: command 'gcc' failed with exit status 1 ================================================== Or is this what you meant by 'less issues'? ;) -- Dr Leighton Pritchard AMRSC T44, Cledwyn Building Institute of Biological Sciences University of Wales, Aberystwyth, SY23 3DD Tel 01970 622353 ext. 2353 PGP public key - http://www.keyserver.net (0x47B4A485)

2 1

ANN: F2PY - Fortran to Python Interface Generator - 6th Release
by Pearu Peterson Dec. 8, 2002

Dec. 8, 2002

F2PY - Fortran to Python Interface Generator, Version 2.32.225 --------------------------------------------------------------- I am pleased to announce the sixth public release of F2PY. The purpose of the F2PY project is to provide a connection between Python and Fortran programming languages. For more information, see http://cens.ioc.ee/projects/f2py2e/ Download source: http://cens.ioc.ee/projects/f2py2e/2.x/F2PY-2-latest.tar.gz What's new? ------------ It has been almost a year from the previous release of F2PY. This release comes with a number of improvements, most important ones are listed as follows: - The issue with a Fortran and C multi-dimensional array storage ordering is finally resolved. F2PY generated wrappers automatically carry out all necessary transformations, trying hard to minimize any performance hits. As a result, the end users of F2PY generated wrappers need not to worry about this issue anymore, multi-dimensional arrays in Python and Fortran have now exactly the same signatures. - Improved wrapping C functions with F2PY. - F2PY Users Guide has been throughly revised to describe and illustrate all latest F2PY features such as wrapping Fortran 77 COMMON blocks, Fortran 90 module data, including Fortran 90 module ALLOCATABLE arrays, etc. The F2PY Users Guide is composed using the Python Docutils tool and is available here: http://cens.ioc.ee/projects/f2py2e/usersguide/ - F2PY has new site for unit testing. - F2PY uses scipy_distutils from SciPy (www.scipy.org) project for compiling Fortran sources and building extension modules. Currently, the following Fortran 77/90 compilers are described by scipy_distutils: Absoft Sun SGI Intel Itanium NAG Compaq Digital Gnu VAST - Finally, F2PY has been extensively used/tested for wrapping large Fortran/C libraries, such as, LAPACK, BLAS, ATLAS, FFTW, FFTPACK, etc. (see SciPy project for more information). This experience has been a very important source for ideas how to make binding Fortran/C codes to Python easier and more robust. Enjoy, Pearu Peterson --------------- <P><A HREF="http://cens.ioc.ee/projects/f2py2e/">F2PY 2.32.225</A> - The Fortran to Python Interface Generator (08-Dec-02)

1 0

interpolate package - scale-dependent?
by Frank Gibbons Dec. 7, 2002

Dec. 7, 2002

I must confess I'm not much of an expert on interpolation. However, I was playing around with the interpolate package today, trying to figure out why the quality of the spline returned appears to vary with the scale of the data: some data (set of (x,y) pairs) that produce a good spline, when the y's are divided by a factor of 100, produce a really poor one. Maybe there are some assumptions about scale inherent in the spline algorithm, perhaps relating to the stiffness of the curves. Still, I figured that should be user-adjustable. If it is, how do I do it? If not, shouldn't there be some documentation on the effective scales that will work? Regarding docs for that package, they're very hard to read in their current form, because each argument's description runs into that of the one that follows it. But it turns out, if you put a blank line between the argument descriptions, then HappyDoc generates far more legible output. I don't know what the formatting rules for HappyDoc are, but wanted to share: This will cause the output to be run together: "x -- first arg y -- second arg" x -- first arg y -- second arg Putting a space between those lines generates: x first arg y second arg Readable docs are important in my opinion. Is this a problem with other packages too? Perhaps we can come up with a script to fix it SciPy-wide. -Frank Gibbons PhD, Computational Biologist, Harvard Medical School BCMP/SGM-322, 250 Longwood Ave, Boston MA 02115, USA. Tel: 617-432-3555 Fax: 617-432-3557 http://llama.med.harvard.edu/~fgibbons

2 1

(long) Weave installation problems on Linux
by Leighton Pritchard Dec. 6, 2002

Dec. 6, 2002

Hi, Apologies first for the length of the posting, and the irrelevance to anyone who's happily using Weave and/or SciPy without any difficulty, but I'm stuck and could do with some help. I've been attempting to install SciPy and Weave under Mandrake 8.2, and I'm having all sorts of niggly problems. I'm most interested in getting Weave to work well first, so I'll begin there. I've managed to get Weave working after a fashion. The simple test code I throw at it works OK, but the test suite that comes with it throws a bundle of errors. I'd greatly appreciate any guidance you could give me as to where I've gone wrong in the installation, or anthing else I may have overlooked/messed up. Apologies if it's a really stupid error. Information to aid with a diagnosis is below: I'm using the tarball from http://www.scipy.org/site_content/weave/weave-0.2.3.tar.gz. $ uname -a Linux louse 2.4.18-6mdk #1 Fri Mar 15 02:59:08 CET 2002 i686 unknown $ gcc --v Reading specs from /usr/lib/gcc-lib/i586-mandrake-linux-gnu/3.0.4/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share/gcc-3.0.4 --enable-shared --enable-threads=posix --disable-checking --enable-long-long --enable-cstdio=stdio --enable-clocale=generic --enable-languages=c,c++,f77,objc,java --program-suffix=-3.0.4 --enable-objc-gc --host=i586-mandrake-linux-gnu --with-system-zlib Thread model: posix gcc version 3.0.4 (Mandrake Linux 8.2 3.0.4-2mdk) The Python version (in usr/local/bin, /usr/local/lib etc. is: Python 2.2.1 (#1, Aug 8 2002, 17:45:24) [GCC 3.0.4 (Mandrake Linux 8.2 3.0.4-2mdk)] on linux2 Numeric is v21.3 After untarring/gunzipping I enter the expanded directory and use the usual (and documented) python setup.py install. Everything appears to go smoothly. >>> import weave shows no errors >>> weave.test() shows a bucketload. Stdout is: ================================================================================= creating test suite for: weave.ast_tools No test suite found for weave.base_info No test suite found for weave.base_spec No test suite found for weave.blitz_info No test suite found for weave.blitz_spec creating test suite for: weave.blitz_tools creating test suite for: weave.build_tools creating test suite for: weave.catalog No test suite found for weave.code_blocks No test suite found for weave.common_info creating test suite for: weave.common_spec No test suite found for weave.conversion_code No test suite found for weave.conversion_code_old No test suite found for weave.cxx_info No test suite found for weave.dumbdbm_patched No test suite found for weave.dumb_shelve creating test suite for: weave.ext_tools building extensions here: /home/lep/.python22_compiled/164260 building extensions here: /home/lep/.python22_compiled/164261 No test suite found for weave.inline_info creating test suite for: weave.inline_tools No test suite found for weave.lib2def No test suite found for weave.misc No test suite found for weave.scalar_info creating test suite for: weave.scalar_spec creating test suite for: weave.sequence_spec creating test suite for: weave.size_check creating test suite for: weave.slice_handler No test suite found for weave.standard_array_info creating test suite for: weave.standard_array_spec No test suite found for weave.swig_info No test suite found for weave.wx_info No test suite found for weave.wx_spec Expression: result[1:-1,1:-1] = (b[1:-1,1:-1] + b[2:,1:-1] + b[:-2,1:-1]+ b[1:-1,2:] + b[1:-1,:-2]) / 5. Run: (10, 10) f warning: specified build_dir '_bad_path_' does not exist or is or is not writable. Trying default locations warning: specified build_dir '..' does not exist or is or is not writable. Trying default locations warning: specified build_dir '_bad_path_' does not exist or is or is not writable. Trying default locations warning: specified build_dir '..' does not exist or is or is not writable. Trying default locations test printing a value:2 ================================================================================= Stderr is: ================================================================================= ...In file included from /usr/local/lib/python2.2/site-packages/weave/blitz-20001213/blitz/numinquire.h:60, from /usr/local/lib/python2.2/site-packages/weave/blitz-20001213/blitz/array/expr.h:63, from /usr/local/lib/python2.2/site-packages/weave/blitz-20001213/blitz/array.h:2469, from /home/lep/.python22_compiled/164262/sc_5599df30197fe981824ad8ec934a784e0.cpp:3: /usr/local/lib/python2.2/site-packages/weave/blitz-20001213/blitz/limits-hack.h:30: multiple definition of `enum std::float_round_style' /usr/include/g++-v3/bits/std_limits.h:866: previous definition here /usr/local/lib/python2.2/site-packages/weave/blitz-20001213/blitz/limits-hack.h:31: conflicting types for `round_indeterminate' /usr/include/g++-v3/bits/std_limits.h:867: previous declaration as `std::float_round_style round_indeterminate' /usr/local/lib/python2.2/site-packages/weave/blitz-20001213/blitz/limits-hack.h:32: conflicting types for `round_toward_zero' /usr/include/g++-v3/bits/std_limits.h:868: previous declaration as `std::float_round_style round_toward_zero' /usr/local/lib/python2.2/site-packages/weave/blitz-20001213/blitz/limits-hack.h:33: conflicting types for `round_to_nearest' /usr/include/g++-v3/bits/std_limits.h:869: previous declaration as `std::float_round_style round_to_nearest' /usr/local/lib/python2.2/site-packages/weave/blitz-20001213/blitz/limits-hack.h:34: conflicting types for `round_toward_infinity' /usr/include/g++-v3/bits/std_limits.h:870: previous declaration as `std::float_round_style round_toward_infinity' /usr/local/lib/python2.2/site-packages/weave/blitz-20001213/blitz/limits-hack.h:36: conflicting types for `round_toward_neg_infinity' /usr/include/g++-v3/bits/std_limits.h:872: previous declaration as `std::float_round_style round_toward_neg_infinity' /usr/local/lib/python2.2/site-packages/weave/blitz-20001213/blitz/limits-hack.h:38: multiple definition of `enum std::float_denorm_style' /usr/include/g++-v3/bits/std_limits.h:875: previous definition here /usr/local/lib/python2.2/site-packages/weave/blitz-20001213/blitz/limits-hack.h:39: conflicting types for `denorm_indeterminate' /usr/include/g++-v3/bits/std_limits.h:876: previous declaration as `std::float_denorm_style denorm_indeterminate' /usr/local/lib/python2.2/site-packages/weave/blitz-20001213/blitz/limits-hack.h:40: conflicting types for `denorm_absent' /usr/include/g++-v3/bits/std_limits.h:877: previous declaration as `std::float_denorm_style denorm_absent' /usr/local/lib/python2.2/site-packages/weave/blitz-20001213/blitz/limits-hack.h:42: conflicting types for `denorm_present' /usr/include/g++-v3/bits/std_limits.h:879: previous declaration as `std::float_denorm_style denorm_present' /usr/local/lib/python2.2/site-packages/weave/blitz-20001213/blitz/limits-hack.h:258: redefinition of `struct std::numeric_limits<_Tp>' /usr/include/g++-v3/bits/std_limits.h:886: previous definition of `struct std::numeric_limits<_Tp>' /usr/local/lib/python2.2/site-packages/weave/blitz-20001213/blitz/limits-hack.h:267: redefinition of `class std::numeric_limits<bool>' /usr/include/g++-v3/bits/std_limits.h:1020: previous definition of `class std::numeric_limits<bool>' /usr/local/lib/python2.2/site-packages/weave/blitz-20001213/blitz/limits-hack.h:274: redefinition of `class std::numeric_limits<char>' /usr/include/g++-v3/bits/std_limits.h:1077: previous definition of `class std::numeric_limits<char>' /usr/local/lib/python2.2/site-packages/weave/blitz-20001213/blitz/limits-hack.h:279: redefinition of `class std::numeric_limits<signed char>' /usr/include/g++-v3/bits/std_limits.h:1135: previous definition of `class std::numeric_limits<signed char>' /usr/local/lib/python2.2/site-packages/weave/blitz-20001213/blitz/limits-hack.h:284: redefinition of `class std::numeric_limits<unsigned char>' /usr/include/g++-v3/bits/std_limits.h:1191: previous definition of `class std::numeric_limits<unsigned char>' /usr/local/lib/python2.2/site-packages/weave/blitz-20001213/blitz/limits-hack.h:298: redefinition of `class std::numeric_limits<short int>' /usr/include/g++-v3/bits/std_limits.h:1303: previous definition of `class std::numeric_limits<short int>' /usr/local/lib/python2.2/site-packages/weave/blitz-20001213/blitz/limits-hack.h:303: redefinition of `class std::numeric_limits<short unsigned int>' /usr/include/g++-v3/bits/std_limits.h:1359: previous definition of `class std::numeric_limits<short unsigned int>' /usr/local/lib/python2.2/site-packages/weave/blitz-20001213/blitz/limits-hack.h:308: redefinition of `class std::numeric_limits<int>' /usr/include/g++-v3/bits/std_limits.h:1414: previous definition of `class std::numeric_limits<int>' /usr/local/lib/python2.2/site-packages/weave/blitz-20001213/blitz/limits-hack.h:313: redefinition of `class std::numeric_limits<unsigned int>' /usr/include/g++-v3/bits/std_limits.h:1470: previous definition of `class std::numeric_limits<unsigned int>' /usr/local/lib/python2.2/site-packages/weave/blitz-20001213/blitz/limits-hack.h:318: redefinition of `class std::numeric_limits<long int>' /usr/include/g++-v3/bits/std_limits.h:1525: previous definition of `class std::numeric_limits<long int>' /usr/local/lib/python2.2/site-packages/weave/blitz-20001213/blitz/limits-hack.h:323: redefinition of `class std::numeric_limits<long unsigned int>' /usr/include/g++-v3/bits/std_limits.h:1581: previous definition of `class std::numeric_limits<long unsigned int>' /usr/local/lib/python2.2/site-packages/weave/blitz-20001213/blitz/limits-hack.h:360: redefinition of `class std::numeric_limits<float>' /usr/include/g++-v3/bits/std_limits.h:1747: previous definition of `class std::numeric_limits<float>' /usr/local/lib/python2.2/site-packages/weave/blitz-20001213/blitz/limits-hack.h:382: redefinition of `class std::numeric_limits<double>' /usr/include/g++-v3/bits/std_limits.h:1823: previous definition of `class std::numeric_limits<double>' /usr/local/lib/python2.2/site-packages/weave/blitz-20001213/blitz/limits-hack.h:404: redefinition of `class std::numeric_limits<long double>' /usr/include/g++-v3/bits/std_limits.h:1902: previous definition of `class std::numeric_limits<long double>' /home/lep/.python22_compiled/164262/sc_5599df30197fe981824ad8ec934a784e0.cpp:550:1: warning: "convert_to_numpy" redefined /home/lep/.python22_compiled/164262/sc_5599df30197fe981824ad8ec934a784e0.cpp:549:1: warning: this is the location of the previous definition E............................................./home/lep/.python22_compiled/164262/sc_9a25bc84add18fe6c75501f6b01bd84e1.cpp: In function `PyObject* compiled_func(PyObject*, PyObject*)': /home/lep/.python22_compiled/164262/sc_9a25bc84add18fe6c75501f6b01bd84e1.cpp:535: no match for `Py::String& < int' operator /usr/local/lib/python2.2/site-packages/weave/CXX/Objects.hxx:390: candidates are: bool Py::Object::operator<(const Py::Object&) const /usr/local/lib/python2.2/site-packages/weave/CXX/Objects.hxx:1433: bool Py::operator<(const Py::SeqBase<Py::Object>::const_iterator&, const Py::SeqBase<Py::Object>::const_iterator&) /usr/local/lib/python2.2/site-packages/weave/CXX/Objects.hxx:1426: bool Py::operator<(const Py::SeqBase<Py::Object>::iterator&, const Py::SeqBase<Py::Object>::iterator&) ............................................................................................................................................ ====================================================================== ERROR: result[1:-1,1:-1] = (b[1:-1,1:-1] + b[2:,1:-1] + b[:-2,1:-1] ---------------------------------------------------------------------- Traceback (most recent call last): File "/usr/local/lib/python2.2/site-packages/weave/tests/test_blitz_tools.py", line 154, in check_5point_avg_2d self.generic_2d(expr) File "/usr/local/lib/python2.2/site-packages/weave/tests/test_blitz_tools.py", line 128, in generic_2d mod_location) File "/usr/local/lib/python2.2/site-packages/weave/tests/test_blitz_tools.py", line 84, in generic_test blitz_tools.blitz(expr,arg_dict,{},verbose=0) #, File "/usr/local/lib/python2.2/site-packages/weave/blitz_tools.py", line 99, in blitz type_factories = blitz_type_factories, File "/usr/local/lib/python2.2/site-packages/weave/inline_tools.py", line 426, in compile_function verbose=verbose, **kw) File "/usr/local/lib/python2.2/site-packages/weave/ext_tools.py", line 349, in compile verbose = verbose, **kw) File "/usr/local/lib/python2.2/site-packages/weave/build_tools.py", line 194, in build_extension setup(name = module_name, ext_modules = [ext],verbose=verb) File "/usr/local/lib/python2.2/distutils/core.py", line 157, in setup raise SystemExit, "error: " + str(msg) CompileError: error: command 'gcc' failed with exit status 1 ---------------------------------------------------------------------- Ran 189 tests in 150.327s FAILED (errors=1) ================================================================================= Test code taken from the tutorial seems to work. E.g. the example shown below works fine. ================================================================================= import random import time def sortedDictValues3(adict): keys = adict.keys() keys.sort() return map(adict.get, keys) def c_sort(adict): assert(type(adict) == type({})) code = """ #line 21 "dict_sort.py" Py::List keys = adict.keys(); Py::List items(keys.length()); keys.sort(); PyObject* item = NULL; for(int i = 0; i < keys.length();i++) { item = PyList_GET_ITEM(keys.ptr(),i); item = PyDict_GetItem(adict.ptr(),item); Py_XINCREF(item); PyList_SetItem(items.ptr(),i,item); } return_val = Py::new_reference_to(items); """ return inline(code,['adict'],verbose=1) alist = range(100) random.shuffle(alist) print alist adict = {} for a in alist: adict[a] = a bdict = adict.copy() b = sortedDictValues3(adict) print b c = c_sort(adict) print c ================================================================================= -- Dr Leighton Pritchard AMRSC T44, Cledwyn Building Institute of Biological Sciences University of Wales, Aberystwyth, SY23 3DD Tel 01970 622353 ext. 2353 PGP public key - http://www.keyserver.net (0x47B4A485)

2 1

Importing foreign images
by Stefan Mogck Dec. 5, 2002

Dec. 5, 2002

Hallo Scipy-user, How can I import e.g. *.tiff and *.jpg files for image processing? I think, I can do it also with python Stefan

3 3

Possibly bug in signal.module mean function
by Stefan Mogck Dec. 5, 2002

Dec. 5, 2002

Hi scipy-user, I'd like to use the wienfilter for filtering my images. I tried again first an example from the manual: stefan@mk39:~> python Python 2.2.2 (#1, Nov 28 2002, 09:15:11) [GCC 2.95.3 20010315 (SuSE)] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> import gui_thread >>> <Importing wxPython... done.> >>> from scipy import * >>> from scipy import plt >>> from Numeric import * >>> from RandomArray import normal >>> img=plt.lena() >>> plt.image(img) <type 'array'> ['__copy__', '__deepcopy__', 'astype', 'byteswapped', 'copy', 'iscontiguous', 'itemsize', 'resize', 'savespace', 'spacesaver', 'tolist', 'toscalar', 'tostring', 'typecode'] <C wxFrame instance at _41200618_wxFrame_p> >>> noisy_img=img+normal(0,32,shape(img)) >>> plt.figure() <C wxFrame instance at _886a420_wxFrame_p> >>> plt.image(noisy_img) <type 'array'> ['__copy__', '__deepcopy__', 'astype', 'byteswapped', 'copy', 'iscontiguous', 'itemsize', 'resize', 'savespace', 'spacesaver', 'tolist', 'toscalar', 'tostring', 'typecode'] <C wxFrame instance at _886a420_wxFrame_p> >>> cleaned_img=signal.wiener(noisy_img) Traceback (most recent call last): File "<stdin>", line 1, in ? File "/usr/local/lib/python2.2/site-packages/scipy/signal/signaltools.py", line 223, in wiener noise = Numeric.mean(Numeric.ravel(lVar)) AttributeError: 'module' object has no attribute 'mean' I am using SciPy -0.2.0_alpha_144.4350 and Numeric-22.0 under pythojn 2.2.2. Have anyvbody an idea about this problem. I want to understand this problem Stefan

2 1

Bug in signaltools.py in Scipy-0.2
by Stefan Mogck Dec. 5, 2002

Dec. 5, 2002

I just posted a possibly bug in the signal module. mean function. What I found that the function 'mean' is not defined directly in Numerical. Therefore I added in signaltools.py: import MLab and changed also line 223: noise = Numeric.mean(Numeric.ravel(lVar)) to noise = MLab.mean(Numeric.ravel(lVar)) The same in line 231 and 232: im = Numeric.maximum(im,0) lVar = Numeric.maximum(lVar,noise) to im = MLab.maximum(im,0) lVar = MLab.maximum(lVar,noise) After this changes the wiener filter is working. See example under: http://www.scipy.org/site_content/screen_shots May be this is not the best solution, but it helps Stefan Mogck

2 1

SciPy setup problem under RH 7.3
by Dave Bazell Dec. 4, 2002

Dec. 4, 2002

I just tried installing scipy on my redhat 7.3 system. I installed the fftw package and the numpy (numeric22) package and then the scipy package. When I start python and try to access scipy to run the test module I get some errors and the tests don't run. Perhaps someone can seem my error and enlighten me. I have included printout to detail the problems Python 2.2.2 (#1, Oct 21 2002, 12:22:55) [GCC 2.96 20000731 (Red Hat Linux 7.3 2.96-110)] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> help() Welcome to Python 2.2! This is the online help utility. If this is your first time using Python, you should definitely check out the tutorial on the Internet at http://www.python.org/doc/tut/. Enter the name of any module, keyword, or topic to get help on writing Python programs and using Python modules. To quit this help utility and return to the interpreter, just type "quit". To get a list of available modules, keywords, or topics, type "modules", "keywords", or "topics". Each module also comes with a one-line summary of what it does; to list the modules whose summaries contain a given word such as "spam", type "modules spam". help> Help on module numeric_version: NAME numeric_version FILE /usr/local/lib/python2.2/site-packages/Numeric/numeric_version.py DATA __file__ = '/usr/local/lib/python2.2/site-packages/Numeric/numeric_ver... __name__ = 'numeric_version' version = '22.0' help> You are now leaving help and returning to the Python interpreter. If you want to ask for help on a particular object directly from the interpreter, you can type "help(object)". Executing "help('string')" has the same effect as typing a particular string at the help> prompt. >>> >>> import scipy Traceback (most recent call last): File "<stdin>", line 1, in ? File "/usr/local/lib/python2.2/site-packages/scipy/__init__.py", line 41, in ? from handy import * File "/usr/local/lib/python2.2/site-packages/scipy/handy.py", line 1, in ? import Numeric File "/usr/local/lib/python2.2/site-packages/Numeric/Numeric.py", line 93, in ? from Precision import * File "/usr/local/lib/python2.2/site-packages/Numeric/Precision.py", line 26, in ? _code_table = _fill_table(typecodes) File "/usr/local/lib/python2.2/site-packages/Numeric/Precision.py", line 23, in _fill_table table[key] = _get_precisions(value) File "/usr/local/lib/python2.2/site-packages/Numeric/Precision.py", line 18, in _get_precisions lst.append( (zeros( (1,), t ).itemsize()*8, t) ) ValueError: Invalid type for array >>> >>> import scipy >>> >>> scipy.test() Traceback (most recent call last): File "<stdin>", line 1, in ? AttributeError: 'module' object has no attribute 'test' >>> >>> Any help would be appreciated. Dave

2 1