From 7626992505dcdaae0c71023f3137a616d28b1b1d Mon Sep 17 00:00:00 2001 From: melanieganz Date: Wed, 24 Jan 2024 16:24:41 +0100 Subject: [PATCH] case 3 files renamed --- src/atlas.md | 229 +++++++++++++++++++++++++++++++++++++++++++-------- 1 file changed, 196 insertions(+), 33 deletions(-) diff --git a/src/atlas.md b/src/atlas.md index 226fdfb020..fdce6a84df 100644 --- a/src/atlas.md +++ b/src/atlas.md @@ -15,7 +15,7 @@ The usage of [_desc-](schema/objects/entities.yaml#desc) is currently discourage ## Directory Structure BIDS-Atlas focuses on the utilization of atlases while also allowing their sharing. Thus, atlases are either stored within a dedicated `atlas` directory at the BIDS root directory (comparable to the `code` directory), such files are the non-altered/original atlases. In the second case, they are stored within the directory of a given subject’s derivatives representing the altered/derived/applied atlases. -### Representing the atlas at the dataset level +### Representing an atlas as a dataset The first option refers to atlases that were not altered, e.g. via spatial transformations and/or resampling or applied to data and thus their initial inclusion/utilization in a given dataset. If there is only this form of atlases (i.e., the tool used), they are always shared at the root folder and everything else is under derivatives. This allows validating any @@ -33,9 +33,8 @@ The default way of storage of the non-altered atlas at the root directory looks atlas-