Hi Michael, I had the same issue a few months ago. In my experience 4GB was sufficient. If there are constraints on the memory, I think 3 GB should also work.

I also had the same issue with -gcut and FS 5.0. Back then I had tried to figure out what was the minimum memory required since I had some memory constraints. I was running jobs on cluster where each node had 16 cores and 32 GB total memory (that could be divided between the 16 cores). At most I was able to run 12 recons on each node. So the minimum memory required was ~ 2.7 GB (32 GB/12).

Mehul

On Sat, Nov 19, 2011 at 12:46 PM, Michael Harms mharms@conte.wustl.eduwrote:

Hello, Approximately how much memory does one need when using the -gcut option with FS 5.1? I had submitted 30+ recons to a cluster that alloted a default of 2.5 GB for processes submitted under this particular queue, and all of them aborted with a bad_alloc error at the gcut stage of skull stripping.

Should 4 GB be sufficient?

thanks, -MH

-- Michael Harms, Ph.D.

---

Conte Center for the Neuroscience of Mental Disorders Washington University School of Medicine Department of Psychiatry, Box 8134 Renard Hospital, Room 6604 Tel: 314-747-6173 660 South Euclid Ave. Fax: 314-747-2182 St. Louis, MO 63110 Email: mharms@wustl.edu

---

---

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 Partners Compliance HelpLine at http://www.partners.org/complianceline . If the e-mail was sent to you in error but does not contain patient information, please contact the sender and properly dispose of the e-mail.