Skip to content

Commit

Permalink
Apply suggestions from code review
Browse files Browse the repository at this point in the history
  • Loading branch information
Remi-Gau authored Oct 6, 2020
1 parent 97b123e commit d1c3be8
Show file tree
Hide file tree
Showing 3 changed files with 3 additions and 3 deletions.
2 changes: 1 addition & 1 deletion src/03-modality-agnostic-files.md
Original file line number Diff line number Diff line change
Expand Up @@ -161,7 +161,7 @@ participants.json
```

The purpose of this RECOMMENDED file is to describe properties of participants
such as age, sex, handedness and so forth.
such as age, sex, handedness.
In case of single-session studies, this file has one compulsory column
`participant_id` that consists of `sub-<label>`, followed by a list of optional
columns describing participants.
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -113,7 +113,7 @@ SHOULD be present:
| MiscChannelCount | RECOMMENDED | [integer][] | Number of miscellaneous analog channels for auxiliary signals. |
| TriggerChannelCount | RECOMMENDED | [integer][] | Number of channels for digital (TTL bit level) triggers. |
| RecordingDuration | RECOMMENDED | [number][] | Length of the recording in seconds (e.g., 3600). |
| RecordingType | RECOMMENDED | [string][] | Defines whether the recording is `"continuous"`, `"discontinuous"` or `"epoched"`, where `"epoched"` is limited to time windows about events of interest (e.g., stimulus presentations, subject responses, and so forth). |
| RecordingType | RECOMMENDED | [string][] | Defines whether the recording is `"continuous"`, `"discontinuous"` or `"epoched"`, where `"epoched"` is limited to time windows about events of interest (e.g., stimulus presentations, subject responses). |
| EpochLength | RECOMMENDED | [number][] | Duration of individual epochs in seconds (e.g., 1) in case of epoched data. |
| ContinuousHeadLocalization | RECOMMENDED | [boolean][] | `true` or `false` value indicating whether continuous head localisation was performed. |
| HeadCoilFrequency | RECOMMENDED | [number][] or [array][] of [numbers][] | List of frequencies (in Hz) used by the head localisation coils (‘HLC’ in CTF systems, ‘HPI’ in Elekta, ‘COH’ in BTi/4D) that track the subject’s head position in the MEG helmet (e.g., `[293, 307, 314, 321]`). |
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -253,7 +253,7 @@ SHOULD be present:
| reference | OPTIONAL | Specification of the reference (e.g., 'mastoid', 'ElectrodeName01', 'intracranial', 'CAR', 'other', 'n/a'). If the channel is not an electrode channel (e.g., a microphone channel) use `n/a`. |
| group | OPTIONAL | Which group of channels (grid/strip/seeg/depth) this channel belongs to. This is relevant because one group has one cable-bundle and noise can be shared. This can be a name or number. Note that any groups specified in `_electrodes.tsv` must match those present here. |
| sampling_frequency | OPTIONAL | Sampling rate of the channel in Hz. |
| description | OPTIONAL | Brief free-text description of the channel, or other information of interest (e.g., position (e.g., "left lateral temporal surface", and so on)). |
| description | OPTIONAL | Brief free-text description of the channel, or other information of interest (e.g., position (e.g., "left lateral temporal surface")). |
| notch | OPTIONAL | Frequencies used for the notch filter applied to the channel, in Hz. If no notch filter applied, use n/a. |
| status | OPTIONAL | Data quality observed on the channel (good/bad). A channel is considered bad if its data quality is compromised by excessive noise. Description of noise type SHOULD be provided in `[status_description]`. |
| status_description | OPTIONAL | Freeform text description of noise or artifact affecting data quality on the channel. It is meant to explain why the channel was declared bad in `[status]`. |
Expand Down

0 comments on commit d1c3be8

Please sign in to comment.