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

BUG: Fix bug with coord frame reading #13129

Merged
merged 2 commits into from
Feb 25, 2025
Merged

BUG: Fix bug with coord frame reading #13129

merged 2 commits into from
Feb 25, 2025

Conversation

larsoner
Copy link
Member

Fixes bugs in mne-bids main introduced by #13083, see for example here. Short fix would have been to just change a .get(coord_frame) to .get(coord_frame, coord_frame), but then I realized we didn't fully test consistency of coord frame constant use. So this PR also cleans that up.

Notably there are some coordinate frames that AFAIK we never use, so those have been singled out a couple of places here. But critically I added some tests to make sure three private constants that we use in many places are now internally consistent. We could in principle include these, but it will bloat all _check_option errors that people see so I don't see much value. And these tests/comments will make it easy to add them later if we ever want them.

@drammock drammock enabled auto-merge (squash) February 25, 2025 16:37
@larsoner larsoner disabled auto-merge February 25, 2025 17:42
@larsoner larsoner merged commit 11df2fa into mne-tools:main Feb 25, 2025
30 of 32 checks passed
@larsoner larsoner deleted the bug branch February 25, 2025 17:42
larsoner added a commit that referenced this pull request Feb 25, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants