Hi,
I haven't got a reply, so I thought I repost this:
Is it a known problem that when doing a nearest interpolation from a volume of integers from a subject's anatomical space to the fsaverage surface using the mri_vol2surf flag results in non-integer output, or am I doing this wrong (see details below)?
Thanks, Thomas
On Sep 9, 2010, at 6:29 PM, ythomas wrote:
Hi,
I am trying to sample a volume of integers in subject's anatomical space to fsaverage surf. However, the output does not seem to be integer valued anymore even though I specify nearest neighbor for interpolation type.
I tried both stable4 and the dev version and used the following command:
mri_vol2surf --regheader 090425_QF86JB_FS --mov /autofs/cluster/ con_003/users/ythomas/test_mri_vol2surf/090425_QF86JB_FS/data/ 090425_QF86JB_vol2vol.nii.gz --hemi lh --projfrac .5 --trgsubject fsaverage --o /autofs/cluster/con_003/users/ythomas/test_mri_vol2surf/ 090425_QF86JB_FS/data/lh.090425_QF86JB_vol2surf.nii.gz --reshape -- interp nearest
You can replicate the results, by going to
/autofs/cluster/con_003/users/ythomas/test_mri_vol2surf/
and running "test_script.csh"
Interestingly, if I replace "fsaverage" in the trgsubject with the subject as the trgsubject (projection onto the same subject's surface), the output remained integer valued. I am not sure how mri_vol2surf works, but perhaps the step from the subject's surface to the fsaverage's surface is messed up?
Thanks, Thomas _______________________________________________ Freesurfer mailing list Freesurfer@nmr.mgh.harvard.edu https://mail.nmr.mgh.harvard.edu/mailman/listinfo/freesurfer
The information in this e-mail is intended only for the person to whom it is addressed. If you believe this e-mail was sent to you in error and the e-mail contains patient information, please contact the Partners Compliance HelpLine at http://www.partners.org/complianceline . If the e-mail was sent to you in error but does not contain patient information, please contact the sender and properly dispose of the e-mail.