Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Identify which parcellations are canonical #49

Open
gkiar opened this issue Nov 21, 2022 · 3 comments
Open

Identify which parcellations are canonical #49

gkiar opened this issue Nov 21, 2022 · 3 comments
Assignees

Comments

@gkiar
Copy link

gkiar commented Nov 21, 2022

Related to #48

So that users can identify which templates are canonical, versus those that have been transformed in someway, it would be important to include this information. In an MVP, this can just be adding a dictionary key of "is different", but in a perfect world, there should also be details on the transformations themselves.

@ebridge2 ebridge2 self-assigned this Nov 21, 2022
@ebridge2
Copy link
Collaborator

On or before Jan 31, 2023 for schaeffer parcellation at 1mm resolution

@Lawreros
Copy link
Collaborator

Been going through the parcellations (albeit slowly) and checking. What should be the protocol for the removal of ROIs due to downsampling? Just have None in the json file for that intensity values or make unique json files for each resolution?

@gkiar
Copy link
Author

gkiar commented Nov 30, 2022

I would first suggest looking for a version of the canonical parcellations that are already downsampled to see if they can be adopted, rather than regenerated. Then, whatever you do, documentation will be key. I do think that each image file should have a corresponding json file, so something in that vein would be my lean.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants