External Email - Use Caution        

 The fix for the error you posted when running the 8.0.0 beta release - 
which has to do with how some python code is run - will be fixed in the 
forthcoming 8.0.0 release; it’s unrelated to your environment setup.
The commands that run the recon-all pipeline in the 8.0.0-beta 2024 release 
have changed since the older 7.2.0 release from 2021, so 7.2.0 does not 
reproduce that error.  You could try setting the environment variable 
listed below on your 8.0.0-beta recon-all command line (bash shell example) to 
revert to the older recon-all behavior.
$ export FS_V8_XOPTS=0 && recon-all <your arguments here>
- R.
On Feb 6, 2025, at 01:02, Lee Lin <lee.kevin....@gmail.com> 
wrote:        External Email - Use 
Caution        Dear FreeSurfer 
developers,
running the 8.0.0-betaRecently, I attempted to run FreeSurfer on my 
new work computer (MacBook Pro, Apple M3 Max, macOS 14.6). I found 
that v8.0.0 beta is the only compatible version, and the installation 
appeared to be successful.
However, when running recon-all on my 7T anatomical 
data using the following command:recon-all -i 
<path_to_anatomy_nii_file> -s <subject_initials> -allI encountered 
an error during subcortical segmentation (see attached "7T_recon-all.log" 
and screenshots). It looks like the deep learning model used 
by mri_sclimbic_seg was reporting an input dimension 
mismatch. 
To diagnose the issue, I tested the following possibilities:1. Is the 
error specific to this data?I ran recon-all on other 7T 
anatomical data, but the same error occurred.2. Is the error specific to 
7T data?I tested recon-all with 3T data, but in this case, the 
process was killed even earlier, and no useful error message was 
provided (see "3T_recon-all.log"). I’m unsure whether these two issues are 
related..3. Is the issue related to the FreeSurfer version or my work 
environment?I ran recon-all on an older MacBook Pro (Apple M1, 
macOS 12.6) using FreeSurfer 7.2.0, and the process completed 
successfully. This suggests that the issue is specific to FreeSurfer 
v8.0.0 beta or my work environment rather than the dataset itself.
Do you have any suggestions on this issue?
Additionally, I noticed that FreeSurfer v8.0.0 beta uses a deep 
learning model for segmentation, which differs from previous versions. Is 
there a way to switch back to the traditional segmentation method?
I would greatly appreciate any insights or troubleshooting suggestions.
Best regards,Lee 
Lin<7T_recon-all.log><7T_recon-all_error-msg2.png><7T_recon-all_error-msg1.png><3T_recon-all.log>_______________________________________________
Freesurfer mailing list
Freesurfer@nmr.mgh.harvard.edu
https://secure-web.cisco.com/1vJ3hkJcbeBmkSfHBn3idEPYXvTCSXvkeUXnJa1D_GXnUvxLS0WgXZnVGX_6mhyZ8X1N5hHrEk2qAg2wMXtQP36kxD4snrbS5-NfpHihRQ4fDp9ywOtYaH06HiXUcls4Fqt9qUrZqZHgKYksJlFCCz-0EfsNnRw_DR4-CV9D1iIE2iMLhY15O19TaoCsiVeoYCrkybpxkf8ARV_uzzninYHKogFttq2Jor3cOkasgTMcBMpJrq4YSo9NXuyFq-u4Je5CZUVsXuRedMHSI8oP0nZsKGMdl-Hou16EqJ8A12BhQN6V4eTgLynxbbnhCB0CvAeZjcqgjB3Gz5W_6U-ShMA/https%3A%2F%2Fmail.nmr.mgh.harvard.edu%2Fmailman%2Flistinfo%2Ffreesurfer

_______________________________________________
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 https://www.massgeneralbrigham.org/complianceline 
<https://www.massgeneralbrigham.org/complianceline> .
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