Hi Bruce,

The exact command I ran was  recon-all -autorecon1 -autorecon2 -subjid
DNS_highRes_N892

I do have ~1000 scans, but it is not a longitudinal study. They are located
under the DNS_highRes_n892/mri/orig/ directory in the .mgz format.

Let me know if you need anymore information. Thanks!


On Wed, Aug 6, 2014 at 3:09 PM, Bruce Fischl <fis...@nmr.mgh.harvard.edu>
wrote:

> Hi Esha
>
> what are you trying to do? From this output it looks like you are runing a
> ~1000 time point longiutdinal study, which I assume is not what you meant.
>
> Please be sure to include the exact command you ran!
>
> cheers
> Bruce
>
>
> On Wed, 6 Aug 2014, Esha Mehta wrote:
>
>  Hello,
>> I am extremely new FreeSurfer user, and have hit a bump in the road while
>> trying to run -autorecon1 and -autorecon2. The process seemed to be
>> running
>> smoothly until I got the following warning messages for every file number,
>> and then it was randomly killed-
>>
>> * WARNING: TP 890 to 1 did not converge !!
>>
>> * WARNING: TP 891 to 1 did not converge !!
>>
>> * WARNING: TP 892 to 1 did not converge !!
>>
>> mapping movs and creating initial template...
>>
>>  allow intensity scaling
>>
>> Linux login4 2.6.32-431.5.1.el6.x86_64 #1 SMP Fri Jan 10 14:46:43 EST 2014
>> x86_64 x86_64 x86_64 GNU/Linux
>>
>> recon-all -s DNS_highRes_N892 exited with ERRORS at Mon Jul 21 10:48:23
>> EDT
>> 2014
>>
>>
>> Within the error log, there was also an extremely lengthy command, and I
>> believe could have been part of the issue as well. It is way to long to
>> post
>> here, but here is how it begins and ends-
>>
>> CMD mri_robust_template --mov
>> /groups/wallacegrp/DNS_highRes_N892/mri/orig/000.mgz
>> /groups/wallacegrp/DNS_highRes_N892/mri/orig/001.mgz
>> /groups/wallacegrp/DNS_highRes_N892/mri/orig/002.mgz
>>
>> ...
>>
>> /groups/wallacegrp/DNS_highRes_N892/mri/orig/888.lta
>> /groups/wallacegrp/DNS_highRes_N892/mri/orig/889.lta
>> /groups/wallacegrp/DNS_highRes_N892/mri/orig/890.lta
>> /groups/wallacegrp/DNS_highRes_N892/mri/orig/891.lta
>>
>>
>> I was hoping you could give me some advice on how to deal with this error,
>> or help me determine whether this is a freesurfer error, or has to do with
>> something else.
>>
>> Thanks so much!
>>
>> --
>> Esha Mehta585-967-7223
>> emeht...@gwu.edu
>> George Washington University, Class of 2017
>>
>>
> _______________________________________________
> 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.
>
>


-- 
Esha Mehta
585-967-7223
emeht...@gwu.edu
George Washington University, Class of 2017
_______________________________________________
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.

Reply via email to