[SciPy-dev] Statistics toolbox and nans
pearu at cens.ioc.ee
Fri Nov 1 08:54:04 CST 2002
On 1 Nov 2002, A.J. Rossini wrote:
> >>>>> "travis" == Travis Oliphant <oliphant.travis at ieee.org> writes:
> travis> Hello developers.
> travis> What should we do about nan's and the stats toolbox. Stats is one
> travis> package where people may use nans to represent missing values.
> Yech. This is a hard issue, but NAN isn't the solution.
I think so too that using NANs for representing missing values cannot be
reliable. There's too much weirdness going on with NaNs depending on the
local C library. For example, on linux
while on Windows nan==1 returns 0, as I have been told. See
Tim Peters has been explained these NAN issues several times on the
Usenet, google for 'Tim Peters NaN'.
Since "all IEEE-754 behavior visible from Python is a platform-dependent
accident" [T.P.], I don't see that NaNs could be used in SciPy for
anything useful in an platform independent way. I would avoid using NaNs
and Infs as much as possible until they become less platform-dependent,
may be by implementing special objects for Python instead of using
float('nan'), float('inf') (that even should not work on Win32).
More information about the Scipy-dev