Hi Douglas,
thank you for the quick reply! That helped for the first hard failure.
Do you have any idea what could have caused the second error message? This only happened for some subjects when rerunning recon-all with -autorecon2 -autorecon3, but always resulted in this error log:
Iterating 2 times --------------------------------- 3d normalization pass 1 of 2 white matter peak found at 110 Cannot allocate memory Linux node098 2.6.32-696.20.1.el6.x86_64 #1 SMP Thu Jan 25 08:47:49 CST 2018 x86_64 x86_64 x86_64 GNU/Linux
recon-all -s 44538_T1_fs_edit exited with ERRORS at Do 29. Mär 01:28:15 CEST 2018
Attached you can find the respective recon-all.log file.
Thank you!
Best, Anna
Hi Anna
from your log file it looks like some other process is using more than 2/3 of the memory on your machine:
total used free shared buffers cached Mem: 24729588 16852524 7877064 4095060 0 10543292 -/+ buffers/cache: 6309232 18420356 Swap: 0 0 0
cheers Bruce
On Thu, 5 Apr 2018, Anna Daniels wrote:
Hi Douglas,
thank you for the quick reply! That helped for the first hard failure.
Do you have any idea what could have caused the second error message? This only happened for some subjects when rerunning recon-all with -autorecon2 -autorecon3, but always resulted in this error log:
Iterating 2 times
3d normalization pass 1 of 2 white matter peak found at 110 Cannot allocate memory Linux node098 2.6.32-696.20.1.el6.x86_64 #1 SMP Thu Jan 25 08:47:49 CST 2018 x86_64 x86_64 x86_64 GNU/Linux
recon-all -s 44538_T1_fs_edit exited with ERRORS at Do 29. Mär 01:28:15 CEST 2018
Attached you can find the respective recon-all.log file.
Thank you!
Best, Anna
freesurfer@nmr.mgh.harvard.edu