Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Default fill value dtype does not match that of data for masked arrays #5613

Open
jakirkham opened this issue Feb 27, 2015 · 0 comments
Open

Comments

@jakirkham
Copy link
Contributor

The fill value type chosen for integers is always int64 and always 999999 even when that doesn't make sense numpy.ma.MaskedArray.fill_value. For instance, take the type uint8. In this case, the fill value is way outside of bounds and ends up getting converted to 63. If the behavior must be preserved, then for uint8 the fill value should be 63 and it's dtype should be uint8. Alternatively, better fill values could be picked that work on a range of types (i.e. 0 for integers and nan for floats and complex) or something similar.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants