Hi Rahul

That typically means that something has gone wrong, like too much skull being left around. The timing of the defect correction is quadratic in the size of the largest defect, so quite fast for small ones, but very very slow for big ones (and less likely to be correct when done).  Look at the inflated.nofix surface and the wm.mgz and see if you can understand why this is happening. There is also a label file that gets generated for the defects that you can load and use to visualize them.

Also, please don’t send snapshots of text – just embed the text in the email so we can search and copy and paste and such

Cheers

Bruce

From: freesurfer-bounces@nmr.mgh.harvard.edu <freesurfer-bounces@nmr.mgh.harvard.edu> On Behalf Of Paul, Rahul
Sent: Friday, January 29, 2021 12:24 PM
To: freesurfer@nmr.mgh.harvard.edu
Subject: [Freesurfer] Fw: Freesurfer recon all

---

From: Paul, Rahul
Sent: Thursday, January 28, 2021 3:52 PM
To: freesurfer@nmr.mgh.harvard.edu <freesurfer@nmr.mgh.harvard.edu>
Subject: Freesurfer recon all

Hi,

I just started working on the freesurfer software. I was trying to use recon-all command but there was an output saying XL error detected, and it remained same for more than 6 hours or so.

Any idea how I can fix it? Bdw i stopped it running after 8 hours or so.

I am using a T1-MRI scan. I am using a MacBook pro (8GB RAM). I am attaching a screenshot and the command I used can be seen in the bottom of the screenshot.

Thank you,

Rahul Paul