Skip to content

Commit 5f70048

Browse files
yarikopticRemi-Gau
andauthored
Include entity-less "scans.json" into an example of inheritance principle (#1945)
* Include entity-less "scans.json" into an example of inheritance principle Clarifies #789 * Apply suggestions from code review --------- Co-authored-by: Remi Gau <[email protected]>
1 parent 6e2874c commit 5f70048

File tree

1 file changed

+7
-1
lines changed

1 file changed

+7
-1
lines changed

src/common-principles.md

Lines changed: 7 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -739,9 +739,11 @@ A guide for using macros can be found at
739739
"sub-01_task-rest_acq-default_bold.nii.gz": "",
740740
"sub-01_task-rest_acq-longtr_bold.nii.gz": "",
741741
"sub-01_task-rest_acq-longtr_bold.json": "",
742-
}
742+
},
743+
"sub-01_scans.tsv": "",
743744
},
744745
"task-rest_bold.json": "",
746+
"scans.json": ""
745747
}
746748
) }}
747749

@@ -773,6 +775,10 @@ the value for field "`RepetitionTime`" is therefore overridden to the value `3.0
773775
The value for field "`EchoTime`" remains applicable to that image, and is not unset by its
774776
absence in the metadata file at the lower level (rule 5.b; corollary 3).
775777

778+
A single `scans.json`, without any entity in the filename at the top level,
779+
is applicable to describe columns of the `sub-01_scans.tsv`
780+
and any other `_scans.tsv` potentially present in the dataset for other subjects.
781+
776782
Example 2: Impermissible use of multiple metadata files at one directory level (rule 4)
777783

778784
<!-- This block generates a file tree.

0 commit comments

Comments
 (0)