Try mri_coreg. You can run it with multiple cores with --threads N

On 6/17/2021 8:48 AM, Marina Fernández wrote:

        External Email - Use Caution

Dear experts,

I would like to co-register T2 to T1 robustly, both images have a
resolution of 0.65mm3.

Firstly, I tried bbregister with the '--init-rr' flag, but this function
doesn't allow to keep the native voxel resolution (i.e., 0.65mm3),
changing it to 1 mm.  As I wanted to maintain the native voxel
resolution , I tried the mri_robust_register function (corresponding to
the '--init-rr' flag) as explained in the help associated with this
function, but this process took thirteen hours:

EXAMPLE 4. Robust cross modal registration:

mri_robust_register --mov movT2.mgz --dst dstT1.mgz --satit --iscale

--mapmov T2_to_T1.mgz --lta T2_to_T1.lta --cost ROBENT --entradius 2

--entcorrection --weights T2_to_T1_weights.mgz

I also tried the standard cross modal registration. The process didn't
take as long, but the result was not as accurate as bbregister.

EXAMPLE 5. Standard cross modal registration:

mri_robust_register --mov movT2.mgz --dst dstT1.mgz --mapmov T2_to_

T1.mgz --lta T2_to_T1.lta --cost NMI

Could you suggest me how to accurately register T2 to T1 images
maintaining the native voxel resolution in a shorter time?

Thank you very much in advance.

Best,
Marina

_______________________________________________
Freesurfer mailing list
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