Re: [matplotlib-devel] release strategy and the color revolution

[Michael W. <mw...@st...>]

On Wed, Feb 18, 2015 at 4:42 PM, Olga Botvinnik <obo...@uc...> wrote:

> FYI the notebook isn't working for me in IPython 2.2.0
>

Oops, sorry.


> I agree with Michael's sentiment that from a marketing perspective, a
> matplotlib-only colormap is advantageous to maintain a consistent brand.
>

Just to be clear, I wasn't suggesting *matplotlib only* in the (legal)
sense that parula is matlab only, just that it should be identifiably "the
matplotlib colormap".


> Will these colormaps also be used for non-imshow/colormesh/pcolormesh
> data, as in for line colors as well? I think that's a great idea! It'll
> make the black and white versions easier to understand since the changing
> colors will monotonically increase/decrease in darkness rather than
> randomly changing.
>

I wasn't really thinking the plt.plot line cycle, more about plt.scatter,
plt.contour, etc. and other places that accept a cmap argument but don't
draw an "image-like" plot. Though, having a default colormap that can be
used when you want to encode a quantitative value in the color of lines,
e.g. the figures here:
http://www.machenslab.org/publications/machens_etal_2010.pdf, would be good
too. That's somewhere you often find people using jet.