Thank You Doug !

We created a specific label for each subject using cmd>

mri_label2label
 --srcsubject fsaverage --srclabel (the ROI.label created in qdec) 
--trgsubject SUBJECT_NAME --trglabel 
$SUBJECTS_DIR/SUBJECT_NAME/label/ROIx-lh.label --regmethod surface 
--hemi lh

after that>
mris_anatomical_stats -l (ROIx-lh.label address) -b SUBJECT_NAME lh

the results are the same,
qdec: X>Y
mris: X<Y

Did we miss another step again ?

Sincerely,
Alex.


--- En date de : Ven 25.2.11, Douglas N Greve <[email protected]> a 
écrit :

De: Douglas N Greve <[email protected]>
Objet: Re: [Freesurfer] Qdec - ROI - different thickness results
À: "Alex Hanganu" <[email protected]>
Cc: "FS Mailing List" <[email protected]>
Date: Vendredi 25 février 2011, 17h12

sorry, I should have said mri_label2label, not mri_surf2surf
doug

Alex Hanganu wrote:
> right, qdec shows
> healthy (X) > patients (Y)
>
> mris_anatomical_stats show:
> Y > X
>
> but I didn't do mri_surf2surf, I just copied the ROI.label in every 
> subjects /label/ directory.
>
> Thank you for your help Doug !
>
> Have a great day,
>
> Alex.
>
>
> --- En date de : *Ven 25.2.11, Douglas N Greve 
> /<[email protected]>/* a écrit :
>
>
>     De: Douglas N Greve <[email protected]>
>     Objet: Re: [Freesurfer] Qdec - ROI - different thickness results
>     À: "Alex Hanganu" <[email protected]>
>     Cc: "FS Mailing List" <[email protected]>
>     Date: Vendredi 25 février 2011, 16h52
>
>     blue means that X>Y. So that sounds like it is compatible with
>     your ROI results, yes?
>     doug
>
>     Alex Hanganu wrote:
>     > Dear Freesurfer Experts,
>     >
>     > In qdec for question:
>     > "Does the average thickness differ between X and Y"
>     > we received blue colored regions, meaning that thickness for
>     group Y is lower then X ?
>     >
>     > We created ROIs for each region, and extracted cortical
>     thickness for each ROI for each subject using mris_anatomical_stats.
>     >
>     > in results: for each ROI, mean cortical thickness of Y group are
>     higher then X.
>     >
>     > is it a mistake, or the question was misunderstood ?
>     >
>     > Sincerely,
>     > Alex.
>     >
>     >
>     >
>     ------------------------------------------------------------------------
>     >
>     > _______________________________________________
>     > Freesurfer mailing list
>     > [email protected]
>     </mc/[email protected]>
>     > https://mail.nmr.mgh.harvard.edu/mailman/listinfo/freesurfer
>
>     -- Douglas N. Greve, Ph.D.
>     MGH-NMR Center
>     [email protected] </mc/[email protected]>
>     Phone Number: 617-724-2358 Fax: 617-726-7422
>
>     Bugs: surfer.nmr.mgh.harvard.edu/fswiki/BugReporting
>     FileDrop: www.nmr.mgh.harvard.edu/facility/filedrop/index.html
>
>
>
>     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.
>
>

-- 
Douglas N. Greve, Ph.D.
MGH-NMR Center
[email protected]
Phone Number: 617-724-2358 
Fax: 617-726-7422

Bugs: surfer.nmr.mgh.harvard.edu/fswiki/BugReporting
FileDrop: www.nmr.mgh.harvard.edu/facility/filedrop/index.html




      
_______________________________________________
Freesurfer mailing list
[email protected]
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.

Reply via email to