no, but if you add the flag -time to recon-all, you will get lines like this in the recon-all.log:
time:: 0:11.49 cmd:: mris_anatomical_stats where you can grep on 'time::' to get command run times, although you'd have to add together some commands to get times for a stage. note: runtimes can vary quite a bit, some subjects take a lot longer to correct than others, and the newer intel nehalem architecture runs in less than half the time as the older amd opteron and p4s. n On Wed, 2010-07-28 at 17:19 -0400, Chris Watson wrote: > Hello, > Do you guys have a script that parses recon-all.log and spits out the > processing time for each step? Something that would be similar to this > in recon-all --help: > -<no>motioncor < 5 min > -<no>nuintensitycor 3 min > -<no>talairach 4 min > -<no>normalization 3 min > -<no>skullstrip 1 min > -<no>gcareg 8 min > -<no>canorm 1 min > -<no>careg 10 hours > > and so on. > > Thanks, > Chris > _______________________________________________ > Freesurfer mailing list > 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 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.
