Dear Michael,

Your code will create 3DT2.FSspace.mgz which is at 0.55mm resolution but with a 
 rotation/translation  in the header to overlap the T1 in RAS space.

You can now run
mri_convert [lr]h.hippoAmygLabels-T1.v21.[hierarchy].mgz   
[lr]h.hippoAmygLabels-T1.v21.[hierarchy].resampled.mgz -rl 3DT2.FSspace.mgz -rt 
nearest -odt float
to produce a volume in the same space as 3DT2.FSspace.mgz (also at 0.55mm). The 
flat -rl stands for “replace like”.

At that point, if the rotation between the original T2 and 3DT2.FSspace.mgz 
bothers you, you can combine the voxels from 
[lr]h.hippoAmygLabels-T1.v21.[hierarchy].resampled.mgz and combine them with 
the header of the original T2 to undo the rotation ;-)

Cheers,

/E

Juan Eugenio Iglesias
Senior research fellow
CMIC (UCL), MGH (HMS) and CSAIL (MIT)
http://www.jeiglesias.com

On Dec 8, 2021, at 04:33, Eyre, Michael 
<michael.e...@kcl.ac.uk<mailto:michael.e...@kcl.ac.uk>> wrote:

        External Email - Use Caution

Hi all

Regarding hippocampal subfield segmentation in FS7- how can I move the 
segmentation result to native T2w space? I plan to compare the result with a 
manual segmentation which was done in this space, using scripts which require 
nifti inputs.

I have run FS7 specifying with the -cm flag that this takes place in my T1 
(MP2RAGE) 0.65mm isotropic resolution:
recon-all -all -s <subject> -i T1w.nii -T2 T2w.nii -T2pial -gcut -cm

Then I ran the Hc subfield segmentation, specifying that my T2w volume 
(3D-SPACE, 0.55mm isotropic) should be used for this:
segmentHA_T2.sh <subject> T2w.nii 3DT2 0

The output that I want to move back to native 3DT2 space is the labelled volume 
lh.hippoAmygLabels-3DT2.v21.mgz (or the nifti of this which of course I can 
create using mri_convert). However this volume is 0.333mm isotropic and has a 
limited field of view - from the documentation: "Note that 
[lr]h.hippoAmygLabels-T1.v21.mgz and 
[lr]h.hippoAmygLabels-T1.v21.[hierarchy].mgz cover only a patch around the 
hippocampus, at a higher resolution than the input image."

The most relevant guidance I can find in the documentation is 
"[lr]h.hippoAmygLabels-T1.v21.FSvoxelSpace.mgz live in the same voxel space as 
the other Freesurfer volumes (e.g., orig.mgz, nu.mgz, aseg.mgz), so you can use 
it directly to produce masks for further analyses, but its resolution is lower 
(1 mm vs 0.333 mm)." In my case FSvoxelSpace is at 0.65mm resolution, but this 
is still lower than my T2w volume (0.55mm) and so would involve some 
downsampling (0.333mm --> 0.65mm --> 0.55mm) which I would like to avoid.

I have tried various linear registration approaches but I always end up with a 
result which, although in 0.55mm space, is clearly not aligned with the 
hippocampus when viewed together with my T2w.nii in ITK-SNAP.

Any suggestions would be much appreciated!

Many thanks

Mike
_______________________________________________
Freesurfer mailing list
Freesurfer@nmr.mgh.harvard.edu<mailto:Freesurfer@nmr.mgh.harvard.edu>
https://mail.nmr.mgh.harvard.edu/mailman/listinfo/freesurfer

_______________________________________________
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 Mass General Brigham 
Compliance HelpLine at http://www.massgeneralbrigham.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.
Please note that this e-mail is not secure (encrypted).  If you do not wish to 
continue communication over unencrypted e-mail, please notify the sender of 
this message immediately.  Continuing to send or respond to e-mail after 
receiving this message means you understand and accept this risk and wish to 
continue to communicate over unencrypted e-mail. 

Reply via email to