From e3ce5ffe7439477744ff41d862bd269f367aa9f1 Mon Sep 17 00:00:00 2001 From: Chris Markiewicz Date: Thu, 10 Aug 2023 17:32:30 -0400 Subject: [PATCH 1/2] Move from atlas- to seg- in derivatives --- src/derivatives/imaging.md | 25 ++++++++++++------------- 1 file changed, 12 insertions(+), 13 deletions(-) diff --git a/src/derivatives/imaging.md b/src/derivatives/imaging.md index b802d6c309..bcd653da08 100644 --- a/src/derivatives/imaging.md +++ b/src/derivatives/imaging.md @@ -153,8 +153,8 @@ Template: A binary (1 - inside, 0 - outside) mask in the space defined by the [`space` entity](../appendices/entities.md#space). If no transformation has taken place, the value of `space` SHOULD be set to `orig`. -If the mask is an ROI mask derived from an atlas, then the [`label` entity](../appendices/entities.md#label)) SHOULD -be used to specify the masked structure +If the mask is an ROI mask derived from an atlas segmentation, +then the [`label` entity](../appendices/entities.md#label)) SHOULD be used to specify the masked structure (see [Common image-derived labels](#common-image-derived-labels)), and the `Atlas` metadata SHOULD be defined. @@ -229,10 +229,10 @@ structure may be concatenated in a single file. Segmentations may be defined in a volume (labeled voxels), a surface (labeled vertices) or a combined volume/surface space. -If the segmentation can be derived from different atlases, -the [`atlas` entity](../appendices/entities.md#atlas) MAY be used to -distinguish the different segmentations. -If so, the `Atlas` metadata SHOULD also be defined. +If the segmentation can be generated in different ways, +for example, following an atlas segmentation, +the [`seg` entity](../appendices/entities.md#atlas) MAY be used to +distinguish the name of the segmentation used. The following section describes discrete and probabilistic segmentations of volumes, followed by discrete segmentations of surface/combined spaces. @@ -268,7 +268,7 @@ Template: / sub-