Mailman 3 August 2006 - SciPy-Dev

Trouble with check loadmat on 64 bit machines
by Nils Wagner Aug. 14, 2006

Aug. 14, 2006

Hi all, I get 16 errors with >>> numpy.__version__ '1.0b2.dev3005' >>> scipy.__version__ '0.5.0.2158' Three typical messages are below Traceback (most recent call last): File "/usr/lib64/python2.4/site-packages/scipy/io/tests/test_mio.py", line 79, in cc self._check_case(name, expected) File "/usr/lib64/python2.4/site-packages/scipy/io/tests/test_mio.py", line 69, in _check_case matdict = loadmat(f) File "/usr/lib64/python2.4/site-packages/scipy/io/mio.py", line 801, in loadmat thisdict = _loadv5(fid,basename) File "/usr/lib64/python2.4/site-packages/scipy/io/mio.py", line 739, in _loadv5 el, varname, unused = _get_element(fid, return_name_dtype=True) File "/usr/lib64/python2.4/site-packages/scipy/io/mio.py", line 724, in _get_element el, name = _parse_mimatrix(fid,numbytes) File "/usr/lib64/python2.4/site-packages/scipy/io/mio.py", line 605, in _parse_mimatrix result = zeros(length, object) MemoryError Traceback (most recent call last): File "/usr/lib64/python2.4/site-packages/scipy/io/tests/test_mio.py", line 79, in cc self._check_case(name, expected) File "/usr/lib64/python2.4/site-packages/scipy/io/tests/test_mio.py", line 69, in _check_case matdict = loadmat(f) File "/usr/lib64/python2.4/site-packages/scipy/io/mio.py", line 801, in loadmat thisdict = _loadv5(fid,basename) File "/usr/lib64/python2.4/site-packages/scipy/io/mio.py", line 739, in _loadv5 el, varname, unused = _get_element(fid, return_name_dtype=True) File "/usr/lib64/python2.4/site-packages/scipy/io/mio.py", line 724, in _get_element el, name = _parse_mimatrix(fid,numbytes) File "/usr/lib64/python2.4/site-packages/scipy/io/mio.py", line 575, in _parse_mimatrix result = squeeze(transpose(reshape(result,tupdims))) File "/usr/lib64/python2.4/site-packages/numpy/core/fromnumeric.py", line 62, in reshape return reshape(newshape, order=order) ValueError: total size of new array must be unchanged Traceback (most recent call last): File "/usr/lib64/python2.4/site-packages/scipy/io/tests/test_mio.py", line 79, in cc self._check_case(name, expected) File "/usr/lib64/python2.4/site-packages/scipy/io/tests/test_mio.py", line 69, in _check_case matdict = loadmat(f) File "/usr/lib64/python2.4/site-packages/scipy/io/mio.py", line 801, in loadmat thisdict = _loadv5(fid,basename) File "/usr/lib64/python2.4/site-packages/scipy/io/mio.py", line 739, in _loadv5 el, varname, unused = _get_element(fid, return_name_dtype=True) File "/usr/lib64/python2.4/site-packages/scipy/io/mio.py", line 724, in _get_element el, name = _parse_mimatrix(fid,numbytes) File "/usr/lib64/python2.4/site-packages/scipy/io/mio.py", line 643, in _parse_mimatrix rowind = _get_element(fid) File "/usr/lib64/python2.4/site-packages/scipy/io/mio.py", line 718, in _get_element el = fid.read(numbytes,miDataTypes[dtype][2],c_is_b=1) File "/usr/lib64/python2.4/site-packages/scipy/io/mio.py", line 209, in read raise ValueError, "When c_is_b is non-zero then " \ ValueError: When c_is_b is non-zero then count is bytes and must be multiple of basic size. Nils

2 2

Re: [SciPy-dev] [SciPy-user] Call for testing
by Nils Wagner Aug. 13, 2006

Aug. 13, 2006

Nils Wagner wrote: > On Sat, 12 Aug 2006 18:02:04 -0700 > Stephen Walton <stephen.walton(a)csun.edu> wrote: > >> Steve Lianoglou wrote: >> >> >>>> Thank you all for running the test ! >>>> >>>> Finally I have disabled ATLAS by >>>> export ATLAS=None >>>> >>>> Good news is that I get the correct result. >>>> So I guess it's definitely an ATLAS issue. >>>> >>>> >>>> >> Yes, but I think the real difficulty is ATLAS 3.6.0 vs. >> 3.7.11. I would >> like to see some kind of official statement, I suppose, >> about which >> version of ATLAS scipy builds best with. 3.6.0 is >> stable but very old; >> Clint Whaley is recommending use of the 3.7 series. The >> good news is >> that he has a grant to help pay him for the time it will >> take to get a >> new stable release out. Nils, it might be worth trying >> ATLAS 3.7.13, >> which has a completely new (and much improved) >> configuration, but READ >> THE DOCS first. Building 3.7.13 is very different from >> building any >> previous versions. >> >> Frankly, I need stability more than the last iota of >> speed right now, so >> I'm using the Fedora Extras 3.6.0 ATLAS binaries with >> Scipy, which gives >> adequate performance and scipy.test(1) finishes with no >> errors. >> >> Steve >> >> _______________________________________________ >> SciPy-user mailing list >> SciPy-user(a)scipy.org >> http://projects.scipy.org/mailman/listinfo/scipy-user >> > > Steve, > > I have used 3.7.11 and the problem is still open. > > Nils > _______________________________________________ > SciPy-user mailing list > SciPy-user(a)scipy.org > http://projects.scipy.org/mailman/listinfo/scipy-user > Hi all, The different results disappeared misteriously ! Something must happened to numpy/scipy between ATLAS 3.6.0 >>> scipy.__version__ '0.5.0.2147' >>> numpy.__version__ '1.0b2.dev2951' >>> and ATLAS 3.6.0 >>> numpy.__version__ '1.0b2.dev3005' >>> scipy.__version__ '0.5.0.2158' >>> Note that ATLAS has been retained unchanged !!! Nils

1 0

Fwd: 206 AstroPy moderator request(s) waiting
by Paul Barrett Aug. 8, 2006

Aug. 8, 2006

Can anyone on this list explain to me what is going on here? I am the primary adminstrator for this mailing list. I keep getting these messages sent to me. However, when I logon to the administrator's web page, none of these messages are there. -- Paul ---------- Forwarded message ---------- From: astropy-bounces(a)scipy.net <astropy-bounces(a)scipy.net> Date: Aug 8, 2006 9:00 AM Subject: 206 AstroPy moderator request(s) waiting To: astropy-owner(a)scipy.net The AstroPy(a)scipy.net mailing list has 206 request(s) waiting for your consideration at: http://www.scipy.net/mailman/admindb/astropy Please attend to this at your earliest convenience. This notice of pending requests, if any, will be sent out daily. Pending posts: From: qfoua(a)egm.lib.rochester.edu on Tue May 30 12:07:10 2006 Subject: Amazing Opportunity for Americans Cause: Post by non-member to a members-only list From: prugmi(a)dc12.petsmart.com on Tue May 30 12:08:24 2006 Subject: Quality Home Loans simplified Cause: Post by non-member to a members-only list [etc.]

2 1

SciPy 2006 LiveCD update
by Bryce Hendrix Aug. 7, 2006

Aug. 7, 2006

In order to prepare the LiveCD's, I need to build them from source tomorrow. Is anyone planning on demo'ing anything that has been added since the SciPy 0.5.0 and NumPy beta 1 releases? If all goes as expected, the LiveCD ISO will also be available Wednesday via bittorrent. Bryce

1 0

SciPy SVN does not work with NumPy SVN for a bit
by Travis Oliphant Aug. 5, 2006

Aug. 5, 2006

I'm aware that SciPy SVN does not work with NumPy SVN. This will be fixed by improving the use of oldnumeric in SciPy in a few hours unless somebody beats me to it. -Travis

1 0

scipy site will be back up real soon now
by Jeff Strunk Aug. 4, 2006

Aug. 4, 2006

Hello, The automatic update for apache had different behavior than the previous version. I am compiling a fixed version, so it should work again soon. Sorry for the inconvenience. Jeff Strunk IT Administrator Enthought, Inc.

1 0

Flop counter for numpy/scipy
by Nils Wagner Aug. 3, 2006

Aug. 3, 2006

Hi all, Is there a way to count flops in numpy/scipy ? I mean, how can I compare two algorithms ? Nils

2 1

New ISP
by Jeff Strunk Aug. 3, 2006

Aug. 3, 2006

Good Morning, I am pleased to announce that Enthought is now using a new ISP. We have a 10 megabit internet connection from our in building provider now. That is 6.6 times faster than our old T1. Downloads of Enthon and Scipy should be much faster now. If you find that you are connecting at slow speeds, it may be that your ISP's DNS cache has not recognized our DNS changes yet. Most should have changed within 20 minutes of the switchover. Some ISPs may take a day, and very few will take a few weeks. Thanks, Jeff Strunk IT Administrator Enthought, Inc.

1 0

Where to put data for tests?
by Matthew Brett Aug. 3, 2006

Aug. 3, 2006

Dear sci-pies, I am sorry if I have missed the obvious answer to this question, but... Some of us are working on unit tests for the scipy.io.loadmat routine. We would like to provide the tests with simple real examples of matlab format .mat files, generated by various versions of matlab. The questions are, where is the best place to put such files, and how should they best be plumbed into setup.py? Should they for example be package data? We had thought that a subdirectory of tests, called 'data' would be a good place for them. Does this seem sensible? Thanks a lot, Matthew

1 0

ANN: Python Enthought Edition 1.0.0 Released
by Bryce Hendrix Aug. 2, 2006

Aug. 2, 2006

Enthought is pleased to announce the release of Python Enthought Edition Version 1.0.0 (http://code.enthought.com/enthon/) -- a python distribution for Windows. About Python Enthought Edition: ------------------------------- Python 2.4.3, Enthought Edition is a kitchen-sink-included Python distribution for Windows including the following packages out of the box: Numpy SciPy IPython Enthought Tool Suite wxPython PIL mingw MayaVi Scientific Python VTK and many more... More information is available about all Open Source code written and released by Enthought, Inc. at http://code.enthought.com 1.0.0 Release Notes ------------------------- A lot of work has gone into testing this release, and it is our most stable release to date, but there are a couple of caveats: * The generated documentation index entries are missing. The full text search does work and the table of contents is complete, so this feature will be pushed to version 1.1.0. * IPython may cause problems when starting the first time if a previous version of IPython was ran. If you see "WARNING: could not import user config", either follow the directions which follow the warning. * Some users are reporting that older matplotlibrc files are not compatible with the version of matplotlib installed with this release. Please refer to the matplotlib mailing list (http://sourceforge.net/mail/?group_id=80706) for further help. We are grateful to everyone who has helped test this release. If you'd like to contribute or report a bug, you can do so at https://svn.enthought.com/enthought.

1 0