Hi Cesar,
Thanks for figuring that out. It is a bit strange though,
While I can imagine an ntt vs nvals difference when
converting from NIFTI to AFNI (internally), the ultimate
test that 3dTcorrelate uses which leads to that error
message compares exactly what gets printed out via
the "3dinfo -nt" command.
This reminds me of your similar issue reading and
writing those files in R, which, despite spending some
time on, I have yet to resolve...
- rick