Hi Ajay,

1) Yes, RetroTS takes the TR in seconds, as well as
the 'Custom' and filename.1D slice timing, based on
the help for that function.

Alternately, I think the to3d slice timing for the
@filename method must be in ms. And it is better to
put the timing into the datasets rather than feed it
to 3dTshift directly (just because you can verify
it whenever you want to).

The 3dTshift @filename timing matches that of to3d.
But again, I suggest you do not use that. Note that
if the dataset already exists, the 3dTcat program
can be use to just set that tpattern for the output.


2) I guess this is covered already. Just do not go
this route, simply because it is not as clear. Use
to3d or 3dTcat to set the tpattern, and then it is
easy to verify with "3dinfo -VERB".


3) The 3dinfo output is always in seconds, regardless
of how slice times are stored in the dataset (i.e. it
divides by 1000 if times are stored in ms).


So first put the correct timing into the dataset. The
only place where you have to specify it directly is
via RetroTS.

- rick