-
Notifications
You must be signed in to change notification settings - Fork 35
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
write subject ID to ["his_id"], not ["first_name"] #546
Conversation
Thanks @aaronjnewman. My first gut feeling is that this makes sense. I just enabled the CI to run the tests. Don't worry if the tests fail, we will work with you to fix any unrelated errors and understand why anything is failing due to the change. |
I think you need to at least adjust this test:
to check |
I may have to defer to @rob-luke or others on this one - I'm not familiar with CI and not sure where this originates. I don't see any instance of |
Pushed a commit that should make sense alongside mne-tools/mne-python#12526. We should merge that then restart CIs here then things should be green 🤞 @aaronjnewman feel free to look to see if the two PRs make sense to you |
@larsoner thanks - like many things, it's clear when I see it, but generating it myself would be a whole 'nother thing :) Appreciate the quick fix! |
Thanks @aaronjnewman |
Reference issue
Fixes #544
What does this implement/fix?
write subject ID to ["subject_info"]["his_id"], not ["subject_info"]["first_name"]. This makes the code more consistent with BIDS specifications, and fixes error generated by
write_raw_snirf()
described in #544