[Numpy-discussion] bug with with fill_values in masked arrays?

Pierre GM pgmdevlist@gmail....
Thu Mar 20 19:24:01 CDT 2008

On Thursday 20 March 2008 19:06:32 Chris Withers wrote:

> > the second element in the array iteration here is actually the
> > numpy.ma.masked constant, which always has the same fill value (which I
> > guess is 999999).
> This sucks to the point of feeling like a bug :-(

It is not.

> Why is it desirable for it to behave like this?

Because that way, you can compare anything to masked and see whether a value 
is masked or not. Anyway, in your case, it's just mean your value is masked. 
You don't care about the filling_value for this one.

More information about the Numpy-discussion mailing list