x.min() depends on ordering

Keith Goodman kwgoodman at gmail.com
Sat Nov 11 18:25:12 EST 2006


On 11/11/06, Robert Kern <robert.kern at gmail.com> wrote:

> Barring a clever solution (at least cleverer than I feel like being
> immediately), the way to solve this would be to check for nans in the array and
> deal with them separately (or simply ignore them in the case of x.min()).
> However, this checking would slow down the common case that has no nans
> (sans nans, if you will).

I'm not one of the fans of sans nans.

I'd prefer a slower min() that ignored nans. But I'm probably in the minority.

How about a nanmin() function?

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642




More information about the NumPy-Discussion mailing list