You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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?
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.
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.
The text was updated successfully, but these errors were encountered: