External Email - Use Caution Python code (including 3rd party python packages) in the Intel Mac build cannot be guaranteed to run on Mac M1, M2 arm processors. Package developers may still build their code using Intel processor specific instructions which cannot be emulated by the Rosetta environment on arm64 Macs. Rosetta translates Intel processor instructions to arm64 processor instructions; when there is no equivalent arm processor instruction, you get the error “illegal instruction”. The remedy for this is to re-write and/or re-build the code (to be more portable). There is an arm64 freesurfer development build including an arm64 python with Apple’s tensorflow. However, the freesurfer python code is not yet entirely compatible with arm64 python and all its packages. The mri_synthsr script currently does not work with arm64 tensorflow; I don’t know about mri_samseg. You can try the arm64 development build via the link, https://secure-web.cisco.com/17oMRv7D8FpOpyCTDI2b6q3ZFH9-liuuaw55Fk0qAsqgBnL3cDmnkVAujZjuxE5eX79DEYS-N-28sS2kPCHZELA_TD9KfXA1gTpkIIQlltrdLjmUYAErTEyV7pXp61dNngBidguhX9Ro7dWKp68cyGlPyIUMglyRLC5Ic8KxVhEd1h6taIbJUs2RF62qX_akkZQzboTafybXKGqtqZO75VJ_VYmF1FbMwq5IEVXbxaM1fZtZ1ZQn6V7EGFGVpOnhJcYCh6SCvDAdGOF8jbC_XE4GUihNWJa4hRA4860MsPxHxc4Or__ON8TElFES-SLctaTntlZ16qO5C18SyRBuAGw/https%3A%2F%2Fsurfer.nmr.mgh.harvard.edu%2Fpub%2Fdist%2Ffreesurfer%2Fdev%2Ffreesurfer-macOS-darwin_arm64-dev.pkg%26nbsp; Please keep in mind this it not a release build and please report any errors. Fixes for these kinds of issues will become available in the development builds via the link above once they are added into the freesurfer development stream. We can also notify the list. - R. On Oct 7, 2023, at 03:23, Bianka Forgó <fbia...@gmail.com> wrote: External Email - Use Caution Dear Freesurfer Developers,I am attempting to use Freesurfer on MacOS Ventura (version 13.5.2) with an M2 Pro silicone chip and GPU. I have successfully installed Freesurfer version 7.4.1.I am trying to use samseg for cross-sectional MS lesion volume analysis by running the following command:run_samseg --input Freesurfer_subjects/T1.nii Freesurfer_subjects/FAMUS/T2FLAIR_reg.nii --pallidum-separate --lesion --lesion-mask-pattern 0 1 --output Freesurfer_subjects/FAMUS/samsegI get the error message:zsh: illegal hardware instruction run_samseg --input Freesurfer_subjects/FAMUS/T1.nii --lesion 0 1 As described in the samseg manual, one may be prompted to use Tensorflow when using this module for the first time. I was not prompted to do so but I did install it (and python3 as well) using the instructions here: MailScanner has detected a possible fraud attempt from "secure-web.cisco.com" claiming to be https://secure-web.cisco.com/1tE2yZiNK2sSgfXl2g2jsBKvz4UwOnAafBZo84FMcVUl1GYayXd0hNDmJphJPV5PjstNU56Mv2-ZHz2gHhAMlXY3hWsiVC1FHjeMi3zwh2v7t_xAJuVou-EfEHo44tHTgbXtjVRgAo0DpLGaC8q50HrjvkQVVyuN6wNvj4caVEzxRrcejp5Id1tZxys3U7RcpxmayW_RhSEZaQHfCJ1Q1oyXrUi1TDf4yT6v1xP-orC4T-AL7A03jXfucvl8wdsmShOubje1GwxXexAM8kDz2tCP3gurL_HfDY8e92Qv3usVI1_utdRBWx-wdHAUfywhLR6tzDc_UhJgGLNgh0-ILoA/https%3A%2F%2Fwww.tensorflow.org%2Finstall%2FpipAfter this, I still get the above error message.I can also see that there is no support for running Tensorflow on Mac with GPU.Does this mean that there's no way for me to run this command or is there anything else I can try to solve this?Of note, the basic samseg command (run_samseg --input <file> [<file> ...] --output <dir> [--threads <threads>] [--pallidum-separate]) is running without any issues.Thank you,Bianka_______________________________________________Freesurfer mailing listfreesur...@nmr.mgh.harvard.eduhttps://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 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.