Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FIX] clarify TriggerChannelCount and TRIG type #1342

Merged
merged 2 commits into from
Nov 3, 2022

Conversation

sappelhoff
Copy link
Member

closes #1318

would this be what you had in mind @robertoostenveld @ftadel @teonbrooks ?

name type units description sampling_frequency low_cutoff high_cutoff notch software_filters status
UDIO001 TRIG V analogue trigger 1200 0.1 300 0 n/a good
MLC11 MEGGRADAXIAL T sensor 1st-order grad 1200 0 n/a 50 SSS bad
```
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I removed this example, because a channels.tsv example is already present below the channel types table

| EOG | Generic EOG channel |
| ECG | ElectroCardioGram (heart) |
| EMG | ElectroMyoGram (muscle) |
| TRIG | Analog (in volt) or digital (TTL bit level) trigger channel |
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The "TTL" convention applies to both the analog representation as the binary interpretation. Even in memory of a computer a bit is still represented as a voltage.

I suggest to write "Analog (TTL in Volt) or digital (binary TTL) trigger channel".

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

oh, and I would not write "bit level", as that suggests that every bit is to be represented in a separate channel. Some systems do that (like Neuromag, only for backward compatibility), but it is not so common. Most represent the bits jointly in a single numeric value.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thanks! implemented in eaa0dfb

@codecov
Copy link

codecov bot commented Oct 25, 2022

Codecov Report

Base: 88.39% // Head: 88.39% // No change to project coverage 👍

Coverage data is based on head (eaa0dfb) compared to base (6b09a66).
Patch has no changes to coverable lines.

Additional details and impacted files
@@           Coverage Diff           @@
##           master    #1342   +/-   ##
=======================================
  Coverage   88.39%   88.39%           
=======================================
  Files          11       11           
  Lines        1086     1086           
=======================================
  Hits          960      960           
  Misses        126      126           

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

☔ View full report at Codecov.
📢 Do you have feedback about the report comment? Let us know in this issue.

@sappelhoff sappelhoff merged commit 224fdcb into bids-standard:master Nov 3, 2022
@sappelhoff sappelhoff deleted the trig branch November 3, 2022 18:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Unclear channel type "TRIG" --> analog versus digital
3 participants