Here's another question about sparse scanning protocols and using 3dTshift before registration. My TR=3500ms. I'm acquiring 26 slices in 2808 ms and in -z order, therefore I made my -tpattern file (tshift.1D) look like this:

2700 2592 2484 2376 2268 2160 2052 1944 1836 1728 1620 1512 1404 1296 1188 1080 972 864 756 648 540 432 324 216 108 0

Here's the command line:
3dTshift -prefix S1-voice-shift -ignore 10 -rlt+ -tpattern @filename tshift.1D S1-voice-epan+orig

FYI, S1-voice-epan+orig was made with the following command line:
to3d -epan –prefix S1-voice-epan -save_outliers S1-voice-out.1D -time:tz 214 26 3500 seqminus S1-voice.\*

Does this seem reasonable or am I missing something? When I run 3dTshift, I always get the following:
***Fatal error: temporal pattern is already aligned in time!

Can I use another option in to3d to tell afni that the 26 slices are collected in 2800ms, not 3500? Can I do the time shifting in to3d and just use 3dTshift for the de-trending step?

TomC

PS: I think there are a few typos in the 3dTshift -help file.
these 2 lines:
seqplus 0 200 400 600 800 Sequential in the -z direction
seqplus 800 600 400 200 0 Sequential in the -z direction

I think should read:

seqplus 0 200 400 600 800 Sequential in the +z direction
seqminus 800 600 400 200 0 Sequential in the -z direction