Maxime Liquet
Maxime Liquet
> I'd like an answer to my question above first, as it currently stands this does not address the ask outlined in the issue. Good catch, I'll see with Demetris....
> I'll make the operation a no-op is the overlay is not a subcoord-y overlay I'm actually not sure how to find whether an overlay is a subcoord-y overlay in...
> Yea, we agreed that because of the complexity involved, it would be sufficient (for now) to require group-wise normalization to be explicitly enabled, and so not applied by default....
We decided yesterday not to try to depend on https://github.com/bokeh/bokeh/pull/13826 for now, since it may take a little while until this is refined and released, and may need more upstream...
Had a look at it with @Hoxbro and saw two issues: - The `y_range` value passed by the stream is the min/max of APPL in the viewport. It should be...
Yes I think that's the minimum required. Looking through the code base for `dask` or `cudf` for example reveals some other places where different data types are handled.
> feature request is to make `subcoordinate_y` group-aware I assume this means users would set the `group` parameter on an Element with e.g. `hv.Curve(..., group='EEG', label='1').opts(subcoordinate_y=True) * hv.Curve(..., group='MEG', label='2').opts(subcoordinate_y=True)`....
We discussed today and clarified (at least for me 🙃 ) that we'd like to normalize the groups independently by default, potentially offering an option to disable that.
@Hoxbro do you think this discussion should take place on HoloViews' tracker? Although hvPlot could have a simple implementation like it does for polars as an easy entry point. @HealthyPear...