Hi Noam
we should just preserve whatever index they use
cheers
Bruce
On Fri, 30 Oct 2015, Peled,
Noam wrote:
>
> Hey Bruce,
> I meant for the Lausanne250 parcellation (http://journals.plos.org/plosone/a
> rticle?id=10.1371/journal.pone.0048121)
> The problem is with the #index column. To creat
Hey Bruce,
I meant for the Lausanne250 parcellation
(http://journals.plos.org/plosone/article?id=10.1371/journal.pone.0048121)
The problem is with the #index column. To create a custom lookup table, I need
to know what is the #index each label gets in the output file of
mri_aparc2aseg.
I want to
You can also load the new segmentation into freeview and see the
segmentation number that each gets. If you can get the color table out
of the annotation, then the segmentation number will be 1000+ that
number (left hemi) and 2000+that number for the right
On 10/30/15 8:30 AM, Bruce Fischl w
what is the laus250 parcellation? The lookup tables are in text so you
should be able to open one in an editor and see what the format is. It's
pretty straightforward. # lines are comments, then it is
cheers
Bruce
On Fri, 30 Oct 2015, Peled, Noam wrote:
> Hey all,
> I used mri_aparc2as
Hey all,
I used mri_aparc2aseg to map the cortical labels from the laus250 parcellation.
Now I need to create a new lookup table, mainly for displaying the labels'
names in freeview.
How can I know what id each label gets in my new laus+aseg.mgz file?
Thanks,
Noam
___
