<spanid="color-changes"></span><h1>Default color changes<aclass="headerlink" href="#default-color-changes" title="Permalink to this headline">#</a></h1>
<p>As discussed at length elsewhere [insert links], <codeclass="docutils literal notranslate"><spanclass="pre">jet</span></code> is an
empirically bad colormap and should not be the default colormap.
Due to the position that changing the appearance of the plot breaks
backward compatibility, this change has been put off for far longer
than it should have been. In addition to changing the default color
map we plan to take the chance to change the default color-cycle on
plots and to adopt a different colormap for filled plots (<codeclass="docutils literal notranslate"><spanclass="pre">imshow</span></code>,
<codeclass="docutils literal notranslate"><spanclass="pre">pcolor</span></code>, <codeclass="docutils literal notranslate"><spanclass="pre">contourf</span></code>, etc) and for scatter like plots.</p>
<sectionid="default-heat-map-colormap">
<h2>Default heat map colormap<aclass="headerlink" href="#default-heat-map-colormap" title="Permalink to this headline">#</a></h2>
<p>The choice of a new colormap is fertile ground to bike-shedding ("No,
it should be _this_ color") so we have a proposed set criteria (via
Nathaniel Smith) to evaluate proposed colormaps.</p>
<ulclass="simple">
<li><p>it should be a sequential colormap, because diverging colormaps are
really misleading unless you know where the "center" of the data is,
and for a default colormap we generally won't.</p></li>
<li><p>it should be perceptually uniform, i.e., human subjective judgments
of how far apart nearby colors are should correspond as linearly as
possible to the difference between the numerical values they
represent, at least locally.</p></li>
<li><p>it should have a perceptually uniform luminance ramp, i.e. if you
convert to greyscale it should still be uniform. This is useful both
in practical terms (greyscale printers are still a thing!) and
because luminance is a very strong and natural cue to magnitude.</p></li>
<li><p>it should also have some kind of variation in hue, because hue
variation is a really helpful additional cue to perception, having
two cues is better than one, and there's no reason not to do it.</p></li>
<li><p>the hue variation should be chosen to produce reasonable results
even for viewers with the more common types of
colorblindness. (Which rules out things like red-to-green.)</p></li>
<li><p>For bonus points, it would be nice to choose a hue ramp that still
works if you throw away the luminance variation, because then we
could use the version with varying luminance for 2d plots, and the
version with just hue variation for 3d plots. (In 3d plots you
really want to reserve the luminance channel for lighting/shading,
because your brain is <em>really</em> good at extracting 3d shape from
luminance variation. If the 3d surface itself has massively varying
luminance then this screws up the ability to see shape.)</p></li>
<li><p>Not infringe any existing IP</p></li>
</ul>
<sectionid="example-script">
<h3>Example script<aclass="headerlink" href="#example-script" title="Permalink to this headline">#</a></h3>
</section>
<sectionid="proposed-colormaps">
<h3>Proposed colormaps<aclass="headerlink" href="#proposed-colormaps" title="Permalink to this headline">#</a></h3>
</section>
</section>
<sectionid="default-scatter-colormap">
<h2>Default scatter colormap<aclass="headerlink" href="#default-scatter-colormap" title="Permalink to this headline">#</a></h2>
<p>For heat-map like applications it can be desirable to cover as much of
the luminance scale as possible, however when colormapping markers,
having markers too close to white can be a problem. For that reason
we propose using a different (but maybe related) colormap to the
heat map for marker-based. The design parameters are the same as
above, only with a more limited luminance variation.</p>
<sectionid="id1">
<h3>Example script<aclass="headerlink" href="#id1" title="Permalink to this headline">#</a></h3>
<spanclass="n">area</span><spanclass="o">=</span><spanclass="n">np</span><spanclass="o">.</span><spanclass="n">pi</span><spanclass="o">*</span><spanclass="p">(</span><spanclass="mi">15</span><spanclass="o">*</span><spanclass="n">np</span><spanclass="o">.</span><spanclass="n">random</span><spanclass="o">.</span><spanclass="n">rand</span><spanclass="p">(</span><spanclass="n">N</span><spanclass="p">))</span><spanclass="o">**</span><spanclass="mi">2</span><spanclass="c1"># 0 to 15 point radiuses</span>
<h3>Proposed color cycle<aclass="headerlink" href="#proposed-color-cycle" title="Permalink to this headline">#</a></h3>
</section>
</section>
</section>
</div>
</main>
</div>
</div>
<!-- Scripts loaded after <body> so the DOM is not blocked -->
<divid="unreleased-message"> You are reading an old version of the documentation (v3.5.3). For the latest version see <ahref="https://matplotlib.org/stable/devel/color_changes.html">https://matplotlib.org/stable/devel/color_changes.html</a></div>