the problem is that the average surface has less surface area than any
individual. We keep track of this in the surface file itself (try mris_info
on it), then correct for it when we need to.
cheers,
Bruce
On Tue, 9 Jun 2009, Alex Fornito wrote:
No, sorry. What is the error?
On 09/06/2009
No, sorry. What is the error?
On 09/06/2009 17:31, "Douglas N Greve" wrote:
> Does this workaround account for the error in the raw area unavoidable
> on an average surface? If not, are you aware of it and is it important
> for your analysis?
>
> doug
>
> Alex Fornito wrote:
>> Rudolph's work
Does this workaround account for the error in the raw area unavoidable
on an average surface? If not, are you aware of it and is it important
for your analysis?
doug
Alex Fornito wrote:
Rudolph's workaround seems to do the trick.
Thanks!
On 06/06/2009 18:16, "Bruce Fischl" wrote:
yeah,
Rudolph's workaround seems to do the trick.
Thanks!
On 06/06/2009 18:16, "Bruce Fischl" wrote:
> yeah, I guess we disabled it since the surface area isn't representative
> of individual subjects. We could either change it to a warning with a
> -force flag or something, or you could run mri_annot
yeah, I guess we disabled it since the surface area isn't representative
of individual subjects. We could either change it to a warning with a
-force flag or something, or you could run mri_annotation2label and run
label_area on the individual labels.
Do you really want the surface area on the
-Original Message-
From: Alex Fornito
Thanks,
I did as you suggested, but got a different error telling me that
mris_anatomical_stats cannot be used with fsaverage as it is an average
subject.
You can try the following "hack": convert the annotation to a series of
labels, and t
Thanks,
I did as you suggested, but got a different error telling me that
mris_anatomical_stats cannot be used with fsaverage as it is an average
subject.
I am running v 4.2.0. Would I be able to run stats on fsaverage using a new
freesurfer version, or is there some other way around this?
I am
Hi Alex,
if all you care about is surface area you can probably just copy the
wm.mgz from any subject into the fsaverage/mri dir. Other stats will of
course then be incorrect. You also have to be careful as the fsaverage
surfaces contain less surface area (due to averaging) than individual
su
Hi,
I'm playing around with different ways of generating custom annotation files
using the fsaverage surface, and would like to estimate the surface area of
each ROI. I tried running mris_anatomical stats, but it seems to required
wm.mgz, which is not contained in the fsaverage directories (please
