From c5f0b7955491072ff67921527ebd3a01a2dc0c93 Mon Sep 17 00:00:00 2001 From: Remi Gau Date: Sun, 3 Apr 2022 08:10:49 +0200 Subject: [PATCH 01/10] [DATALAD RUNCMD] add filetree macro comment === Do not change lines below === { "chain": [], "cmd": "sed -i '/^.*make_filetree_example/i \\' ./src/**/*.md", "exit": 0, "extra_inputs": [], "inputs": [], "outputs": [], "pwd": "." } ^^^ Do not change lines above ^^^ --- .../01-magnetic-resonance-imaging-data.md | 32 +++++++++++++ .../02-magnetoencephalography.md | 8 ++++ .../04-intracranial-electroencephalography.md | 8 ++++ .../05-task-events.md | 12 +++++ ...logical-and-other-continuous-recordings.md | 12 +++++ .../10-microscopy.md | 20 ++++++++ src/05-derivatives/02-common-data-types.md | 20 ++++++++ src/05-derivatives/03-imaging.md | 48 +++++++++++++++++++ src/99-appendices/06-meg-file-formats.md | 40 ++++++++++++++++ src/99-appendices/11-qmri.md | 36 ++++++++++++++ 10 files changed, 236 insertions(+) diff --git a/src/04-modality-specific-files/01-magnetic-resonance-imaging-data.md b/src/04-modality-specific-files/01-magnetic-resonance-imaging-data.md index 41969de679..bfb492d7d3 100644 --- a/src/04-modality-specific-files/01-magnetic-resonance-imaging-data.md +++ b/src/04-modality-specific-files/01-magnetic-resonance-imaging-data.md @@ -273,6 +273,10 @@ which are typically used in `part-mag`/`part-phase` or `part-real`/`part-imag` pairs of files. For example: + {{ MACROS___make_filetree_example( { "sub-01": { @@ -426,6 +430,10 @@ for more information on `dir` field specification. Multi-echo data MUST be split into one file per echo using the [`echo-`](../99-appendices/09-entities.md#echo) key-value pair. For example: + {{ MACROS___make_filetree_example( { "sub-01": { @@ -456,6 +464,10 @@ name with the exception of the `part-` or `part-` key/valu For example: + {{ MACROS___make_filetree_example( { "sub-01": { @@ -540,6 +552,10 @@ additional terms and their definitions. Example: + {{ MACROS___make_filetree_example( { "sub-01": { @@ -707,6 +723,10 @@ two runs each, and the intent of the researcher is that all of them are part of a unique multipart scan, then they will tag all four runs with the same `MultipartID` (shown at the right-hand side of the file listing): + {{ MACROS___make_filetree_example( { "sub-1": { @@ -723,6 +743,10 @@ same `MultipartID` (shown at the right-hand side of the file listing): If, conversely, the researcher wanted to store two multipart scans, one possibility is to combine matching phase-encoding directions: + {{ MACROS___make_filetree_example( { "sub-1": { @@ -739,6 +763,10 @@ is to combine matching phase-encoding directions: Alternatively, the researcher's intent could be combining opposed phase-encoding runs instead: + {{ MACROS___make_filetree_example( { "sub-1": { @@ -755,6 +783,10 @@ runs instead: The `MultipartID` metadata MAY be used with the [`acq-