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: src/modality-specific-files/physiological-recordings.md
+9-19Lines changed: 9 additions & 19 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -371,7 +371,7 @@ A guide for using macros can be found at
371
371
},
372
372
}) }}
373
373
374
-
## Physiology "events"
374
+
###Physiology "events"
375
375
376
376
Discontinuous data associated with continuous recordings
377
377
stored in `<matches>_physio.tsv.gz` files MAY be specified
@@ -510,13 +510,9 @@ the `OnsetSource` is set to `"n/a"` in `sub-01_task-nback_physioevents.json`:
510
510
511
511
<!-- #!# This needs to be fixed -->
512
512
513
-
### 2. JSON Data files
514
-
515
-
Metadata sidecar files (`<matches>_physio.json`) **SHOULD** define the field `PhysioType`. This field indicates a specific type of formatting, rather than a physiological modality. The `PhysioType``"generic"` value, being the default, **MUST** be assumed if the `PhysioType` metadata is not defined.
513
+
**JSON Data files**. All metadata we are proposing are either **OPTIONAL** or **RECOMMENDED**, and they are meant to enrich the current `"generic"``PhysioType`. However, we are also suggesting the introduction of a `"enriched"``PhysioType`, that will differ from `"generic"` because one proposed metadata, `MeasureType`, will be **REQUIRED** rather than **RECOMMENDED**. Equally, the `Units` metadata will be **REQUIRED** instead of **RECOMMENDED** in this case.
516
514
517
-
All metadata we are proposing are either **OPTIONAL** or **RECOMMENDED**, and they are meant to enrich the current `"generic"``PhysioType`. However, we are also suggesting the introduction of a `"enriched"``PhysioType`, that will differ from `"generic"` because one proposed metadata, `MeasureType`, will be **REQUIRED** rather than **RECOMMENDED**. Equally, the `Units` metadata will be **REQUIRED** instead of **RECOMMENDED** in this case.
518
-
519
-
Compared to the current BIDS specification (1.10.0), at the file level we are adding one metadata, the **OPTIONAL**`SubjectPosition`, indicating the position of the subject during the data collection (see section 2.1).
515
+
Compared to the current BIDS specification (1.10.0), at the file level we are adding one metadata, the **OPTIONAL**`SubjectPosition`, indicating the position of the subject during the data collection (see below "Metadata fields used in top level metadata").
520
516
521
517
When specifying column names, columns **MUST** have unique names. All such data columns **MUST** be appropriately defined in the JSON metadata.
522
518
@@ -528,39 +524,33 @@ When specifying column names, columns **MUST** have unique names. All such data
528
524
"SamplingFrequency": 1000,
529
525
"SubjectPosition": "sitting",
530
526
"PhysioType": "enriched",
531
-
...
532
527
"screda1": {
533
528
"MeasureType": "EDA-phasic",
534
529
"Units": "mS",
535
530
"Placement": "Thenar",
536
-
...
537
531
},
538
532
"screda2": {
539
533
"MeasureType": "EDA-tonic",
540
534
"Units": "mS",
541
535
"Placement": "Hypothenar",
542
-
...
543
536
},
544
537
"ecg": {
545
538
"MeasureType": "ECG",
546
539
"Units": "mV",
547
540
"Placement": "II",
548
-
...
549
541
},
550
542
"ppg": {
551
543
"MeasureType": "PPG",
552
544
"Units": "au",
553
545
"Placement": "Right earlobe",
554
-
...
555
-
},
556
-
...
546
+
}
557
547
}
558
548
```
559
549
560
-
As described in the following table (Section 2.2), this BEP is adding a few metadata to describe columns.
550
+
As described in the table below ("Metadata fields for column description."), this BEP is adding a few metadata to describe columns.
561
551
562
552
- The most important one is `MeasureType`, a **RECOMMENDED** metadata that indicates the actual nature of the data in the column.
563
-
- This metadata value is a string that **MUST** come from a set of keywords (see table 2.2).
553
+
- This metadata value is a string that **MUST** come from a set of keywords.
564
554
- This set of keywords can be expanded in the future to include more physiological modalities.
565
555
- When the file-level metadata `PhysioType` is `"enriched"`, `MeasureType` becomes a **REQUIRED** field for each column.
566
556
@@ -590,15 +580,15 @@ More information about the metadata entities contained in the JSON files can be
590
580
591
581
---
592
582
593
-
### 2.1 Metadata fields used in top level metadata
0 commit comments