questions
questions > RE: dcm2nii converting resting state files error
Feb 6, 2017 10:02 PM | Kai-Chun Yang
RE: dcm2nii converting resting state files error
Dear Chris,
Thanks for developing such a nice tool!
I wonder how can I change the output nifti file to be saved as FLOAT 32 in dcm2niix?
The version I applied is "Chris Rorden's dcm2niiX version v1.0.20170130 (64-bit Linux)"
Thanks a lot!
Best regards,
KC
Originally posted by Chris Rorden:
3.) The standard NIfTI 16-bit data type is 16-bit SIGNED integers - this can losslessly encode values from -32768..+32767. This is typically fine, as most classic MRI systems use 12-bit ADC (range 0..4096). However, it is clear that your software is set up to convert to 16-bit UNSIGNED (0..65535). This is really way beyond the SNR expected for EPI data, but it poses a problem for true lossless conversion. In this situation my software provides you with two options:
a.) save as unsigned 16-bit integers (UINT16): this keeps the raw data from your scanner unchanged. However, this is a legal but atypical NIfTI data format so subsequent tools may fail.
b.) save as 32-bit floating point (FLOAT32): this is a standard format that has ample precision. However, the files will require twice as much disk space and will probably require more time to process.
Thanks for developing such a nice tool!
I wonder how can I change the output nifti file to be saved as FLOAT 32 in dcm2niix?
The version I applied is "Chris Rorden's dcm2niiX version v1.0.20170130 (64-bit Linux)"
Thanks a lot!
Best regards,
KC
Originally posted by Chris Rorden:
3.) The standard NIfTI 16-bit data type is 16-bit SIGNED integers - this can losslessly encode values from -32768..+32767. This is typically fine, as most classic MRI systems use 12-bit ADC (range 0..4096). However, it is clear that your software is set up to convert to 16-bit UNSIGNED (0..65535). This is really way beyond the SNR expected for EPI data, but it poses a problem for true lossless conversion. In this situation my software provides you with two options:
a.) save as unsigned 16-bit integers (UINT16): this keeps the raw data from your scanner unchanged. However, this is a legal but atypical NIfTI data format so subsequent tools may fail.
b.) save as 32-bit floating point (FLOAT32): this is a standard format that has ample precision. However, the files will require twice as much disk space and will probably require more time to process.
Threaded View
Title | Author | Date |
---|---|---|
landsmbarbara | Sep 4, 2015 | |
Chris Rorden | Sep 4, 2015 | |
Kai-Chun Yang | Feb 6, 2017 | |
Chris Rorden | Feb 7, 2017 | |
Kai-Chun Yang | Feb 9, 2017 | |
lucero pacheco | Sep 11, 2016 | |
Chris Rorden | Sep 14, 2016 | |
Chris Rorden | Sep 12, 2016 | |
landsmbarbara | Sep 7, 2015 | |