mne-tools / mne-tools/mne-python
Standard montage and built-in adjacency identifiers ("EEG cap names") don't match
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 3.5k
- Forks
- 1.6k
- Avg merge
- 1d 6h
- Merged PRs (30d)
- 100
Description
# %%
import mne
montage_name = 'easycap-M1'
m = mne.channels.make_standard_montage(montage_name)
adj, ch_names = mne.channels.read_ch_adjacency(montage_name)
The read_ch_adjacency() call raises:
ValueError: "easycap-M1" is not a valid
fname. Try one of:['easycap128ch-av', 'neuromag306', 'KIT-UMD-3', 'biosemi64', 'bti148', 'easycap32ch-av', 'KIT-UMD-1', 'easycapM11', 'KIT-208', 'KIT-UMD-4', 'ctf275', 'easycapM14', 'ctf64', 'easycapM1', 'biosemi16', 'KIT-UMD-2', 'bti248grad', 'easycapM15', 'ctf151', 'bti248', 'neuromag306planar', 'biosemi32', 'easycap64ch-av', 'KIT-NYU-2019', 'KIT-157']
We should establish consistency here where possible
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 by tracing mne.channels.make_standard_montage() and mne.channels.read_ch_adjacency() to compare their accepted montage identifiers, especially easycap-M1 and easycapM1. Determine which naming differences can be aligned, then verify that the same identifiers work consistently in both calls. The issue does not name specific files or tests, so locate the relevant implementation and test coverage first.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100