It totally looks like it. How much RAM do you have on the machine you’re using? Cheers, Eugenio

-- Juan Eugenio Iglesias http://www.jeiglesias.com

From: "Fischl, Bruce R.,PHD" BFISCHL@mgh.harvard.edu Date: Thursday, March 16, 2023 at 14:04 To: Freesurfer support list freesurfer@nmr.mgh.harvard.edu, "Iglesias Gonzalez, Juan E." JIGLESIASGONZALEZ@mgh.harvard.edu Subject: RE: [Freesurfer] CT and mri_synthsr

I think it usually means it ran out of memory

From: freesurfer-bounces@nmr.mgh.harvard.edu freesurfer-bounces@nmr.mgh.harvard.edu On Behalf Of Gonzalo Rojas Costa Sent: Thursday, March 16, 2023 2:01 PM To: Iglesias Gonzalez, Juan E. JIGLESIASGONZALEZ@mgh.harvard.edu Cc: freesurfer@nmr.mgh.harvard.edu Subject: [Freesurfer] CT and mri_synthsr

External Email - Use Caution Dear Juan:

I tested mri_synthsr using three different CT images using 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