You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In this example, `sourcedata/dicoms` is not nested inside
310
-
`sourcedata/raw`, **and only the `sourcedata/raw` subdirectory** is a BIDS-compliant dataset among `sourcedata/` subfolders.
311
-
The subdirectories of `derivatives` MAY be BIDS-compliant derivatives datasets
312
-
(see [Non-compliant derivatives](#non-compliant-derivatives) for further discussion).
313
-
The above example is a fully compliant BIDS dataset, providing a convention useful for organizing source, raw BIDS, and derived BIDS data while maintaining overall BIDS compliance.
314
-
When using this convention it is RECOMMENDED to set the `SourceDatasets`
315
-
field in `dataset_description.json` of each subdirectory of `derivatives` to:
In this example, `sourcedata/dicoms` is not nested inside
435
+
`sourcedata/raw`, **and only the `sourcedata/raw` subdirectory** is a BIDS-compliant dataset among `sourcedata/` subfolders.
436
+
The subdirectories of `derivatives` MAY be BIDS-compliant derivatives datasets
437
+
(see [Non-compliant derivatives](#non-compliant-derivatives) for further discussion).
438
+
The above example is a fully compliant BIDS dataset, providing a convention useful for organizing source, raw BIDS, and derived BIDS data while maintaining overall BIDS compliance.
439
+
When using this convention, `dataset_description.json` MUST have `DatasetType` to be set to `"project"`. It is also RECOMMENDED to set the `SourceDatasets`
440
+
field in `dataset_description.json` of each subdirectory of `derivatives` to:
0 commit comments