Re: [Numpy-discussion] loadtxt error

2008-09-23 Thread Joshua Lippai
David said the bug was fixed in the trunk, which you don't have; the development state of the main source code, or the trunk, is the latest state available, and releases are always a bit behind trunk since it would be kind of ridiculous to make a new release every time someone commits a change. You

Re: [Numpy-discussion] performance of the numpy

2008-09-23 Thread David Cournapeau
frank wang wrote: > Hi, I am new user from matlab world. So I always compare with matlab. > in my code, i have a large array with about 10 data. when I perform > > c=fft(b) > d=abs(c) > plot(d) > > I got good response. however, when i try to execute: > plot(abs(fft(b))) Can you post the ex

Re: [Numpy-discussion] performance of the numpy

2008-09-23 Thread Nadav Horesh
You should use absolute (a ufunc) and not abs (internal python function): >>> plot(absolute(fft(b))) Nadav. -הודעה מקורית- מאת: [EMAIL PROTECTED] בשם frank wang נשלח: ד 24-ספטמבר-08 08:21 אל: Discussion of Numerical Python נושא: [Numpy-discussion] performance of the numpy Hi, I am n

[Numpy-discussion] performance of the numpy

2008-09-23 Thread frank wang
Hi, I am new user from matlab world. So I always compare with matlab. in my code, i have a large array with about 10 data. when I perform c=fft(b) d=abs(c) plot(d) I got good response. however, when i try to execute: plot(abs(fft(b))) it takes forever and i have to kill the operation.

Re: [Numpy-discussion] loadtxt error

2008-09-23 Thread frank wang
My numpy version is 1.1.1. I just downloaded and installed. It is the same result. Also, when I use the list, I got similar error said list does not have the find command. ---> 14 fid=loadtxt(fname,comments='"',dtype='|S4',converters={cols:lambda s:int(s,16)},usecols=[cols]) 15 16

Re: [Numpy-discussion] loadtxt error

2008-09-23 Thread frank wang
My numpy version is numpy-1.1.1-win32-superpack-python2.5.exe. It is the newest release. By the way, in Python, how can I check numpy version? Thanks Frank Date: Tue, 23 Sep 2008 08:42:00 -0400From: [EMAIL PROTECTED]: [EMAIL PROTECTED]: Re: [Numpy-discussion] loadtxt error This bug has bee

Re: [Numpy-discussion] python 2.4 incompatibility in numpy.lookfor in numpy 1.2.0rc2

2008-09-23 Thread joep
On Sep 23, 6:48 pm, joep <[EMAIL PROTECTED]> wrote: > A possible solution would be in > > http://bazaar.launchpad.net/~pauli-virtanen/scipy/pydocweb/revision/386 > > It seems to be possible to be used in the same way when iter_modules > is not available. > The usage in ``_lookfor_generate_cache``

Re: [Numpy-discussion] python 2.4 incompatibility in numpy.lookfor in numpy 1.2.0rc2

2008-09-23 Thread joep
A possible solution would be in http://bazaar.launchpad.net/~pauli-virtanen/scipy/pydocweb/revision/386 It seems to be possible to be used in the same way when iter_modules is not available. The usage in ``_lookfor_generate_cache`` in lib/utils.py looks almost exactly the same as in the above re

Re: [Numpy-discussion] np.min(np.inf,1000) == np.inf

2008-09-23 Thread Robert Kern
On Tue, Sep 23, 2008 at 15:34, joep <[EMAIL PROTECTED]> wrote: > I just fell over this: > np.min(np.inf,1000) > 1.#INF min(np.inf,1000) > 1000 > np.max(-np.inf,1000) > -1.#INF max(-np.inf,1000) > 1000 > > Is this known behavior? It is known that that's not the API of numpy.min(

Re: [Numpy-discussion] python 2.4 incompatibility in numpy.lookfor in numpy 1.2.0rc2

2008-09-23 Thread Jarrod Millman
On Tue, Sep 23, 2008 at 1:35 PM, Robert Kern <[EMAIL PROTECTED]> wrote: > On Tue, Sep 23, 2008 at 15:18, joep <[EMAIL PROTECTED]> wrote: >> Hi, >> I was trying to use lookfor on python 2.4 and got an exception with >> np.lookfor because of a missing method in pkgutil that was added in >> python 2.5

Re: [Numpy-discussion] python 2.4 incompatibility in numpy.lookfor in numpy 1.2.0rc2

2008-09-23 Thread Robert Kern
On Tue, Sep 23, 2008 at 15:18, joep <[EMAIL PROTECTED]> wrote: > Hi, > I was trying to use lookfor on python 2.4 and got an exception with > np.lookfor because of a missing method in pkgutil that was added in > python 2.5. Hmmm. Unfortunately, that's an intrinsic part of the lookfor() functionalit

[Numpy-discussion] np.min(np.inf,1000) == np.inf

2008-09-23 Thread joep
I just fell over this: >>> np.min(np.inf,1000) 1.#INF >>> min(np.inf,1000) 1000 >>> np.max(-np.inf,1000) -1.#INF >>> max(-np.inf,1000) 1000 Is this known behavior? I finally realized, that I have to do this (the doc string says array like) >>> np.min([np.inf,1000]) 1000.0 >>> np.max([-np.inf,10

[Numpy-discussion] python 2.4 incompatibility in numpy.lookfor in numpy 1.2.0rc2

2008-09-23 Thread joep
Hi, I was trying to use lookfor on python 2.4 and got an exception with np.lookfor because of a missing method in pkgutil that was added in python 2.5. see the following session >>> np.lookfor('range') Traceback (most recent call last): File "", line 1, in ? np.lookfor('range') File "C:\P

Re: [Numpy-discussion] New patch for new mgrid / ogrid functionality

2008-09-23 Thread Gael Varoquaux
On Tue, Sep 23, 2008 at 07:41:17PM +0200, Stéfan van der Walt wrote: > That's a great way to fix the problem: if we call it `grid`, we can > turn it into a function and accept the more generic arguments, whilst > having keywords to choose between open and meshed grids. If you make it a function yo

Re: [Numpy-discussion] New patch for new mgrid / ogrid functionality

2008-09-23 Thread Gael Varoquaux
On Tue, Sep 23, 2008 at 09:39:53AM +0200, David Kaplan wrote: > I would note that there is nothing in the API breakage that prevents > doing what Gael mentions. The only change is that: > > > X = mgrid[0:4, 0:4, 0:4] > would be replaced with: > X = asarray( mgrid[ 0:4, 0:4, 0:4 ] ) Doesn't thi

Re: [Numpy-discussion] New patch for new mgrid / ogrid functionality

2008-09-23 Thread Stéfan van der Walt
2008/9/23 Robert Kern <[EMAIL PROTECTED]>: > The only time it would need to return a list is with the new > functionality. So expose the new functionality with a different object > instead of cramming it into an existing object with an incompatible > API. That's a great way to fix the problem: if

Re: [Numpy-discussion] New patch for new mgrid / ogrid functionality

2008-09-23 Thread Robert Kern
On Tue, Sep 23, 2008 at 02:39, David Kaplan <[EMAIL PROTECTED]> wrote: > Hi, > > I would note that there is nothing in the API breakage that prevents > doing what Gael mentions. The only change is that: > >> > X = mgrid[0:4, 0:4, 0:4] > > would be replaced with: > > X = asarray( mgrid[ 0:4, 0:4, 0

Re: [Numpy-discussion] loadtxt error

2008-09-23 Thread David Huard
This bug has been fixed in the trunk a couple of weeks ago. Cheers, David On Mon, Sep 22, 2008 at 8:10 PM, Pierre GM <[EMAIL PROTECTED]> wrote: > On Monday 22 September 2008 19:56:47 frank wang wrote: > > This error is caused that the usecols is a tuple and it does not have > find > > command.

Re: [Numpy-discussion] complex roots() segfault on Solaris 10/x86 with numpy 1.2.rc1 using python 2.5.2

2008-09-23 Thread David Cournapeau
Michael Abshoff wrote: > > So it looks like gfortran 4.2.4 on Solaris + "-O3" miscompiles lapack, > which is honestly unbelievable considering netlib.org lapack+BLAS are > the yard stick for any Fortran compiler. > Well, not many people use gfortran on Solaris, I would guess. Another problem

Re: [Numpy-discussion] complex roots() segfault on Solaris 10/x86 with numpy 1.2.rc1 using python 2.5.2

2008-09-23 Thread Michael Abshoff
David Cournapeau wrote: > Michael Abshoff wrote: Hi David, >> Sorry for not being precise: Both python and numpy have been build with >> >> OPT=-DNDEBUG -g -O0 -fwrapv -Wall -Wstrict-prototypes > > Hm, strange. I don't know why you can't get any debug info, then. well, it looks like some sort o

Re: [Numpy-discussion] New patch for new mgrid / ogrid functionality

2008-09-23 Thread David Kaplan
Hi, I would note that there is nothing in the API breakage that prevents doing what Gael mentions. The only change is that: > > X = mgrid[0:4, 0:4, 0:4] would be replaced with: X = asarray( mgrid[ 0:4, 0:4, 0:4 ] ) On the other hand, not making this change makes for a strange and ugly impleme