External Email - Use Caution
On Thu, Jul 28, 2022 at 12:00 freesurfer-request@nmr.mgh.harvard.edu wrote:
Send Freesurfer mailing list submissions to freesurfer@nmr.mgh.harvard.edu
To subscribe or unsubscribe via the World Wide Web, visit
https://secure-web.cisco.com/17A-Eh02HTEIkh0f-xhl-a9F9UFoVcPZ8ScGAVIIkCyX9xb... or, via email, send a message with subject or body 'help' to freesurfer-request@nmr.mgh.harvard.edu
You can reach the person managing the list at freesurfer-owner@nmr.mgh.harvard.edu
When replying, please edit your Subject line so it is more specific than "Re: Contents of Freesurfer digest..."
Today's Topics:
- Re: Understanding ?h.sphere.reg (Salar Dini, Elaheh)
- Re: TRACULA -bedp parallel processing (Salar Dini, Elaheh)
- Re: ERROR: Talairach failed (Bouchra Guelib)
- Problem with hypothalamus subunits? (Zeng, Victor (BIDMC - Keshavan - Psychiatry))
- Fwd: eTIV (Bouchra Guelib)
- Re: mri_jacobian questions (Danielle Carrol)
- Re: mri_jacobian questions (Fischl, Bruce)
- Applying bonferroni clusterwise correction for 2spaces with PALM F-contrast (Hye Min Shin)
- Re: Problem with hypothalamus subunits? (Iglesias Gonzalez, Juan E.)
- The password request for the Freesurfer VirtualBox Image (Nina Omejc)
Message: 1 Date: Wed, 27 Jul 2022 17:55:33 +0000 From: "Salar Dini, Elaheh" elaheh.salardini@yale.edu Subject: Re: [Freesurfer] Understanding ?h.sphere.reg To: Freesurfer support list freesurfer@nmr.mgh.harvard.edu Message-ID: < BL0PR08MB467671BB49604E614465BEACF5979@BL0PR08MB4676.namprd08.prod.outlook.com
Content-Type: text/plain; charset="utf-8"
External Email - Use CautionHi Doug,
I found the solution to my problem, so please ignore my previous message. Thanks so much for always helping out anyway. In case, this question ever comes up for anyone else, here is the solution:
I just used freesurfer auto-recon steps to create the files I want using co-registered images. I needed the following files:
talairach.xfm and rh.cortex.label for my pipeline, so I just the following steps of recon-all on my co-registered files:
recon-all< https://secure-web.cisco.com/1EgFMsGckBYd6kxqV7w3f8yesPKD4GKe7qDUsgWQVhG57fK...
-autorecon1 -subjid <subjid> -talairach<
https://secure-web.cisco.com/13rqQe933ugmKwkEcnA8chHodDfVQwjtWZzI9UaMx6O-BYN...
on post-co-registerated orig.mgz to get talairach.xfm
and recon-all< https://secure-web.cisco.com/1EgFMsGckBYd6kxqV7w3f8yesPKD4GKe7qDUsgWQVhG57fK...
-autorecon2 -subjid <subjid> -white on post-co-registerated
aseg.presurf.mgz, brain.finalsurfs.mgz, wm.mgz, filled.mgz and ?h.orig to get ?h.cortex.label
Thanks and all the best, Ela
From: Salar Dini, Elaheh elaheh.salardini@yale.edu Sent: Tuesday, July 26, 2022 12:45 PM To: Freesurfer support list freesurfer@nmr.mgh.harvard.edu Subject: Re: Understanding ?h.sphere.reg
Hi Douglas, It does. Thank you. Can you also help me with something else? If we coregister bunch of volume and surfaces using the same reg.lta for one subject, is there a way to safely reflect these changes in label files like rh.cortex.label or in transformation fies like talairach.xfm? In other words, can we make any changes to rh.cortex.label and talairach.xfm from pre co-registeration to make them usable with post co-registration files? Thanks
Re: [Freesurfer] Understanding ?h.sphere.reg< https://secure-web.cisco.com/1UhOk22D0i3wY4fnQeKPgzgZbpFeOxSlca-61id1BOytmBI...
Douglas N. Greve< https://secure-web.cisco.com/16No3VGvLeslOCiSS6roovjBfOQ7EhU19JD6sWi2cufNdrD...
Sun, 24 Jul 2022 19:20:57 -0700<
https://secure-web.cisco.com/19tmADuYKDPqctiaAK489R3GB6vDIWL4rRxkEmP5pU-zA7m... ard.edu%26q%3Ddate%3A20220724>
The ?h.sphere.reg xyz coordinates are coordinates on the sphere. To apply a spherical registration, a point on one spherical mesh is mapped to the closest point on the other spherical mesh. not sure if that answers your question ... ________________________________ From: Salar Dini, Elaheh elaheh.salardini@yale.edu Sent: Thursday, July 21, 2022 5:26 PM To: Freesurfer support list freesurfer@nmr.mgh.harvard.edu Subject: Understanding ?h.sphere.reg
Dear freesurfer experts,
I was wondering if ?h.sphere.reg files have any coordinates in space tagged to them? What I actually mean is I'm using TRACULA which itself use the following files from mri and surf folder (all created by running recon-all on T1 image): aparc+aseg.mgz, brain.mgz, brainmask.mgz, orig.mg, T1.mgz and ThalamicNuclei.v12.Ta.FSvoxelSpace.mgzlh.thickness,rh.thickness,lh.white,rh.white,lh.sphere.reg,rh.shere.reg. I have all these files (except ?h.thickness and ?h.sphere.reg) in new coordinates in space created by co-registration. The pipeline we use to create recon-all results is almost the same as freesurfer pipeline with a slight difference in autorecon1 step, so the final results are almost always the same but the coordinate of the brain in 3D space is different, so we usually end up co-register one's reconstruction result (from our pipeline) with oneself T1.nii (come from mri_convert T1.dcm) so the structural mri reconstruction and dwi dcm files are in the same coordinate and can overlay . My understanding is that there is no coordinate tagged to ?h.sphere.reg files in 3D space, rather they are regulatory files which include some information about x,y,z vertices in regard to the surface of a hypothetical sphere (and the xyz are coming from the curvature of one's brain). As a result, I can use ?h.sphere.reg files as they are without any need to make any changes to match my files after they are coregistered. Is my understanding correct?
I'm sorry if my language is not clear enough. I tried my best to describe the situation, but I'm not sure if my description is clear enough.
Thank you for your help and time. Ela