Yes exactly along the lines of 1), 2) 3) +1 for this. My idea was that 2)
also could accept functions as values then, which might be covered though
by 3)


On Thu, Jan 10, 2013 at 11:17 PM, Eric89GXL <notifications@github.com>wrote:

> In mne/viz.py:
>
> > @@ -114,9 +115,22 @@ def _plot_topo(info, times, show_func, layout, decim, vmin, vmax, colorbar,
> >                  # hack to inlcude channel idx and name, to use in callback
> >                  ax.__dict__['_mne_ch_name'] = name
> >                  ax.__dict__['_mne_ch_idx'] = ch_idx
> > -                show_func(ax, ch_idx, tmin, tmax, vmin, vmax)
> > +                if layout.kind == 'Vectorview-all':
> > +                    if info['chs'][ch_idx]['unit']==112:
> > +                        show_func(ax, ch_idx, tmin, tmax, vmin[0], vmax[0])
> > +                    elif info['chs'][ch_idx]['unit']==201:
> > +                        show_func(ax, ch_idx, tmin, tmax, vmin[1], vmax[1])
> > +                else:
> > +                    show_func(ax, ch_idx, tmin, tmax, vmin, vmax)
>
> Yeah, using the human-readable mne.fiff.FIFF values is better.
>
> I like the idea of having vmin, vmax arguments. Maybe 1) dict() support
> for different channel types, 2) function support, or 3) None (default)
> leading to old behavior (peak-to-peak scaling, IIRC). Not sure if the
> parameter would need to be a unified vlim or vmin and vmax separately,
> though...
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/mne-tools/mne-python/pull/361/files#r2611904>.
>
>