yes, the -legacy flag was only necessary for the v3.0 to v4.0 transition. v4.0 data should be fully compatible with reprocessing in v5.
n. On Wed, 2010-09-22 at 17:31 -0500, Juranek, Jenifer wrote: > I'm hoping to push my legacy datasets (processed and edited in FSv4.0.5) > through FSv5.0.0. After installing FSv5.0.0, I received an error that it > didn't look like a legacy analysis (see below). > [jjura...@localhost subjects]$ recon-all -legacy -s SB_057_H21001 > ERROR: you have specified -legacy, but this does not look like > a legacy analysis. > > My recon-all.log file for this subjid reports the following build-stamp.txt: > freesurfer-Linux-centos4_x86_64-stable-pub-v4.0.5 > > How do I convince FSv5.0.0 that I am feeding it legacy data from FSv4.0.5? > Have I skipped too many versions to use this -legacy flag? > > Many thanks, > Jenifer > > > _______________________________________________ > 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.
