mne-tools / mne-tools/mne-python
ENH: Allow `mne coreg` to adjust other dataset properties for OPM data
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 3.5k
- Forks
- 1.6k
- Avg merge
- 1d 6h
- Merged PRs (30d)
- 100
Description
For OPM data, it would be convenient to allow mne coreg to adjust more than just the head_mri_t (by writing -trans.fif files, which it does currently).
Even with our existing OPM dataset from years ago, the head and MRI coordinate frames are taken as equal, which they shouldn't be. We should allow for using the current (in the GUI) sensor<->MRI relationship and use the current LPA/Nasion/RPA (from the MRI) to correct the LPA/Nasion/RPA in info['dig'], which in turn should update the head coordinate frame definition, which in turn should change the rest of info['dig'], info['chs][ii]['loc'], info['dev_head_t'], etc.
Adapted from #11405
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the mne coreg command and its existing handling of head_mri_t and -trans.fif files. Trace how the GUI exposes the current sensor-to-MRI relationship and how LPA/Nasion/RPA are represented in info['dig'], info['chs'][ii]['loc'], and info['dev_head_t']. Done means OPM dataset properties are consistently updated from the current coregistration state.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli, data
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100