processing-scripts > converts NIFTI_datatype=4 (INT16) to float
Showing 1-4 of 4 posts
May 30, 2014 01:05 AM | peter lee
converts NIFTI_datatype=4 (INT16) to float
Hi all,
running seed Fox_tn_LP_3mm
------------------------
Extracting timeseries for seed Fox_tn_LP_3mm
Computing Correlation for seed Fox_tn_LP_3mm
++ 3dfim+: AFNI version=AFNI_2011_12_21_1014 (May 23 2014) [64-bit]
++ Authored by: B. Douglas Ward
Wrote bucket dataset into /home/peter/phxian/schpatient_c/sub111/func/RSFC/Fox_tn_LP_3mm_corr.nii.gz
Z-transforming correlations for seed Fox_tn_LP_3mm
++ 3dcalc: AFNI version=AFNI_2011_12_21_1014 (May 23 2014) [64-bit]
++ Authored by: A cast of thousands
** AFNI converts NIFTI_datatype=4 (INT16) in file /home/peter/phxian/schpatient_c/sub111/func/RSFC/Fox_tn_LP_3mm_corr.nii.gz to FLOAT32
Warnings of this type will be muted for this session.
Set AFNI_NIFTI_TYPE_WARN to YES to see them all, NO to see none.
++ Output dataset /home/peter/phxian/schpatient_c/sub111/func/RSFC/Fox_tn_LP_3mm_Z.nii.gz
Registering Z-transformed map to standard space
what do you think about the warning?
how to deal with it?
Thank you..
Peter
running seed Fox_tn_LP_3mm
------------------------
Extracting timeseries for seed Fox_tn_LP_3mm
Computing Correlation for seed Fox_tn_LP_3mm
++ 3dfim+: AFNI version=AFNI_2011_12_21_1014 (May 23 2014) [64-bit]
++ Authored by: B. Douglas Ward
Wrote bucket dataset into /home/peter/phxian/schpatient_c/sub111/func/RSFC/Fox_tn_LP_3mm_corr.nii.gz
Z-transforming correlations for seed Fox_tn_LP_3mm
++ 3dcalc: AFNI version=AFNI_2011_12_21_1014 (May 23 2014) [64-bit]
++ Authored by: A cast of thousands
** AFNI converts NIFTI_datatype=4 (INT16) in file /home/peter/phxian/schpatient_c/sub111/func/RSFC/Fox_tn_LP_3mm_corr.nii.gz to FLOAT32
Warnings of this type will be muted for this session.
Set AFNI_NIFTI_TYPE_WARN to YES to see them all, NO to see none.
++ Output dataset /home/peter/phxian/schpatient_c/sub111/func/RSFC/Fox_tn_LP_3mm_Z.nii.gz
Registering Z-transformed map to standard space
what do you think about the warning?
how to deal with it?
Thank you..
Peter
May 30, 2014 08:05 AM | Maarten Mennes
RE: converts NIFTI_datatype=4 (INT16) to float
Hello,
you can ignore that warning. Float32 allows greater numerical precision when storing the data (so this conversion is a good thing)
Maarten
you can ignore that warning. Float32 allows greater numerical precision when storing the data (so this conversion is a good thing)
Maarten
May 30, 2014 04:05 PM | peter lee
RE: converts NIFTI_datatype=4 (INT16) to float
Thanks Maarten.
I have another question is that,
there's no slice time correction in the scripts,
is that right?
how to add this process in the bash_process.sh?
thanks.
Peter
I have another question is that,
there's no slice time correction in the scripts,
is that right?
how to add this process in the bash_process.sh?
thanks.
Peter
May 30, 2014 06:05 PM | peter lee
RE: converts NIFTI_datatype=4 (INT16) to float
thanks Maarten,
I have viewed the previous discussion in this forum,
and got lots of information about slice timing correction now.
I still have one question is that, could I get the acquisition order from the raw data (e.g., dicom),
Have a good day..
Peter
I have viewed the previous discussion in this forum,
and got lots of information about slice timing correction now.
I still have one question is that, could I get the acquisition order from the raw data (e.g., dicom),
Have a good day..
Peter