Eugenio,
If you generate the files on one system and look that them on another of opposite endian, you may run into a problem with the Nifti magic word. If it is written backwards, or interpreted that way, you can modify it as suggested here:
https://www.jiscmail.ac.uk/cgi-bin/webadmin?A2=ind1009&L=spm&P=R2148&1=spm&9=A&J=on&d=No+Match%3BMatch%3BMatches&z=4
However, "n+1" is for a single file, and "ni1" is for the hdr/image pair, so you may have a different issue.
Kathy Pearson
Hi everyone,
I ran into trouble trying to use statstical images generated in SPM8 for neuronavitaged TMS in a Nifti-compatible TMS-system (Localite TMSNavigator, http://www.localite.de/de/tms/index_tms.html).
Specifically, I acquired an fMRI finger-tapping task in older subjects using a block design. After preprocessing without spatial normalization, I ran a simple first-level analysis (movement versus rest) to identify motor cortex activations in each subject's individual anatomy. I exported the thresholded T-maps using the "save" option in the SPM8 results GUI (hdr + img).
When I load the resulting T-maps into the TMS Navigator, I get a warning that the images aren't stored in the proper format ("1+n" rather than "ni1" or "n+1"). Non-processed Nifit-images, e.g. the corresponding anatomical files, can be read without problems.
I'm lost as to what causes this error and whether (a) there's something I missed during the image processing/results saving procedure in SPM8 and (b) how I can access and change the header such that it conforms the proper Nifti struct.
Thanks a lot!
Eugenio Abela
|