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
Currently template-space files derived from C-PAC are labeled space-template which does not differentiate different-template-spaced files from one another.
I'm backburnering in favor of FCP-INDI/TheWay#8. I case someone else picks this up before I get back to it, I started a branch (templates/MNI) that so far just adds a function (lookup_identifier) to look up the standard identifier based on a regex of the in-container filename. So far the lookup table only includes two MNI spaces.
'''Function to return a standard template identifier for a packaged template, if known. Otherwise, returns the literal string 'template' Parameters ---------- template_path : str Returns ------- identifier : str Examples -------- >>> lookup_identifier('/usr/share/fsl/5.0/data/standard/' ... 'MNI152_T1_1mm_brain.nii.gz') 'MNI152NLin6ASym' >>> lookup_identifier('/code/CPAC/resources/templates/' ... 'tpl-MNI152NLin2009cAsym_res-01_label-brain_' ... 'probseg.nii.gz') 'MNI152NLin2009cAsym' >>> lookup_identifier('/cpac_templates/chd8_functional_template_sk.nii') 'template' '''
Related problem
Currently template-space files derived from C-PAC are labeled
space-template
which does not differentiate different-template-spaced files from one another.Proposed feature
Use standard template identifiers like
space-MNI152NLin2009
Acceptance criteria
space-
entitySpatialReference
included in JSON sidecarAlternatives
No response
Additional context
Related:
monkey
andnhp-macaque
#26The text was updated successfully, but these errors were encountered: