plotting

In reference to a previous topic on changing tile providers from the community support discourse, I noticed that the attribution in the bottom right hand corner is not removed when changing the TileRender which leads to the attributions stacking on top of each other.

Screensho

Bug summary

The new matplotlib.colors.make_norm_from_scale helper dynamically generates a norm class from a scale class. Currently, in the codebase, it is only used as a decorator to create "toplevel" classes (e.g., it is used to generate LogNorm from LogScale, etc.), but it can also be used within other functions to dynamically generate a norm class based on a user-given arbitrary scale (

it's becoming more time-consuming and error-prone to manually re-test all the demos following internal refactorings and API adjustments.

now that the API is fleshed out a bit, it's possible to test a large amount of code (non-granularly) without having to simulate all interactions via Puppeteer or similar.

a lot of code can already be regression-tested by simply running all the demos and val

https://readthedocs.org/projects/chartify/builds/

What's wrong?

It is currently a pain to use an OxyPlot.WinfowsForms.PlotView with a transparent background: it throws if you set its BackColor to transparent. To avoid this, it is necessary to set the ControlStyles.SupportsTransparentBackColor style to true on the PlotView; however, Control.SetStyle is protected, so consumers must resort to reflection or extending PlotView to do so. This could be

I think it could be useful, when one wants to plot only e.g. class 1, to have an option to produce consistent plots for both plot_cumulative_gain and plot_roc

At the moment, instead, only plot_roc supports such option.

Thanks a lot

Michael Bostock has made some major improvements to the overlap avoidance algorithms in d3-sankey over the last week. Since the code in holoviews is a fairly straightforward Python port of that code it should be reasonably straightforward to update our code to match. Here's a link to the diff for all the updates.

I don't think this is a duplicate ticket, even though it's quite an obvious feature after that cat demo at SciPy2018.

The code that selects and renders the different geos is here in the THREE.js code
https://github.com/maartenbreddels/ipyvolume/blob/master/js/src/scatter.js#L57

I don't know quite where/how to inject the mesh definition compatible with the data file of this form, but i

What is the feature ?

I'm trying out this library for the first time and there's some places where it would be delightful to have shorthand functions:

1. Shorthand functions for Pos: Pos::top_right, Pos::bottom_right, Pos::bottom_center etc..
2. Short way to set colors for components. Currently, lots of boilerplate is required for e.g. white-on-black plotos
   • a cool start would b

Details

(This is related to JuliaPlots/Plots.jl#1706)

For example scatter(skipmissing([1.0, 2.0, missing, 1.0])) fails with Cannot convert Base.SkipMissing{Vector{Union{Missing, Float64}}} to series data for plotting.

Generally skipmissing is not required but it seems odd to see this fail.

Also I stumbled on this while trying to make a histogram, e.g.

The following code gives a segfault with Makie 0.15 and Julia 1.6.1 (also reproduced with 1.7-beta2):

using Makie

xs = range(150, 160, length=100)
ys = range(7, 9, length=100)
points = [(x, y, 0.0) for x in xs for y in ys]
x, y, z = map(i -> getindex.(points, i), 1:3)

flags = (153 .< x .< 153.5) .& (7 .< y .< 7.3)
surface(y[flags], x[flags], z[flags]);

Starting Julia

According to numpydocs there's a proper order for the sections. The big one we violate is that it should be "See Also", then "Notes". That ends up looking like:

It would be better to be consistent, a