Dear FreeSurfers,
After adding WMCP to a number of my subjects (which corrected the problem), I retrieved to cortical and subcortical volumes from my subjects using the "aparcstats2table". I had used "aparcstats2table" before and after adding the control points. Accurately, the regions I wanted to change, did change in volume. However, the subcortical volumes post WMCP changed a lot as well? Some regions changed more than 20% after adding WMCP to other regions? Is this normal? Should I go with the original "subcortical" segmentation volumes, or the new ones? Is this part of the known bug in version 5.1.0 mentioned in the release notes about "running recon-all" a second time? Please advise?
Sincerely , Mark Fletcher
Hi Mark
it's hard to say if it's a "bug", but it is definitely a change in behavior that will go away with 5.2 (that is, we will no longer regenerate the aseg when you add control points).
cheers Bruce On Wed, 17 Oct 2012, Mark Fletcher wrote:
Dear FreeSurfers,
After adding WMCP to a number of my subjects (which corrected the problem), I retrieved to cortical and subcortical volumes from my subjects using the "aparcstats2table". I had used "aparcstats2table" before and after adding the control points. Accurately, the regions I wanted to change, did change in volume. However, the subcortical volumes post WMCP changed a lot as well? Some regions changed more than 20% after adding WMCP to other regions? Is this normal? Should I go with the original "subcortical" segmentation volumes, or the new ones? Is this part of the known bug in version 5.1.0 mentioned in the release notes about "running recon-all" a second time? Please advise?
Sincerely , Mark Fletcher
freesurfer@nmr.mgh.harvard.edu