FIX: support for for commas in channel names #53
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
reveals an issue
|
This seems like an MNE-Python reading error to me:
as if MNE-Python does not properly read channel names with commas. |
in that case we do not need to cover comma issues in formatting event type is always Stimulus event description is always numeric so a comma never occurs
|
this one is blocked until mne-tools/mne-python#8492 is resolved. |
|
This passes on this mne branch: mne-tools/mne-python#8492 🙂 so once that is merged, we can merge here as well |
|
merging now to continue development without merge conflicts, and because I am confident in the behavior |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
closes #51
commas in (1) event type, and (2) event description are currently irrelevant, because: