Re: [Numpy-discussion] min() of array containing NaN

at NaNs are unexpected, so it would be helpful to raise an Exception. Thanks for all of the helpful discussion on this issue. -- Thomas J. Duck <[EMAIL PROTECTED]> Associate Professor, Department of Physics and Atmospheric Science, Dalhousie University, Halifax, Nova Scotia, Canada

[Numpy-discussion] min() of array containing NaN

Determining the minimum value of an array that contains NaN produces a surprising result: >>> x = numpy.array([0,1,2,numpy.nan,4,5,6]) >>> x.min() 4.0 I expected 0.0. Is this the intended behaviour or a bug? I am using numpy 1.1.1. Thanks, Tom -- Thomas J. Duck

[Numpy-discussion] 0d array value comparisons

ut is at least workable. Are these the intended results? Thanks, Tom -- Thomas J. Duck <[EMAIL PROTECTED]> Associate Professor, Department of Physics and Atmospheric Science, Dalhousie University, Halifax, Nova Scotia, Canada, B3H 3J5. Tel: (902)494-1456 | Fax: (902)494-51

Re: [Numpy-discussion] Strange behavior for argsort() and take()

Thanks, Anne. I misinterpreted what argsort() provides. I was thinking about it in terms of the kind of behaviour exhibited by searchsorted(). --Tom -- On 18-Jun-08, at 12:10 PM, Anne Archibald wrote: > 2008/6/18 Thomas J. Duck <[EMAIL PROTECTED]>: > >> I

[Numpy-discussion] Strange behavior for argsort() and take()

xpected)! Can anyone shed some light on what is happening here for me? I have tested this on both my OS X/Fink and Debian/Lenny systems with the same result. Thanks, Tom -- Thomas J. Duck <[EMAIL PROTECTED]> Associate Professor, Department of Physics and Atmospheric Science, Dalhousie

[Numpy-discussion] Memory leak for in-place Numeric+numpy addition

Hi, There seems to be a memory leak when arrays are added in-place for mixed Numeric/numpy applications. For example, memory usage quickly ramps up when the following program is executed: import Numeric,numpy x = Numeric.zeros((2000,2000),typecode=Numeric.Float64) for j in range(200):