Skip to content

dhcpAsym cohort-42 label file overlaid onto midthickness marks medial wall as frontal/parietal lobe, cingulate gyrus #1

@joey-scanga

Description

@joey-scanga

Hello!

I'm a programmer with Dr. Chad Sylvester's lab at WashU, and we were attempting to use the dhcpAsym-cohort-42 templates to resample native surfaces for neonates generated by Nibabies using their "MCRIBS" reconstruction method into dHCP-den-32k space, since MCRIBS generates native spheres registered to the week 42 dHCP standard spheres.

We've tried performing this resampling post-Nibabies by running the wb_comand -surface-resample command, inputting the subject's outputted native sphere, the subject's native sphere in register with dHCP space, and the standard dHCP 42-week sphere with a density of 32k vertices, for each hemisphere. We're also using the BARYCENTRIC option when running this command.

We've been having some mixed results when using these inputs -- the problem may either be on the MCRIBS surface-reconstruction side, where the native spheres supposedly in register with dHCP space aren't as well-registered as they could be, or the standard-space 42-week cohort spheres we're pulling from TemplateFlow aren't the ones we should be using.

In the process of troubleshooting, I wanted to see what the 32k-density label files looked like overlaid onto the template midthickness surface GIFTIs in Workbench -- it appears even the label file seems to have some registration issues, noticeably around the medial wall area, where areas marked as frontal/parietal lobe and cingulate gyrus encroach pretty deeply into the medial wall. Here's a screenshot:

Image

(I also had to rename the label files to load them in, replacing the underscore before label.gii with another period).

Am I overlaying the correct label file here?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions