Dear Gonzalo,

It normally mean “you ran out of memory”. Does cropping the input image a bit more tightly around the brain solve the problem? (you can easily use Freeview->tools for this)

Cheers,

/E

--

Juan Eugenio Iglesias

http://www.jeiglesias.com

From: Gonzalo Rojas Costa <gonzalo.rojas.costa@gmail.com>
Date: Friday, March 17, 2023 at 16:49
To: "Iglesias Gonzalez, Juan E." <JIGLESIASGONZALEZ@mgh.harvard.edu>
Cc: "freesurfer@nmr.mgh.harvard.edu" <freesurfer@nmr.mgh.harvard.edu>
Subject: mri_synthsr with CT images

        External Email - Use Caution        

Dear Juan:

  I tested mri_synthsr using three different CT images with the threshold (80 value) that you told me some days ago. The first works ok, but with the other 2, I got the following error:

developer@developer-VirtualBox:~$ mri_synthseg --i /home/developer/Documents/OAS31367/sub-OAS31367_sess-d0142_run-01_CT_0_80.nii.gz --o /home/developer/Documents/OAS31367 --cpu
SynthSeg 2.0
using CPU, hiding all CUDA_VISIBLE_DEVICES
using 1 thread
predicting 1/1
Killed

  What does "Killed" mean? Any log file?

  Sincerely,




Gonzalo Rojas Costa
Department of Radiology
Clínica las Condes
Lo Fontecilla 441, Las Condes, Santiago, Chile.
Tel: 56-2-2105170
Cel: 56-9-97771785