-
Notifications
You must be signed in to change notification settings - Fork 87
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
_read_events errors on BAD_ACQ_SKIP #1257
Comments
Hello! 👋 Thanks for opening your first issue here! ❤️ We will try to get back to you soon. 🚴🏽♂️ |
@drammock From the documentation of the
The problem we're facing is that BIDS demands we assign an event code, and currently we're not picking any automatically for Annotations |
Would it make sense to add those entries automatically for "special" annotation values like this? |
I believe we once considered this but didn't want to choose an arbitrary event code But now I feeel -- why not? |
Given that we are an "MNE-Python library", I would be fine to add some special treatment for "classic" MNE-Python annotations that have a defined meaning, like |
Description of the problem
I have a MEG FIF dataset that mostly doesn't have annotations (only the occasional
BAD_ACQ_SKIP
), and does have stim-channel events (which I parse beforehand and pass in as an events array). I would expect theBAD_ACQ_SKIP
annotation to be silently preserved in the Raw file, but in factwrite_raw_bids
fails because there is no entry forBAD_ACQ_SKIP
in the event ID dictionary.Am I just missing something obvious here? I've not actually used mne-bids very much so it's quite possible I'm just doing it wrong.
Steps to reproduce
Expected results
file is written
Actual results
Additional information
The text was updated successfully, but these errors were encountered: