nope, never seen that error. Probably from mri_segment. If you send me the input volume I'll take a look (check the recon-all.log and see what command was running when that happened). Also, definitely check it before sending to make sure it's reasonable
On Wed, 19 Jun 2013, Sudhin A. Shah wrote: > Hi > > ERROR: MRIthickenThinWMStrands: invalid x,y,z! > > Numerical result out of range > > > Any tips? > S > > _______________________________________________ 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.