Re: [Freesurfer] recon-all compared to dev table

2015-05-08 Thread Nick Schmansky, MGH
Kody,

The ReconAllDevTable wiki page describes the stream that is under
development.  For v5.3, you will want this page:

https://surfer.nmr.mgh.harvard.edu/fswiki/ReconAllTableStableV5.3

Be aware though that the commands listed may not be *exactly* as that
found in a v5.3 run, as this table is manually created and abbreviated
for readability.  But if you find discrepancies with a v5.3 run of
yours, feel free to email me or the list pointing out the mistakes, so
that we can update it.

I've also updated the main wiki page so that people are not directed to
the ReconAllDevTable page.

Side note, if you want try our 'dev' version (documented by
ReconAllDevTable), which will become v6 in a few weeks, you can get it
here:

ftp://surfer.nmr.mgh.harvard.edu/pub/dist/freesurfer/dev/

and would appreciate testing feedback, as we'd hate to release v6 with
some dumb mistake that we didn't catch in testing.

Nick


On Thu, 2015-05-07 at 11:51 -0700, zal...@u.washington.edu wrote:
> Dear freesurfer team,
> 
> I'm very new to freesurfer, and I am currently working my way through the 
> recon-all dev table functions (listed here: 
> http://freesurfer.net/fswiki/ReconAllDevTable) step-by-step in preparation 
> for processing a large amount of participant volumetric data. While doing so 
> I've noticed some inconsistencies between the dev table and the series of 
> functions called by the recon-all command.
> 
> For example:
> -The apas2aseg function listed in the dev table does not exist in my bin file 
> (nor does it appear to be called by recon-all).
> -The cortical ribbon output occurs after the three cortical parcellation 
> steps/creation of the anatomical.stats files (instead of prior to these steps 
> like the dev table suggests)
> -The MNI intensity correction (the mri_nu_correct.mni function) is not called 
> following the skull-stripping.
> I downloaded the latest version of freesurfer (5.3.0) last week so it should 
> be up-to-date. 
> 
> Thank you for taking the time to answer my questions,
> -Kody J. Zalewski
> 
> 
> 
> ___
> 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.



[Freesurfer] recon-all compared to dev table

2015-05-07 Thread zalewk
Dear freesurfer team,

I'm very new to freesurfer, and I am currently working my way through the 
recon-all dev table functions (listed here: 
http://freesurfer.net/fswiki/ReconAllDevTable) step-by-step in preparation for 
processing a large amount of participant volumetric data. While doing so I've 
noticed some inconsistencies between the dev table and the series of functions 
called by the recon-all command.

For example:
-The apas2aseg function listed in the dev table does not exist in my bin file 
(nor does it appear to be called by recon-all).
-The cortical ribbon output occurs after the three cortical parcellation 
steps/creation of the anatomical.stats files (instead of prior to these steps 
like the dev table suggests)
-The MNI intensity correction (the mri_nu_correct.mni function) is not called 
following the skull-stripping.
I downloaded the latest version of freesurfer (5.3.0) last week so it should be 
up-to-date. 

Thank you for taking the time to answer my questions,
-Kody J. Zalewski



___
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.