Hello,

To add details to Peter's request, what is the output from this?

3dinfo -slice_timing run_1+orig


Using an MB acquisition should not really matter here. Perhaps
FSL does not support it is because of the limiting nature of the
NIFTI header, which is not capable of storing general slice timing
information, it just uses codes for a few known timing patters.


I do not see what artifacts you are alluding to in the image,
though there is a single red dot, which is odd. Note that we
generally avoid Fourier interpolation (for almost anything).
Though it can make nice results and is elegant, any spikes can
cause ringing artifacts.

By default afni_proc.py uses -quintic interpolation, so spikes
cannot spread far.


Can you provide any clarity regarding the artifacts? Note that
striping is common when motion occurs, with or without 3dTshift.

- rick