11# Templates and atlases
22
33In the following we describe how the outcomes of analyses that produce new
4- templates and [ atlases] ( schema/objects/entities.yaml #atlas) are organized
4+ templates and [ atlases] ( ../glossary.md #atlas-entities ) are organized
55as BIDS-Derivatives.
66These outcomes typically involve quantitative maps, feature maps, parcellations,
77segmentations, and other knowledge annotations such as landmarks defined with
@@ -17,20 +17,20 @@ these outcomes:
1717 <source_entities>[_space-<space>][_atlas-<label>][seg-<label>][_scale-<label>][_res-<label>][_den-<label>][_desc-<label>]_<suffix>.<extension>
1818```
1919
20- Template's [ ` suffix ` ] ( schema/objects/entities.yaml #suffix) will generally be existing BIDS raw modalities
20+ Template's [ ` suffix ` ] ( ../glossary.md #suffix-common_principles ) will generally be existing BIDS raw modalities
2121such as ` T1w ` , while it will normally take ` dseg ` , ` probseg ` , or ` mask ` to encode atlased knowledge.
22- In terms of [ ` extension ` ] ( schema/objects/entities.yaml #extension) , ` nii[.gz] ` , ` dscalar.nii[.gz] ` ,
22+ In terms of [ ` extension ` ] ( ../glossary.md #extension-common_principles ) , ` nii[.gz] ` , ` dscalar.nii[.gz] ` ,
2323` dlabel.nii[.gz] ` , ` label.gii[.gz] ` , ` tsv ` , or ` json ` .
2424
25- The [ ` atlas- ` entity] ( schema/objects/entities.yaml #atlas) is REQUIRED to encode files belonging in
25+ The [ ` atlas- ` entity] ( ../glossary.md #atlas-entities ) is REQUIRED to encode files belonging in
2626the atlas identified by the label.
2727Two entities MAY be employed along with ` atlas- ` to disentangle different realizations and scales
2828of a single atlas:
2929
30- - [ ` seg- ` ] ( schema/objects/entities.yaml #seg) is REQUIRED when a single atlas has several different
30+ - [ ` seg- ` ] ( ../glossary.md #seg-entities ) is REQUIRED when a single atlas has several different
3131 realizations (for instance, segmentations and parcellations created with different criteria) that
3232 need disambiguation.
33- - [ ` scale- ` ] ( schema/objects/entities.yaml #scale) is REQUIRED to disambiguate different atlas 'scales',
33+ - [ ` scale- ` ] ( ../glossary.md #scale-entities ) is REQUIRED to disambiguate different atlas 'scales',
3434 when the atlas has more than one 'brain unit' resolutions, typically relating to the area covered
3535 by regions.
3636
@@ -107,7 +107,7 @@ As the authors of 'Colin27' indicate, it is aligned with MNI305:
107107
108108Therefore, this pipeline potentially could have produced outputs in the realigned T1w space
109109before alignment to the MNI305 template.
110- To disambiguate in this case, we employ the [ ` space- ` ] ( schema/objects/entities.yaml #space) entity:
110+ To disambiguate in this case, we employ the [ ` space- ` ] ( ../glossary.md #space-entities ) entity:
111111
112112``` Text
113113colin27-pipeline/
@@ -229,7 +229,7 @@ MIAL67ThalamicNuclei-pipeline/
229229
230230## Filenames of derivatives with atlases in their provenance
231231
232- Like for the [ ` space- ` entity] ( schema/objects/entities.yaml #space) , outputs derived from atlases
232+ Like for the [ ` space- ` entity] ( ../glossary.md #space-entities ) , outputs derived from atlases
233233MUST employ ` atlas- ` , ` seg- ` , and ` scale- ` when necessary:
234234
235235``` Text
0 commit comments