Hello all,

After running the program dcm2niix_afni with this command : dcm2niix_afni *, I realized that the offset in slice acquisition time are set to 0 (3dinfo -slice_timing dset+tlrc). Is this really the case that the timing offset has been corrected? I don't see any info about that in the dcm2niix_afni documentation. Then, when I run 3dvolreg with the -tshift flag the program says the dataset has no time offset.

Also, I noticed that the dcm2niix_afni program keeps running and outputs many more datasets appending a, b, c, d...to the filename :
found 195 DICOM image(s)
slices stacked despite varying acquisition numbers (if this is not desired please recompile)
Note: rare 16-bit UNSIGNED integer image. Older tools may require 32-bit conversion
Convert 195 DICOM as test_20170626150037_cmrr_mbep2d_bold_195_5 (96x96x63x195)
Found 195 DICOM image(s)
slices stacked despite varying acquisition numbers (if this is not desired please recompile)
Note: rare 16-bit UNSIGNED integer image. Older tools may require 32-bit conversion
Convert 195 DICOM as test_20170626150037_cmrr_mbep2d_bold_195_5a (96x96x63x195)
Found 195 DICOM image(s)
slices stacked despite varying acquisition numbers (if this is not desired please recompile)
Note: rare 16-bit UNSIGNED integer image. Older tools may require 32-bit conversion
Convert 195 DICOM as test_20170626150037_cmrr_mbep2d_bold_195_5b (96x96x63x195)
Found 195 DICOM image(s)
slices stacked despite varying acquisition numbers (if this is not desired please recompile)
Note: rare 16-bit UNSIGNED integer image. Older tools may require 32-bit conversion
Convert 195 DICOM as test_20170626150037_cmrr_mbep2d_bold_195_5c (96x96x63x195)

thanks for your help,
pat