Re: [Numpy-discussion] Faster

2008-05-05 Thread Damian Eads
Hi, Looks like a fun discussion: it's too bad for me I did not join it earlier. My first try at scipy-cluster was completely in Python. Like you, I also tried to find the most efficient way to transform the distance matrix when joining two clusters. Eventually my data sets became big enough t

Re: [Numpy-discussion] MoinMoin <-> docstrings gateway

2008-05-05 Thread dieter h
On Mon, May 5, 2008 at 1:48 AM, Gael Varoquaux <[EMAIL PROTECTED]> wrote: > On Mon, May 05, 2008 at 03:17:20AM +0300, Pauli Virtanen wrote: > > Some time ago there was discussion about MoinMoin <-> docstrings > > gateway. Did it produce some results? > > My girlfriend, Emmanuelle, (Cced, I am no

Re: [Numpy-discussion] Compilation problems - bizzare

2008-05-05 Thread Charles R Harris
On Mon, May 5, 2008 at 5:33 PM, Thomas Hrabe <[EMAIL PROTECTED]> wrote: > Hi all, > > currently, I am writing a box of modular functions for exchanging python & > matlab objects (nd arrays in particular). > I am facing an odd problem which I can not explain to myself: > > I use > PyArg_ParseTuple

Re: [Numpy-discussion] Compilation problems - bizzare

2008-05-05 Thread Robert Kern
On Mon, May 5, 2008 at 6:33 PM, Thomas Hrabe <[EMAIL PROTECTED]> wrote: > > Hi all, > > currently, I am writing a box of modular functions for exchanging python & > matlab objects (nd arrays in particular). > I am facing an odd problem which I can not explain to myself: > > I use > PyArg_ParseT

[Numpy-discussion] Compilation problems - bizzare

2008-05-05 Thread Thomas Hrabe
Hi all, currently, I am writing a box of modular functions for exchanging python & matlab objects (nd arrays in particular). I am facing an odd problem which I can not explain to myself: I use PyArg_ParseTuple(args, "O!s",&PyArray_Type, &array,&na) for parsing the array and a string. This funct

Re: [Numpy-discussion] Debian Lenny switches to Python 2.5 default

2008-05-05 Thread Robert Kern
On Mon, May 5, 2008 at 2:56 PM, Keith Goodman <[EMAIL PROTECTED]> wrote: > I'm the click of a botton away from changing the python default on my > Debian Lenny system from 2.4 to 2.5. Has anyone experienced any numpy > issues after the switch? 2.4 -> 2.5 in general shouldn't be a problem. If you

Re: [Numpy-discussion] numpy masked array oddity

2008-05-05 Thread Pierre GM
On Monday 05 May 2008 15:35:35 Eric Firing wrote: > What I meant was that I don't see that such a ravelled version of a > matrix would be likely to make sense in a linear algebra context, so > leaving it as a matrix is likely to cause confusion rather than > convenience. Still, it would be consist

Re: [Numpy-discussion] Debian Lenny switches to Python 2.5 default

2008-05-05 Thread Angus McMorland
2008/5/5 Keith Goodman <[EMAIL PROTECTED]>: > I'm the click of a botton away from changing the python default on my > Debian Lenny system from 2.4 to 2.5. Has anyone experienced any numpy > issues after the switch? All normal here so far, with most of a day's use. All numpy tests pass, and I ge

[Numpy-discussion] Debian Lenny switches to Python 2.5 default

2008-05-05 Thread Keith Goodman
I'm the click of a botton away from changing the python default on my Debian Lenny system from 2.4 to 2.5. Has anyone experienced any numpy issues after the switch? ___ Numpy-discussion mailing list Numpy-discussion@scipy.org http://projects.scipy.org/mai

Re: [Numpy-discussion] numpy masked array oddity

2008-05-05 Thread Eric Firing
Pierre GM wrote: > On Monday 05 May 2008 15:10:56 Eric Firing wrote: >> Pierre GM wrote: >>> * An alternative would be to force the output of MaskedArray.compressed() >>> to type(MaskedArray._baseclass), where the _baseclass attribute is the >>> class of the underlying array: usually it's only ndar

Re: [Numpy-discussion] numpy masked array oddity

2008-05-05 Thread Pierre GM
On Monday 05 May 2008 15:10:56 Eric Firing wrote: > Pierre GM wrote: > > * An alternative would be to force the output of MaskedArray.compressed() > > to type(MaskedArray._baseclass), where the _baseclass attribute is the > > class of the underlying array: usually it's only ndarray, but it can be >

Re: [Numpy-discussion] numpy masked array oddity

2008-05-05 Thread Eric Firing
Pierre GM wrote: > On Monday 05 May 2008 13:19:40 Russell E. Owen wrote: >> The object returned by maskedArray.compressed() appears to be a normal >> numpy array (based on repr output), but in reality it has some >> surprising differences: > > Russell: > > * I assume you're not using the latest v

Re: [Numpy-discussion] Deprecating PyDataMem_RENEW ?

2008-05-05 Thread Robert Kern
On Mon, May 5, 2008 at 1:30 PM, David Cournapeau <[EMAIL PROTECTED]> wrote: > On Tue, May 6, 2008 at 2:11 AM, Robert Kern <[EMAIL PROTECTED]> wrote: > > > > I am in favor of at least trying this out. We will have to have a set > > of benchmarks to make sure we haven't hurt the current uses of

Re: [Numpy-discussion] Deprecating PyDataMem_RENEW ?

2008-05-05 Thread Anne Archibald
2008/5/5 Robert Kern <[EMAIL PROTECTED]>: > On Mon, May 5, 2008 at 7:44 AM, David Cournapeau > <[EMAIL PROTECTED]> wrote: > > > In numpy, we can always replace realloc by malloc/free, because we know > > the size of the old block: would deprecating PyMemData_RENEW and > > replacing them by Py

Re: [Numpy-discussion] Deprecating PyDataMem_RENEW ?

2008-05-05 Thread David Cournapeau
On Tue, May 6, 2008 at 2:11 AM, Robert Kern <[EMAIL PROTECTED]> wrote: > > I am in favor of at least trying this out. We will have to have a set > of benchmarks to make sure we haven't hurt the current uses of > PyMemData_RENEW which Tim points out. What would be a good stress test for PyArray_

Re: [Numpy-discussion] Deprecating PyDataMem_RENEW ?

2008-05-05 Thread David Cournapeau
On Tue, May 6, 2008 at 1:59 AM, Timothy Hochberg <[EMAIL PROTECTED]> wrote: > I don't think you would want to do this in the core of PyArray_FromIter; > presumably realloc can sometimes reuse the existing pointer and save on > allocating a new chunk of memory. Since there are lots of allocations i

Re: [Numpy-discussion] numpy masked array oddity

2008-05-05 Thread Pierre GM
On Monday 05 May 2008 13:19:40 Russell E. Owen wrote: > The object returned by maskedArray.compressed() appears to be a normal > numpy array (based on repr output), but in reality it has some > surprising differences: Russell: * I assume you're not using the latest version of numpy, are you ? If

Re: [Numpy-discussion] numpy masked array oddity

2008-05-05 Thread Christopher Barker
Robert Kern wrote: > I don't know the reason why it's not an ndarray, but you don't have to > copy the data again to get one: > > c = ma.compressed().view(numpy.ndarray) would: c - numpy.asarray(ma.compressed()) work too? -CHB -- Christopher Barker, Ph.D. Oceanographer Emergency Respons

Re: [Numpy-discussion] numpy masked array oddity

2008-05-05 Thread Robert Kern
On Mon, May 5, 2008 at 12:19 PM, Russell E. Owen <[EMAIL PROTECTED]> wrote: > The object returned by maskedArray.compressed() appears to be a normal > numpy array (based on repr output), but in reality it has some > surprising differences: > > import numpy > a = numpy.arange(10, dtype=int) > b

Re: [Numpy-discussion] Learn about numpy

2008-05-05 Thread Nadav Horesh
I think you have a problem of overflow in r5: You may better use utin64 instead of uint32. Nadav. -הודעה מקורית- מאת: [EMAIL PROTECTED] בשם Folkert Boonstra נשלח: ב 05-מאי-08 19:17 אל: Discussion of Numerical Python נושא: Re: [Numpy-discussion] Learn about numpy Folkert Boonstra sc

[Numpy-discussion] numpy masked array oddity

2008-05-05 Thread Russell E. Owen
The object returned by maskedArray.compressed() appears to be a normal numpy array (based on repr output), but in reality it has some surprising differences: import numpy a = numpy.arange(10, dtype=int) b = numpy.zeros(10) b[1] = 1 b[3] = 1 ma = numpy.core.ma.array(a, mask=b, dtype=float) print

Re: [Numpy-discussion] numpy in RHEL4

2008-05-05 Thread Robert Kern
On Mon, May 5, 2008 at 6:14 AM, Bala subramanian <[EMAIL PROTECTED]> wrote: > Dear friends, > > I am trying to install numpy version numpy-1.0.4 in RHEL 4. My python > version is 2.3.4. While installation, it throws me the following error and > stops. Kindly write me how to get rid of this. The f

Re: [Numpy-discussion] Deprecating PyDataMem_RENEW ?

2008-05-05 Thread Robert Kern
On Mon, May 5, 2008 at 7:44 AM, David Cournapeau <[EMAIL PROTECTED]> wrote: > In numpy, we can always replace realloc by malloc/free, because we know > the size of the old block: would deprecating PyMemData_RENEW and > replacing them by PyMemeData_NEW/PyMemData_FREE be possible, such as to > ma

Re: [Numpy-discussion] Deprecating PyDataMem_RENEW ?

2008-05-05 Thread Timothy Hochberg
On Mon, May 5, 2008 at 5:44 AM, David Cournapeau < [EMAIL PROTECTED]> wrote: > Hi, > >While working again on the fftpack module, to clean things up and > speed some backends (in particular fftw3, which is really sub-optimal > right now), I remembered how much unaligned data pointer in numpy ar

Re: [Numpy-discussion] Learn about numpy

2008-05-05 Thread Folkert Boonstra
Folkert Boonstra schreef: > Nadav Horesh schreef: > >> What you do here is a convolution with >> >> 0 1 0 >> 1 1 1 >> 0 1 0 >> >> kernel, and thresholding, you can use numpy.numarray.nd_image package: >> >> import numpy.numarray.nd_image as NI >> . >> . >> . >>ker = array([[0,1,0], [1,1,1],

[Numpy-discussion] Deprecating PyDataMem_RENEW ?

2008-05-05 Thread David Cournapeau
Hi, While working again on the fftpack module, to clean things up and speed some backends (in particular fftw3, which is really sub-optimal right now), I remembered how much unaligned data pointer in numpy arrays hurt performances. So I would like to relaunch the discussion on aligned allo

[Numpy-discussion] numpy in RHEL4

2008-05-05 Thread Bala subramanian
Dear friends, I am trying to install numpy version numpy-1.0.4 in RHEL 4. My python version is 2.3.4. While installation, it throws me the following error and stops. Kindly write me how to get rid of this. Thanks, Bala -

Re: [Numpy-discussion] Learn about numpy

2008-05-05 Thread Folkert Boonstra
Nadav Horesh schreef: > What you do here is a convolution with > > 0 1 0 > 1 1 1 > 0 1 0 > > kernel, and thresholding, you can use numpy.numarray.nd_image package: > > import numpy.numarray.nd_image as NI > . > . > . >ker = array([[0,1,0], [1,1,1],[0,1,0]]) >result = (NI.convolve(self.bufb

[Numpy-discussion] [IT] Weekend outage complete

2008-05-05 Thread Peter Wang
Hi everyone, The downtime took a little longer than expected (perhaps that is to be expected?), but everything should be back up and running now. Mail, web, SVN, and Trac for scipy.org and enthought.com are all functional. The mail server is working through some backlogged mail but that

Re: [Numpy-discussion] strict aliasing?

2008-05-05 Thread David Cournapeau
Charles R Harris wrote: > > Interesting article. I note that it is OK to alias pointers to the > signed and unsigned versions of integer types, which is where I must > have picked up my notions about length. I don't recall seeing any > major bit of software that didn't use the -fno-strict-aliasi