-
Notifications
You must be signed in to change notification settings - Fork 92
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
ENH: Don't enforce BIDS & Raw channel name equivalence in read_raw_bids() #698
Conversation
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.
There was a problem hiding this 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 !
Co-authored-by: Alexandre Gramfort <alexandre.gramfort@m4x.org>
agreed, and eventually the validator should check that channel names in raw and BIDS are the same. |
validator would then be required to read EEG/MEG formats. It's too much I
think. For me
we should not enforce that the names are the same. We take the raw files as
they are and
the sidecar take precedence.
… |
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? |
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. |
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: