Hi Fred,

That goes along with that Toshi found, and with what I was looking
into today. The AFNI->NIfTI conversion has some difficulties with
slice timing, which I am hopfully fixing. I have not looked into
how to3d converts to NIfTI, but expect it is via the same mechanism.

I do not think the problem is from NIfTI to AFNI (which is where
'3dinfo' on a NIfTI dataset would have trouble). I think the
problem is in writing the NIfTI dataset to begin with, in that the
NIfTI dataset does not have the correct slice_code (as seen using
'nifti_tool -disp_hdr').

I will let you know more tomorrow.

Thanks,

- rick