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
Copy file name to clipboardExpand all lines: source/event_definitions/index.rst
+40Lines changed: 40 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,6 +5,46 @@ Task events for behavioral experiments are saved as ``events.tsv`` and ``events.
5
5
6
6
In addition to the event definitions provided in the BIDS specification, M-BIDS requires event labels to be stored in an ``event_type`` column. The exact allowed event labels depend on the experiment type or benchmark challenge.
7
7
8
+
Expected file location
9
+
----------------------
10
+
11
+
Fear-conditioning event files should be stored together with the corresponding task recording files. The target folder depends on the available physiological modalities.
12
+
13
+
.. csv-table:: Table 1: Event file location by modality
"Eye-tracking only", "``beh/``", "Eye-tracking-only datasets can store task events and eye recordings in the behavioral folder."
18
+
"SCR only", "``physio/``", "Skin conductance recordings are physiological recordings and should be stored in the physiology folder."
19
+
"Eye-tracking and SCR", "``physio/``", "When physiological recordings are present together, the task recordings and corresponding events are stored in the physiology folder."
20
+
21
+
For an eye-tracking-only fear-conditioning dataset, the structure may look like this:
If both eye-tracking and SCR recordings are present, the files should be placed under ``physio/``. This placement follows the modality handling described by BEP020 and BEP045 and is supported by the BIDS importer.
0 commit comments