Hey Bruce, I’m helping a group from University of Cincinnati with this patient, so unfortunately I don’t have access to the data. They are running recon-all on a laptop that has 32 GB of RAM. Nothing else big is running in the background. Would you recommend manually fixing the defect in the skull?
Thanks, Noam From: freesurfer-boun...@nmr.mgh.harvard.edu <freesurfer-boun...@nmr.mgh.harvard.edu> On Behalf Of Fischl, Bruce Sent: Thursday, November 18, 2021 9:29 PM To: Freesurfer support list <freesurfer@nmr.mgh.harvard.edu> Subject: Re: [Freesurfer] recon-all reconbatchjobs Segmentation fault Hi Noam How much ram do you have in the machine? Is anything else big running? You can also examine that defect and see what is going on. 9000 vertices is pretty big so something significant like a chunk of skull might be fixable Cheers Bruce From: freesurfer-boun...@nmr.mgh.harvard.edu<mailto:freesurfer-boun...@nmr.mgh.harvard.edu> <freesurfer-boun...@nmr.mgh.harvard.edu<mailto:freesurfer-boun...@nmr.mgh.harvard.edu>> On Behalf Of Peled, Noam Sent: Thursday, November 18, 2021 9:05 PM To: Freesurfer support list <freesurfer@nmr.mgh.harvard.edu<mailto:freesurfer@nmr.mgh.harvard.edu>> Subject: Re: [Freesurfer] recon-all reconbatchjobs Segmentation fault Thanks Doug! Unfortunately, removing the parallel flag didn’t help: “ … After retessellation of defect 43 (v0=79551), euler #=-51 (145804,431777,285922) : difference with theory (-68) = -17 CORRECTING DEFECT 44 (vertices=9236, convex hull=4698, v0=79649) Command terminated by signal 11 @#@FSTIME 2021:11:17:14:54:07 mris_fix_topology N 14 e 12788.52 S 1.14 U 12786.35 P 99% M 1761016 F 0 R 581366 W 0 c 79248 w 3 I 0 O 3960 L 1.01 1.00 1.00 @#@FSLOADPOST 2021:11:17:18:27:16 mris_fix_topology N 14 1.00 1.00 1.00 “ Any ideas? Thanks again, Noam From: freesurfer-boun...@nmr.mgh.harvard.edu<mailto:freesurfer-boun...@nmr.mgh.harvard.edu> <freesurfer-boun...@nmr.mgh.harvard.edu<mailto:freesurfer-boun...@nmr.mgh.harvard.edu>> On Behalf Of Douglas N. Greve Sent: Wednesday, November 17, 2021 10:09 AM To: freesurfer@nmr.mgh.harvard.edu<mailto:freesurfer@nmr.mgh.harvard.edu> Subject: Re: [Freesurfer] recon-all reconbatchjobs Segmentation fault I'm not sure what is happening. Does it work without the parallel flag? btw, you are not using 7.2 here's your build: build-stamp.txt: freesurfer-linux-ubuntu18_x86_64-dev-20210824-e101185 On 11/16/2021 4:26 PM, Peled, Noam wrote: Dear Freesurfer group, I was running recon-all (Freesurfer 7.2 on Ubuntu) and received the following error: “ mris_fix_topology -mgz -sphere qsphere.nofix -inflated inflated.nofix -orig orig.nofix -out orig.premesh -ga -seed 1234 UC07 rh Waiting for PID 6337 of (6337 6340) to complete... Waiting for PID 6340 of (6337 6340) to complete... /home/basuia/Documents/mmvt_root/freesurfer/bin/reconbatchjobs: line 77: 6340 Segmentation fault (core dumped) exec $JOB >> $LOG 2>&1 PIDs (6337 6340) completed and logs appended. “ Please find the log file attached. Any idea what is the problem? Thanks, Noam _______________________________________________ Freesurfer mailing list Freesurfer@nmr.mgh.harvard.edu<mailto:Freesurfer@nmr.mgh.harvard.edu> https://mail.nmr.mgh.harvard.edu/mailman/listinfo/freesurfer
_______________________________________________ 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 Mass General Brigham Compliance HelpLine at http://www.massgeneralbrigham.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. Please note that this e-mail is not secure (encrypted). If you do not wish to continue communication over unencrypted e-mail, please notify the sender of this message immediately. Continuing to send or respond to e-mail after receiving this message means you understand and accept this risk and wish to continue to communicate over unencrypted e-mail.
