Skip to content

Commit

Permalink
Remove some "bad latin"
Browse files Browse the repository at this point in the history
  • Loading branch information
yarikoptic committed Dec 19, 2024
1 parent 7bc17cc commit d5fef1f
Show file tree
Hide file tree
Showing 2 changed files with 8 additions and 6 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -265,7 +265,7 @@ c234 n/a 1 SYNC mV 1000 good
```

Note: In many datasets multiple sets of identifiers are used for probes, electrodes and channels.
We RECOMMEND to include alternative sets of identifiers, e.g. identifiers that enumerate electrodes according to their spatial arrangement, as additional custom columns in the .tsv file.
We RECOMMEND to include alternative sets of identifiers, for instance identifiers that enumerate electrodes according to their spatial arrangement, as additional custom columns in the `.tsv` file.

**Recommended Channel Type Values**

Expand Down Expand Up @@ -611,7 +611,7 @@ contain a `task` entity in their name. For the nose-poke task, additional behavi

This dataset contains intracellular data from slices acquired from two subjects (20220101-A and 20220101B). Details about the subjects and the sample generation are documented in the samples (tsv/json) files. Data of each subject is stored in separate subject directories (top level directories), each of which contains an ‘ephys’ subdirectory. Note that there is no session-level directory in this case. Here, we choose the option of having “multiple tasks/runs in separate files” as described in 3.81., to demonstrate the high level of readability offered by the filenames in this case.

For the first subject only a single sample (a cell for patch-clamp terminology) was extracted (sample-cell001), on which two recordings (runs 1 and 2) were performed. Here, the `scans.tsv` file can be used to store information such as the starting recording times. The detailed information on the recording channel (e.g. also the recording mode used) is stored in the `channels.tsv` which, in this case, is common to all available recordings. The probes and electrodes files provide information on the pipette and solutions used for the recordings and are also shared for the two data files.
For the first subject only a single sample (a cell for patch-clamp terminology) was extracted (sample-cell001), on which two recordings (runs 1 and 2) were performed. Here, the `scans.tsv` file can be used to store information such as the starting recording times. The detailed information on the recording channel (such as the recording mode used) is stored in the `channels.tsv` which, in this case, is common to all available recordings. The probes and electrodes files provide information on the pipette and solutions used for the recordings and are also shared for the two data files.

For the second subject two samples (sample-cell003 and sample-cell004) were extracted and a single recording performed on each of them. Each recording was performed using a different probe (listed in the probes.tsv) having specific electrode and channel information. Therefore, each data file has a dedicated channel and electrode file with the same name as the data file.

Expand Down
10 changes: 6 additions & 4 deletions src/schema/objects/columns.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -120,7 +120,7 @@ channel_label:
description: |
Human readable identifier. Use this name to specify the
content of signals not generated by electrodes. For example,
'DAQ internal synchronization signals', 'behavioral signals', 'behavioral cues', etc.
'DAQ internal synchronization signals', 'behavioral signals', 'behavioral cues'.
type: string
color:
name: color
Expand Down Expand Up @@ -928,9 +928,11 @@ trial_id:
display_name: Trial ID
description: |
If the data entity belongs to set of data_entities forming a trial,
they have to be linked to the same trial_id. This can be used to e.g. group stimulation and response records.
The optional `trial_type` events.tsv column can be used to provide the further information on the trial like
`electric stimulation`,`rest`, or `pharmaceutical stimulation`, etc.
they have to be linked to the same trial_id.
This can be used for example for group stimulation and response records.
The optional `trial_type` events.tsv column can be used to provide
further information on the trial like such as `electric stimulation`,
`rest`, or `pharmaceutical stimulation`.
type: string
trial_type:
name: trial_type
Expand Down

0 comments on commit d5fef1f

Please sign in to comment.