does this happen every time you run it? The message said that the job was killed, which suggests something outside of recon-all (eg, if you were running it on a cluster, sometimes a job will get killed if it runs out of memory or runs too long).

On 08/23/2017 02:30 PM, Cara Bohon wrote:

I have a couple of subjects "exited with ERRORS" after running almost 48 hours (when my others all took about 13-15 hours on the same server). Both exited during Fix Topology lh.

The only time "error" appears is in this line: IFLAG= -1 LINE SEARCH FAILED. SEE DOCUMENTATION OF ROUTINE MCSRCH ERROR RETURN OF LINE SEARCH: INFO= 4 POSSIBLE CAUSES: FUNCTION OR GRADIENT ARE INCORRECT OR INCORRECT TOLERANCESoutof QuasiNewtonEMA: 011: -log(p) = -0.0 tol 0.000010 - which prior messages to this list suggest is not meaningful or problematic.

I am brand new to Freesurfer, so I'm not quite sure where to start in troubleshooting. The orig.mgz file looks fine to me, but maybe I'm missing something. Any other tips for things to check? I'm attaching a recon-all.log file in case that is helpful. I am running Freesurfer 5.3.0 on Linux.

Thanks for any tips on addressing the error!

-Cara

---

Freesurfer mailing list Freesurfer@nmr.mgh.harvard.edu https://mail.nmr.mgh.harvard.edu/mailman/listinfo/freesurfer