AFNI Message Board

Dear AFNI users-

We are very pleased to announce that the new AFNI Message Board framework is up! Please join us at:

https://discuss.afni.nimh.nih.gov

Existing user accounts have been migrated, so returning users can login by requesting a password reset. New users can create accounts, as well, through a standard account creation process. Please note that these setup emails might initially go to spam folders (esp. for NIH users!), so please check those locations in the beginning.

The current Message Board discussion threads have been migrated to the new framework. The current Message Board will remain visible, but read-only, for a little while.

Sincerely, AFNI HQ

History of AFNI updates  

Previous Message Next Message
Message List New Topic Print View
|
Daniel Glen
April 21, 2009 12:27PM
Rick and I took a quick look at this problem. The problem is your input datasets are scaled bytes Analyze files; values stored as 255 are scaled down to 1 in this case. Writing out to NIFTI will use NIFTI if the data is determined to be non-integral. So a value of 0.99999 is not an integer, and a float type is assigned. You can work around this issue by either removing scale factors from the data input or the output with -nscale as in this example:

3dcalc -datum byte -nscale -a dset.hdr -expr 'int(a+0.5)' -prefix dset_byte
Reply Quote
RSS
Subject Author Posted

3dAllineate's output datatype not matching source

Terry Nycum April 20, 2009 07:25PM

Re: 3dAllineate's output datatype not matching source

Daniel Glen April 21, 2009 12:27PM