Re: [Numpy-discussion] np.histogram: upper range bin

2011-06-12 Thread Peter Butterworth
ition when using np.histogram(x): max(x) == top bin limit --- Re: [Numpy-discussion] np.histogram: upper range bin Christopher Barker Thu, 02 Jun 2011 09:19:16 -0700 Peter Butterworth wrote: > in np.histogram the top-most bin edge is inclusive of the upper range > limit. As documented in the doc

[Numpy-discussion] np.histogram: upper range bin

2011-06-02 Thread Peter Butterworth
ch *includes* 4. ''' -- thanks, peter butterworth ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion

Re: [Numpy-discussion] stable sort on a recarray ?

2011-03-29 Thread Peter Butterworth
is not mentioned on that page that lexsort is a stable sort. . no structured array / recarray example is given . it also states that "Structured arrays are sorted lexically by argsort", but fails to mention that the resulting sort is not stable. -- thanks, peter butterworth ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion

Re: [Numpy-discussion] np.dtype(int) 64bit

2010-10-24 Thread Peter Butterworth
ion argmin() returns an index, which is implemented as 'Py_ssize_t' in C and is 64 bit on all 64 bit systems. -- Christoph -- thanks, peter butterworth ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion

[Numpy-discussion] np.dtype(int) 64bit

2010-10-23 Thread Peter Butterworth
xpected result on 64 bit numpy is what I get on Ubuntu with np 2.0.0 dev : >>> np.dtype(int) dtype('int64') Could someone please confirm this ? -- thanks, peter butterworth ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion

[Numpy-discussion] mean of empty sequence gives nan

2010-09-27 Thread Peter Butterworth
In numpy 1.5.0, I got the following for mean of an empty sequence (or array): In [21]: mean([]) Warning: invalid value encountered in double_scalars Out[21]: nan Is this behaviour expected ? Also, would it be possible to have more explicit warning messages about the problem being related numpy