help
help > RE: confound corrected nifti header shows TR 1
Sep 23, 2016 12:09 PM | Pravesh Parekh - University of Oslo
RE: confound corrected nifti header shows TR 1
Hi Rajeev and Patricia,
I believe it is not a bug in Conn as such but got to do with SPM; when you preprocess the data in SPM, the resulting nifti files do not have the TR value anymore (i.e. TR is set to be zero).
I tried loading one of my raw fMRI image volumes
image = spm_vol('rsfMRI.nii,1');
on exploring the "private" nifti object inside the image structure, I found a field called "timing" [image.private.timing] which returns two sub-fields: toffset, and tspace
where tspace contains the original TR of the images. If I open any of the SPM processed files, I do not see any timing field!
Also, it is quite interesting to note that both of you suggest that the TR = 1 for your processed files; however, in my case I see TR = 0. I am using SPM 12b and checking the image information using MRICron, on a Windows machine.
However, the information must be existing somewhere in the header and/or can be reconstructed because the SPM.mat file (after first level specification) contains the TR value in the SPM.xY.RT field.
Best
Pravesh
Originally posted by Patricia M:
I believe it is not a bug in Conn as such but got to do with SPM; when you preprocess the data in SPM, the resulting nifti files do not have the TR value anymore (i.e. TR is set to be zero).
I tried loading one of my raw fMRI image volumes
image = spm_vol('rsfMRI.nii,1');
on exploring the "private" nifti object inside the image structure, I found a field called "timing" [image.private.timing] which returns two sub-fields: toffset, and tspace
where tspace contains the original TR of the images. If I open any of the SPM processed files, I do not see any timing field!
Also, it is quite interesting to note that both of you suggest that the TR = 1 for your processed files; however, in my case I see TR = 0. I am using SPM 12b and checking the image information using MRICron, on a Windows machine.
However, the information must be existing somewhere in the header and/or can be reconstructed because the SPM.mat file (after first level specification) contains the TR value in the SPM.xY.RT field.
Best
Pravesh
Originally posted by Patricia M:
Hi Rajeev,
I am having the same problem with some old data that has been already processed. Have you managed to find a solution to correct this?
Thanks so much!
Cheers,
Patricia
I am having the same problem with some old data that has been already processed. Have you managed to find a solution to correct this?
Thanks so much!
Cheers,
Patricia
Threaded View
Title | Author | Date |
---|---|---|
Rajeev Krishnadas | Nov 16, 2015 | |
Rajeev Krishnadas | Nov 17, 2015 | |
Patricia M | Sep 22, 2016 | |
Rajeev Krishnadas | Oct 8, 2016 | |
Pravesh Parekh | Sep 23, 2016 | |