diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index c34f9cb514..d923051e32 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -257,6 +257,9 @@ The keyword for the heading must be one of the following: - example - quote +Do not put [macros](#using-macros) in admonitions, +as this will likely not give the output you expect. + ## Using macros We use [mkdocs-macros](https://mkdocs-macros-plugin.readthedocs.io/en/latest/) diff --git a/src/modality-specific-files/behavioral-experiments.md b/src/modality-specific-files/behavioral-experiments.md index aa17cc3757..b27592cad4 100644 --- a/src/modality-specific-files/behavioral-experiments.md +++ b/src/modality-specific-files/behavioral-experiments.md @@ -1,5 +1,11 @@ # Behavioral experiments (with no neural recordings) +!!! example "Example datasets" + + Datasets containing behavioral data can be found + in the [BIDS examples repository](https://bids-standard.github.io/bids-examples/#behavioral) + and can be used as helpful guidance when curating new datasets. + {{ MACROS___make_filename_template("raw", datatypes=["beh"]) }} -In addition to logs from behavioral experiments performed alongside imaging data -acquisitions, one can also include data from experiments performed with no neural -recordings. -The results of those experiments can be stored in the `beh` directory using the same -formats for event timing (`_events.tsv`), metadata (`_events.json`), +In addition to logs from behavioral experiments +performed alongside imaging data acquisitions, +one MAY also include data from experiments +performed with no neural recordings. +The results of those experiments MAY be stored in the `beh` directory +using the same formats for event timing (`_events.tsv`), +metadata (`_events.json`), physiological (`_physio.tsv.gz`, `_physio.json`) and other continuous recordings (`_stim.tsv.gz`, `_stim.json`) as for tasks performed during MRI, electrophysiological or other neural recordings. -Additionally, events files that do not include the mandatory `onset` and -`duration` columns can still be included, but should be labeled `_beh.tsv` -rather than `_events.tsv`. +Additionally, events files +that do not include the mandatory `onset` and `duration` columns +MAY be included, +but MUST be labeled `_beh.tsv` rather than `_events.tsv`. ## Sidecar JSON (`*_beh.json`) diff --git a/src/modality-specific-files/task-events.md b/src/modality-specific-files/task-events.md index c3822094a5..f4fa4dbdf6 100644 --- a/src/modality-specific-files/task-events.md +++ b/src/modality-specific-files/task-events.md @@ -27,9 +27,9 @@ Each task events file REQUIRES a corresponding task data file. It is also possible to have a single `events.tsv` file describing events for all participants and runs (see [Inheritance Principle](../common-principles.md#the-inheritance-principle)). -As with all other tabular data, `events.tsv` files MAY be accompanied by a JSON -file describing the columns in detail (see -[Tabular Files](../common-principles.md#tabular-files)). +As with all other tabular data, `events.tsv` files MAY be accompanied +by a JSON file describing the columns in detail +(see [Tabular Files](../common-principles.md#tabular-files)). The tabular files consists of one row per event and a set of REQUIRED and OPTIONAL columns: @@ -44,26 +44,30 @@ and a guide for using macros can be found at The content of `events.tsv` files SHOULD be sorted by values in the `onset` column. -Note for MRI data: -If any acquired scans have been discarded before forming the imaging data file, -ensure that an `onset` of 0 corresponds to the time the first image was stored. -For example in case there is an in scanner training phase that -begins before the scanning sequence has started events from this sequence should -have negative onset time counting down to the beginning of the acquisition of -the first volume. - -Note regarding the precision of numeric metadata: -It is RECOMMENDENDED that dataset curators specify numeric metadata like `onset` and -`duration` with as much decimal precision as is reasonable in the context of the experiment. -For example in an EEG experiment with devices operating at 1000 Hz sampling frequency, -dataset curators SHOULD specify **at least** 3 figures after the decimal point. - -An arbitrary number of additional columns can be added. Those allow describing -other properties of events that could be later referenced in modeling and +An arbitrary number of additional columns can be added. +Those allow describing other properties of events that could be later referenced in modeling and hypothesis extensions of BIDS. Note that the `trial_type` and any additional columns in a TSV file SHOULD be documented in an accompanying JSON sidecar file. +!!! note "Regarding the precision of numeric metadata" + + For the precision of numeric metadata, + it is RECOMMENDENDED that dataset curators specify numeric metadata like `onset` and + `duration` with as much decimal precision as is reasonable in the context of the experiment. + For example in an EEG experiment with devices operating at 1000 Hz sampling frequency, + dataset curators SHOULD specify **at least** 3 figures after the decimal point. + +!!! note "For fMRI data" + + For fMRI data + if any acquired scans have been discarded before forming the imaging data file, + ensure that an `onset` of 0 corresponds to the time the first image was stored. + For example in case there is an in scanner training phase that + begins before the scanning sequence has started events from this sequence should + have negative onset time counting down to the beginning of the acquisition of + the first volume. + Example: