ylim in plot_evoked_topo
See original GitHub issueThe ylim parameter in plot_evoked_topo is None by default and for this default, the channels have different ylim. I think this is a bad default because:
- It does not allow comparison across channels (e.g., lateralization effects)
- It does not allow you to easily spot bad channels
Instead, the ylim should be determined based on all the channels. One option is to copy the defaults from xplotter which are based on expected physical values of the quantities for evoked responses. The other option is to use the MAD or some such thing so that you get reasonable values even when bad channels are present.
Issue Analytics
- State:
- Created 3 years ago
- Comments:14 (14 by maintainers)
 Top Results From Across the Web
Top Results From Across the Web
mne.viz.plot_evoked_topo — MNE 1.2.2 documentation
Plot 2D topography of evoked responses. ... If None, the ylim parameter for each channel type is determined by the minimum and maximum...
Read more >y-limits of subplots in plot_evoked_topo · Issue #6039
Hi all, Is there a way to set y-axis limits in the « click-to-magnify » plots in plot_evoked_topo? The ylim input applies to...
Read more >plot_compare_evokeds from mne.EvokedArray: confidence ...
When plotting the topomaps, I could apply scalings=dict(eeg=1) and convert the Y lims of the colorbar to [-3, 3]. But I cannot figure...
Read more >mne.Evoked — MNE 0.15.dev0 documentation
plot ([picks, exclude, unit, show, ylim, ...]) Plot evoked data using ... Plot topographic maps of specific time points of evoked data.
Read more >Make figures more publication ready
Suppose we want a figure with an evoked plot on top, and the brain activation below, with the brain subplot slightly bigger than...
Read more > Top Related Medium Post
Top Related Medium Post
No results found
 Top Related StackOverflow Question
Top Related StackOverflow Question
No results found
 Troubleshoot Live Code
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free Top Related Reddit Thread
Top Related Reddit Thread
No results found
 Top Related Hackernoon Post
Top Related Hackernoon Post
No results found
 Top Related Tweet
Top Related Tweet
No results found
 Top Related Dev.to Post
Top Related Dev.to Post
No results found
 Top Related Hashnode Post
Top Related Hashnode Post
No results found

Yeah , Definitely. For now , it looks like the defined ylims seems to be preserved while within plot_evoked_topo and somehow does some weird stuff after the data gets passed on to class
_plot_topo, which is responsible for producing the actual plot.Also looking back at the original issue, the default ylims being assigned when
plot_evoked_topois called with out any parameters seems to be in the magnitude of several hundreds. Forevoked_megin the above example, it’s specifically [(-548.98971293,548.98971293) , (-199.91518048,199.91518048).ok so presently you can zoom by drawing a square but the ylim is not adjusted dynamically
that seems something valuable to add !