headers
Ian Mallett | 1 Aug 01:01
Picon

Re: Is this a bug?

Awww, it's fun to be foolish on Fridays!

_______________________________________________
NumPy-Discussion mailing list
NumPy-Discussion <at> scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion
Permalink | Reply | 0 comments |
headers
David Cournapeau | 1 Aug 06:14
Picon

Re: ** On entry to ILAENV parameter number 2 had an illegal value

On Fri, Jul 31, 2009 at 8:20 PM, David
Cournapeau<david <at> ar.media.kyoto-u.ac.jp> wrote:
> Steven Coutts wrote:
>> David Cournapeau <david <at> ar.media.kyoto-u.ac.jp> writes:
>>
>>  If you are willing to do
>>
>>> it, I would  also be interested whether numpy works ok if linked against
>>> BLAS/LAPACK instead of atlas (i.e. build numpy, again from scratch, with
>>> ATLAS=None python setup.py build, and then run the test suite).
>>>
>>>
>>
>> Yes that appears to work fine, all tests run.
>>
>
> So that's a problem with ATLAS. Maybe a gcc bug ? Another user contacted
> me privately for my rpm repository, and got exactly the same problem
> with the rpms, on CENTOS 5.3 as well. I will try to look at it on a
> centos VM if I have time this WE,

Ok, I have installed CENTOS 5.3 on my machine (kudos to vmware fusion
which installs the OS automatically), build numpy 1.3.0 with atlas
3.8.3 + lapack 3.1.1 on 64 bits. But I could not reproduce the bug,
unfortunately. Are you using the threaded atlas ?

cheers,

David
_______________________________________________
NumPy-Discussion mailing list
NumPy-Discussion <at> scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion
Permalink | Reply | 6 comments |
headers
David Cournapeau | 1 Aug 06:15
Picon

Re: ** On entry to ILAENV parameter number 2 had an illegal value

On Sat, Aug 1, 2009 at 1:14 PM, David Cournapeau<cournape <at> gmail.com> wrote:
> On Fri, Jul 31, 2009 at 8:20 PM, David
> Cournapeau<david <at> ar.media.kyoto-u.ac.jp> wrote:
>> Steven Coutts wrote:
>>> David Cournapeau <david <at> ar.media.kyoto-u.ac.jp> writes:
>>>
>>>  If you are willing to do
>>>
>>>> it, I would  also be interested whether numpy works ok if linked against
>>>> BLAS/LAPACK instead of atlas (i.e. build numpy, again from scratch, with
>>>> ATLAS=None python setup.py build, and then run the test suite).
>>>>
>>>>
>>>
>>> Yes that appears to work fine, all tests run.
>>>
>>
>> So that's a problem with ATLAS. Maybe a gcc bug ? Another user contacted
>> me privately for my rpm repository, and got exactly the same problem
>> with the rpms, on CENTOS 5.3 as well. I will try to look at it on a
>> centos VM if I have time this WE,
>
> Ok, I have installed CENTOS 5.3 on my machine (kudos to vmware fusion
> which installs the OS automatically), build numpy 1.3.0 with atlas
> 3.8.3 + lapack 3.1.1 on 64 bits. But I could not reproduce the bug,
> unfortunately. Are you using the threaded atlas ?

I forgot: another thing which would be helpful since you can reproduce
the bug would be to build a debug version of numpy (python setup.py
build_ext -g), and reproduce the bug under gdb to have a traceback.

David
_______________________________________________
NumPy-Discussion mailing list
NumPy-Discussion <at> scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion
Permalink | Reply | 5 comments |
headers
Scott Sinclair | 1 Aug 11:16
Picon
Gravatar

Doc-editor internal error

Hi,

I'm seeing "500 Internal Error" at http://docs.scipy.org/numpy/stats/

Cheers,
Scott
Permalink | Reply | 1 comment |
headers
Scott Sinclair | 1 Aug 11:33
Picon
Gravatar

Re: Doc-editor internal error

Ignore the noise. Seems to be fixed now..

2009/8/1 Scott Sinclair <scott.sinclair.za <at> gmail.com>:
> Hi,
>
> I'm seeing "500 Internal Error" at http://docs.scipy.org/numpy/stats/
>
> Cheers,
> Scott
>
Permalink | Reply | 0 comments |
headers
Gerard Vermeulen | 2 Aug 17:14
Picon

PyQwt-5.2.0 released

What is PyQwt ( http://pyqwt.sourceforge.net ) ?

- it is a set of Python bindings for the Qwt C++ class library which
  extends the Qt framework with widgets for scientific and engineering
  applications.   It provides a 2-dimensional plotting widget and
  various widgets to display and control bounded or unbounded floating
  point values.

- it requires and extends PyQt, a set of Python bindings for Qt.

- it supports the use of PyQt, Qt, Qwt, and optionally NumPy or SciPy
  in a GUI Python application or in an interactive Python session.

- it runs on POSIX, Mac OS X and Windows platforms (practically any
  platform supported by Qt and Python).

- it plots fast: fairly good hardware allows a rate of 100,000
  points/second. (PyQwt with Qt-3 is faster than with Qt-4).

- it is licensed under the GPL with an exception to allow dynamic
  linking with non-free releases of Qt and PyQt. 

The most important new features of PyQwt v5.2.0 are:
- support for Qwt v5.2.0
- support for PyQt4 upto v4.5.4, PyQt3 upto v3.18.1, and SIP upto
  v4.8.2.
- switch to documentation generated by Sphinx.
- provide a normal qwt plugin for the pyuic4 user interface compiler
  instead of the anormal qwt plugin included in PyQt. 

The most important bug fixes in PyQwt-5.2.0 are:
- fixed crashes in the QImage-array conversion functions.
- fixed three transfer of ownership bugs.

PyQwt-5.2.0 supports:
1. Python v2.6.x and v2.5.x.
2. PyQt v3.18.1 downto v3.17.5.
3  PyQt v4.5.x, v4.4.x.
4  SIP v4.8.x downto v4.7.3.
5. Qt v3.3.x.
6. Qt v4.5.x, v4.4.x, and v4.3.x.
7. Qwt v5.2.x, v5.1.x, and v5.0.x.
8. Recent versions of NumPy, numarray, and/or Numeric.

Enjoy -- Gerard Vermeulen
Permalink | Reply | 0 comments |
headers
David Warde-Farley | 3 Aug 08:12
Picon
Favicon
Gravatar

Re: Differences Between Arrays and Matrices in Numpy

On 30-Jul-09, at 1:14 PM, Nanime Puloski wrote:

> What are some differences between arrays and matrices using the Numpy
> library? When would one want to use arrays instead of matrices and  
> vice
> versa?

This is answered in the online documentation in several places:

http://preview.tinyurl.com/n6of54
http://docs.scipy.org/doc/numpy/reference/arrays.classes.html#matrix-objects

Regards,

David
Permalink | Reply | 0 comments |
headers
Steven Coutts | 3 Aug 10:30

Re: ** On entry to ILAENV parameter number 2 had an illegal value

David Cournapeau <cournape <at> gmail.com> writes:

> 
> I forgot: another thing which would be helpful since you can reproduce
> the bug would be to build a debug version of numpy (python setup.py
> build_ext -g), and reproduce the bug under gdb to have a traceback.
> 
> David

Ok I have rebuilt numpy-1.3.0 with debugging, and it segfaults as soon as I
import numpy in python2.5

Backtrace -:
http://pastebin.com/d27fbd2a5

Regards
Permalink | Reply | 4 comments |
headers
Steven Coutts | 3 Aug 10:35

Re: ** On entry to ILAENV parameter number 2 had an illegal value

Steven Coutts <stevec <at> couttsnet.com> writes:

> 
> Ok I have rebuilt numpy-1.3.0 with debugging, and it segfaults as soon as I
> import numpy in python2.5
> 
> Backtrace -:
> http://pastebin.com/d27fbd2a5
> 
> Regards
> 

Sorry ignore this, I cleanded out numpy properly, re-installed 1.3.0 and the
tests are all running now.

Regards
Permalink | Reply | 3 comments |
headers
David Cournapeau | 3 Aug 10:26
Picon
Picon

Re: ** On entry to ILAENV parameter number 2 had an illegal value

Steven Coutts wrote:
>
>
> Sorry ignore this, I cleanded out numpy properly, re-installed 1.3.0 and the
> tests are all running now.
>   

Do you mean that if you build with debug information, everything else
being equal, you cannot reproduce the crashes ?

cheers,

David
Permalink | Reply | 2 comments |

Gmane