[Neuroimaging] Nibabel API change - always read as float

Nate Vack njvack at wisc.edu
Tue Jul 7 18:30:36 CEST 2015

On Mon, Jul 6, 2015 at 6:28 PM Gael Varoquaux <gael.varoquaux at normalesup.org>

You cannot do numerics without being aware of dtype and overflow.
> Seriously.

When 75% of your files are natively stored as floats, but for some reason
the 25% of them are shorts, it's remarkably easy to not notice that
Something Bad has quietly happened, until you go and look at all the output
files and say "wait, what?"

Yes, I know that situation is not supposed to happen (and I could have
avoided it by running a data type report before doing computation), but
there are delightful surprises in datasets. Even when you're aware of these
things, they're still lurking with their sharp pointy teeth.

The ultimate answer to "what is the least surprising behavior?" is
complicated and probably depends on your normal use cases. For me, it's
default conversion to float.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/neuroimaging/attachments/20150707/981ec63a/attachment.html>

More information about the Neuroimaging mailing list