We noticed the same thing last year, as posted in an earlier message:
[
afni.nimh.nih.gov]
Up until now, we have been using a work-around: What we do is take the slice offsets given with the 3dinfo -verb command, subtract them from the TR, and then use the new numbers as the input to the 3dTshift command.
e.g. If the time offsets in the file header are:
0 1060 60 1120 120 1180 ...
and the TR is 2000, then we create a text file with the following times:
2000 940 1940 880 2880 ...
We then use this file as the toffsets file in the 3dTshift command. This seems to do the trick.
Tom Johnstone
W.M. Keck Laboratory for Functional Brain Imaging and Behavior
University of Wisconsin-Madison