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: Don't enforce BIDS & Raw channel name equivalence in read_raw_bids() #698

Merged
merged 3 commits into from
Feb 9, 2021

Conversation

hoechenberger
Copy link
Member

@hoechenberger hoechenberger commented Feb 9, 2021

Fixes #697

Please note that the same issue still exists for iEEG data in dig._handle_electrodes_reading(), but I don't fully understand the code and therefore currently don't dare to touch it. @adam2392 might want to give this one a shot 😇

cc @MaelysSolal

Merge checklist

Maintainer, please confirm the following before merging:

  • All comments resolved
  • This is not your own PR
  • All CIs are happy
  • PR title starts with [MRG]
  • whats_new.rst is updated
  • PR description includes phrase "closes <#issue-number>"

Fixes mne-tools#697

Please note that the same issue still exists for iEEG data in `dig._handle_electrodes_reading()`,
but I don't fully understand the code and therefore
currently don't dare to touch it.
Copy link
Member

@agramfort agramfort left a comment

Choose a reason for hiding this comment

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

to me it's the right thing to do !

doc/whats_new.rst Outdated Show resolved Hide resolved
Co-authored-by: Alexandre Gramfort <alexandre.gramfort@m4x.org>
@sappelhoff
Copy link
Member

to me it's the right thing to do !

agreed, and eventually the validator should check that channel names in raw and BIDS are the same.

@agramfort
Copy link
Member

agramfort commented Feb 9, 2021 via email

@hoechenberger
Copy link
Member Author

to me it's the right thing to do !

agreed, and eventually the validator should check that channel names in raw and BIDS are the same.

Yes I'm confused here, @sappelhoff said he agrees with you, but then suggests something that would enforce the opposite :) So just to clear up the confusion: Do you think this PR is doing the right thing, @sappelhoff?

@sappelhoff
Copy link
Member

Yes it's the right thing to take the sidecar files as the truth.

The validator checking that raw and sidecar info is aligned would be more of a help to dataset curators to get their story straight (less room for error). --> but that's future talk ... and as Alex says, it may even never happen because we have nobody developing dataset readers in JS.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
3 participants