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

[ENH] Add interpretation of "n/a" onsets in events.tsv files #1966

Merged
merged 2 commits into from
Oct 28, 2024

Conversation

Remi-Gau
Copy link
Collaborator

@Remi-Gau
Copy link
Collaborator Author

@VisLab

Copy link

codecov bot commented Oct 21, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 86.87%. Comparing base (790c0fb) to head (de4db09).
Report is 5 commits behind head on master.

Additional details and impacted files
@@           Coverage Diff           @@
##           master    #1966   +/-   ##
=======================================
  Coverage   86.87%   86.87%           
=======================================
  Files          16       16           
  Lines        1410     1410           
=======================================
  Hits         1225     1225           
  Misses        185      185           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@@ -339,7 +339,7 @@ onset:
Onset (in seconds) of the event, measured from the beginning of the acquisition
of the first data point stored in the corresponding task data file.
Negative onsets are allowed, to account for events that occur prior to the first
stored data point.
stored data point. A `n/a` value indicates the onset time is unknown or unavailable.
Copy link
Collaborator

Choose a reason for hiding this comment

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

I would move this to the bottom to avoid breaking up discussion of negatives. And maybe "A value of n/a..." to get around the a/an weirdness with consonants like n (I would use "an n/a").

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

moved actually at the end of the whole section

Copy link
Member

Choose a reason for hiding this comment

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

Thanks for addressing this. I think n/a is fine. The description for onset now seems to be parallel to the description for duration.

@effigies effigies changed the title [FIX] mention that n/a value indicates the onset time is unknown or unavailable. [ENH] Add interpretation of "n/a" onsets in events.tsv files Oct 21, 2024
@effigies effigies merged commit d9fa107 into bids-standard:master Oct 28, 2024
27 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Should "n/a" be allowed in the onset column of events.tsv
4 participants