Skip to content

ENH: sEEG and ECoG sensor sizes are too large by default, should be configurable #12472

@libertyh

Description

@libertyh

Describe the new feature or enhancement

The mne.viz.Brain functionality has improved a lot lately, and I have a request to make it even better. The current size of the sensors when you use brain.add_sensors() to an ECoG or sEEG visualization is quite a bit bigger than the actual sensors are in reality, which I think actually makes it difficult to appreciate where they are in space and makes them overlap in a way that is not aesthetically pleasing. I have two suggestions, one really easy, and one maybe more complex.

  1. I would like to suggest an overall change to the global default size for sEEG and ECoG electrodes in this visualization.
  2. I suggest another keyword argument to brain.add_sensors() that would allow for adjusting the electrode size on an individual basis instead of the whole montage. This can be a nice way of showing visually the size of different effects on each electrode (for example, make the electrode bigger if it's response is larger).

Describe your proposed implementation

  1. For 1, I propose to change the default size in defaults.py* -- for defaults['coreg']['ecog_scale'] and ['seeg_scale'] I suggest 2e-3 instead of 5e-3. Typically ECoG electrodes might be anywhere from 1-2.5 mm in diameter, and sEEG electrodes closer to 0.8-1mm. The spacing between contacts can vary between a few millimeters to a centimeter, so the scale of 5e-3 (5mm) often will make them overlap for a denser montage. I've already made this change in my own fork.

  2. For 2, I would add something to add_sensors(), but I want to make sure it wouldn't break anything else, so I'm open to alternatives.

Picture attached of what the new (smaller) size looks like:

image

Describe possible alternatives

N/A

Additional context

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions