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