[Neuroimaging] Nibabel API change - always read as float

Matthew Brett matthew.brett at gmail.com
Tue Jul 7 01:27:35 CEST 2015

On Tue, Jul 7, 2015 at 12:19 AM, Alexandre ABRAHAM
<abraham.alexandre at gmail.com> wrote:
> On Tue, Jul 7, 2015 at 1:08 AM, Brendan Moloney <moloney at ohsu.edu> wrote:
>> Sorry, I could be a bit more diplomatic some times. I don't mean to
>> discourage anyone from participating in the conversation.
> Don't worry, you were diplomatic enough ;). What I meant is that we clearly
> have two sides here: people who consider nifti data as intrinsically float,
> and people who think that the type is actually meaningful.

I think I missed the argument for this.

Don't forget the the output dtype is not the dtype as specified in the
header, but the dtype as specified in the header then cast to float if
the slope == 1 and offset == 0.

Sometimes I suppose this might be the algorithm intended by the author
of the image, but most of the time the author had no such intention.
They usually just meant to find a good datatype to keep a smaller data
size on disk.  Do you disagree?    I can show you lots of OpenFMRI
images where I think that is clearly the case.



More information about the Neuroimaging mailing list