Re: [Freesurfer] Killed procees during running WMH-SynthSeg

2024-01-30 Thread fsbuild
External Email - Use Caution  We have seen the (Mac or Linux) OS automatically kill resource greedy processes, e.g., commands using large model files.   Increasing the limit on physical RAM usage and/or increasing how much data is swapped out to disk may still not allow the proc

Re: [Freesurfer] Killed procees during running WMH-SynthSeg

2024-01-30 Thread Bender, Andrew
External Email - Use Caution Dear Freesurfer Experts, I’m evaluating WMH-SynthSeg for white matter lesion segmentation using the most recent development version, and ran into similar issues reported last month: https://secure-web.cisco.com/15YjRoSDCoF2Q2A8SbHg4Jal044A5FQlCGhkswU

Re: [Freesurfer] Killed procees during running WMH-SynthSeg

2023-12-21 Thread Matthew Lynch
External Email - Use Caution I have found that mri_synthseg v. 7.4.0 in WSL is finicky even with 32 Gb RAM. It seems to work most of the time with 32 Gb RAM by using .wslconfig to limit WSL physical memory usage to 24 Gb and swap at 32 Gb. (synthseg uses about 1-2 Gb of swap in t

Re: [Freesurfer] Killed procees during running WMH-SynthSeg

2023-12-21 Thread Iglesias Gonzalez, Juan E.
Dear Chuyue, It’s very posible that you ran out of RAM. I think you need about 32GB to run this module. Do you think that could be the problem? Cheers, /Eugenio -- Juan Eugenio Iglesias http://www.jeiglesias.com From: freesurfer-boun...@nmr.mgh.harvard.edu on behalf of 赵楚越 Date: Thursday, De