[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: handling NaN

From: Andy Adler
Subject: Re: handling NaN
Date: Wed, 31 Jul 2002 21:49:09 -0400 (EDT)

On Wed, 31 Jul 2002, John W. Eaton wrote:
> On 31-Jul-2002, Paul Kienzle <address@hidden> wrote:
> | Or you can use nanmax as defined in octave-forge (,
> | which does the same thing:
> I've also noticed that Matlab now removes NaN automatically in min and
> max (but apparently not yet in std, mean, etc.).  Although I would
> prefer to distinguish between missing and NaN, maybe Octave should
> ignore NaNs in min and max for compatibility?

I guess this is one of those "should octave do bug-for-bug compatibility?"
type questions.

My personal opinion is that min or max _should_ by default
retain NaN values. NaN normally means that something significant
happened. That significant event should be retained by default.
The choice to ignore NaN should be semantically explicit,
such as by using nanfunction.

If the octave-froge implementation of nanmax.m is too slow,
then we can always rewrite it as a *DLD function.

Andy Adler,                address@hidden

Octave is freely available under the terms of the GNU GPL.

Octave's home on the web:
How to fund new projects:
Subscription information:

reply via email to

[Prev in Thread] Current Thread [Next in Thread]