Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP

Loading…

colormaps docstring update #889

Merged
merged 7 commits into from

6 participants

@endolith

This is an attempt at updating the colormaps docstring to include all the new colormaps and more information about where they came from and what they're supposed to do, some of which was in comments in _cm.py, but not otherwise visible to users. (https://gist.github.com/2719900)

Warning: I don't know if I did the rst formatting correctly, if the descriptions of colormaps are totally correct, if we should also mention that the "base" colormaps are copied from Matlab, or how to properly do forks and pull requests in GitHub. :)

endolith and others added some commits
@endolith endolith typo 7ee65ef
@endolith endolith some typos and small changes
("overwrite" = original file no longer exists. "override" = file still exists, but we're ignoring what it says)
ceff6f3
@efiring efiring Merge pull request #884 from endolith/patch-3
some typo fixes and small changes to the matplotlibrc stuff
fbbf5bb
@endolith endolith update colormaps docstring with more maps, their origins and purposes…
… as best I can tell
73fb325
lib/matplotlib/pyplot.py
((6 lines not shown))
- * autumn
- * bone
- * cool
- * copper
- * flag
- * gray
- * hot
- * hsv
- * jet
- * pink
- * prism
- * spring
- * summer
- * winter
- * spectral
+ matplotlib provides a number of colormaps, a complete list of which can be found in `cm._cmapnames`.
@mdboom Owner
mdboom added a note

As an identifier with a _ prefix is supposed to be private, by Python convention, we probably shouldn't recommend using it in the docs. I think we should add a public alias for this and then recommend using the that in the docs.

@mdboom Owner
mdboom added a note

Looking at this again, I don't see why this very function colormap couldn't be used to return a list of colormap names. This function currently only exists for documentation.

Making colormaps() return a list of colormaps seems pretty logical to me.

@pelson Collaborator
pelson added a note

I would probably get all the colormaps with:

import matplotlib.cm as cm
print cm.cmap_d.keys()

But having a pyplot function which returns a list of cmap names sounds sensible.

@pelson Collaborator
pelson added a note

Additionally, it would be nice to use full sphinx cross linking here (even if the thing you are linking to is not documented). e.g.

... which can be found in :class:`~matplotlib.cm.cmap_d`.

Well, cm.cmap_d.keys() and cm.datad.keys() both include all the reversed names like gray_r, which is probably not desirable for printing? _cmapnames is created from datad before it gets the reversed names added to it, so I used that. Didn't realize it shouldn't be exposed to the user like that, though.

On the other hand, if you use register_cmap(), the new colormap shows up in cmap_d.keys(), but not in datad.keys() or _cmapnames, so cmap_d.keys() seems like the right answer. I guess showing the _r colormaps too is legitimate, since ones you create with register_cmap don't have any _r version.

@pelson Collaborator
pelson added a note

Sounds like you are turning over some stones and finding some interesting "features". It might be worth putting some comments/attribute docstrings in matplotlib.cm at the datad, _cmapnames and cmap_d variables. Additionally, some of these inconsistencies might be improved by making the default colormaps go through the register_cmap function rather than have them modify the data structures directly (but that is a bigger change, and I can't guarantee that it is entirely sensible).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
lib/matplotlib/pyplot.py
((26 lines not shown))
imshow(X, cmap=cm.hot)
- or post-hoc using the corresponding pylab interface function::
+ Additionally, for the "base" colormaps below, you can set the colormap post-hoc using the corresponding pylab interface function::
imshow(X)
hot()
@mdboom Owner
mdboom added a note

I'm not a fan of the inconsistency of some colormaps being available this way and others not. On the other hand, I don't know if we want to pollute the pyplot namespace further by adding more colormaps there. It might be nice to have something like:

colormap('hot')

work. What do others think?

@WeatherGod Collaborator

And that function could be used to set an rcparam for default colormap...

I had the same thoughts. The post-hoc functions are copied from Matlab (except spectral()), but Matplotlib has a lot more built-in colormaps now, so it wouldn't make sense to give them all functions.

Maybe something shorter like cmap('hot'), since it's primarily used interactively?

@f0k
f0k added a note

There is pyplot.set_cmap('hot') for exactly that purpose. Given that nobody thought of this, it should definitely be mentioned in the colormaps docstring as well :) (Note: Its implementation is currently broken, but Issue #896 will fix this.)
/edit: Both the shortcut functions (hot(), jet() etc.) and set_cmap(...) do not only work post-hoc, but also "pre-hoc", as an alternative to the cmap keyword parameter.
/edit2: I always preferred those because cmap is documented to only accept colors.Colormap instances, which I thought needed an extra import (I did not notice pylab.cm already gives access to those, maybe it wasn't mentioned in the matplotlib 0.99 docstrings). However, as I just found out, cmap also accepts strings, so imshow, imsave and any other function documenting the cmap keyword argument need a docstring update as well! Would be great if you could include this in your pull request while you're at it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
@mdboom
Owner

This looks great. The rst formatting seems to be fine. Hop on the mailing list if you're having trouble building the docs -- I or others can help.

It would be awesome to also include the show_colormaps example inline here in the docstring. A picture is worth a thousand words for this stuff after all.

@WeatherGod
Collaborator

This is excellent work. Thank you for putting the time in for doing this!

lib/matplotlib/pyplot.py
((47 lines not shown))
+
+ ============ =======================================================
+ Colormap Description
+ ============ =======================================================
+ gist_earth mapmaker's colors from dark blue deep ocean to green
+ lowlands to brown highlands to white mountains
+ gist_gray (identical to *gray*)
+ gist_heat sequential red-orange-yellow-white, to emulate blackbody
+ radiation from an iron bar as it grows hotter
+ gist_ncar pseudo-spectral colormap from National Center for Atmospheric Research [#]_
+ gist_rainbow runs through the colors in spectral order at nearly constant intensity
+ gist_stern "Stern special" color table from Interactive Data Language software
+ gist_yarg (identical to *gray_r*)
+ ============ =======================================================
+
+ The following 34 colormaps are based on the `ColorBrewer <http://colorbrewer.org>`_ color specifications and designs developed by Cynthia Brewer:
@pelson Collaborator
pelson added a note

Ideally we would like to get line widths <= 80 characters for smaller screens, would you mind putting newlines through this and other long lines.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
@pelson
Collaborator

@endolith great stuff! The more people contributing to the documentation the better we can get it.

@ mpl devs: As far as I can see it, this would be suitable to go into 1.1.x. Maybe we should spark off another issue which implements the syntax discussed for setting a default palette instead of the plt.jet() / plt.hot() style syntax?

@mdboom
Owner

See #896. Directly relevant to the discussion here.

lib/matplotlib/pyplot.py
((64 lines not shown))
+ ========= =======================================================
+ Colormap Description
+ ========= =======================================================
+ autumn sequential increasing shades of red-orange-yellow
+ bone sequential black-white color map with a tinge of blue,
+ to emulate X-ray film
+ cool sequential decreasing shades of cyan-magenta
+ copper sequential increasing shades of black-copper
+ flag repeating red-white-blue-black pattern
+ gray simple sequential linearly-increasing black-to-white
+ grayscale
+ hot sequential black-red-yellow-white, to emulate blackbody
+ radiation from an object at increasing temperatures
+ hsv red-yellow-green-cyan-blue-pink-magenta, formed by
+ changing the hue component in the HSV color space;
+ meant to be used in plotting periodic data (that is,
@efiring Owner
efiring added a note

You might replace the parenthetical explanation by saying, "...meant to be used for cyclic variables such wind direction or time of day",

ok, that makes sense.

"meant for plotting cyclic values that wrap around at the endpoints, such as wind direction or time of day"?

that could actually be a 4th category, couldn't it? I got the 3 categories from colorbrewer documentation, but they don't have any cyclic ones. any idea what the flag and prism maps are meant for?

@efiring Owner
efiring added a note

Flag and prism might be used as alternatives for ordinary line contours, primarily giving a sense of shapes and gradients; but I suspect they are rarely used at all. Matlab has them, so we do too, for better or worse.

Ok, I added a description of cyclic as a separate scheme

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
lib/matplotlib/pyplot.py
((77 lines not shown))
+ hsv red-yellow-green-cyan-blue-pink-magenta, formed by
+ changing the hue component in the HSV color space;
+ meant to be used in plotting periodic data (that is,
+ in which the maximum magnitude and the minimum
+ magnitude are equivalent)
+ jet blue-cyan-yellow-red, a variant of hsv; based on a
+ fluid-jet simulation by NCSA [#]_
+ pink sequential increasing pastel black-pink-white, meant
+ for sepia tone colorization of photographs
+ prism repeating red-yellow-green-blue-purple-...-green pattern
+ spring shades of magenta-yellow
+ summer shades of green-yellow
+ winter shades of blue-green
+ spectral black-purple-blue-green-yellow-red-white spectrum
+ ========= =======================================================
+
@efiring Owner
efiring added a note

It seems it would be more fair to acknowledge here that all but the last are designed to match their Matlab counterparts, or something to that effect (if that is the case).

Yeah they're all copied from matlab except spectral, but I wasn't sure if that should be mentioned or not. any ideas for wording? they are also used in other things like h5utils, but, again, copied from matlab. http://ab-initio.mit.edu/wiki/index.php/Color_tables_in_h5topng

@efiring Owner
efiring added a note

"With the exception of spectral, the above colormaps are based on those of the same name provided by Matlab."

I don't know how they were derived or extracted; alternative wording suggestions are welcome.

Added

"The base colormaps are (with the exception of spectral) derived from those of the same name provided with Matlab:"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
@efiring efiring commented on the diff
lib/matplotlib/pyplot.py
((146 lines not shown))
+ * YlGn
+ * YlGnBu
+ * YlOrBr
+ * YlOrRd
+
+ Qualitative:
+
+ * Accent
+ * Dark2
+ * Paired
+ * Pastel1
+ * Pastel2
+ * Set1
+ * Set2
+ * Set3
+
@efiring Owner
efiring added a note

You might want to note here or elsewhere (footnote?) that the qualitative schemes here are illustrative, and that ordinarily they should be generated as discrete maps for the particular number of colors needed, not at quasi-continuous maps. You could even include a reference to the colors.ListedColormap class.

This is issue #881, for others' reference. Maybe we should "soft deprecate" them by saying they don't really belong here and shouldn't be used? Like gist_gray is identical to gray and should never have existed, so I just list it as "identical to gray". should I go a step further and say "deprecated, use gray instead"?

@efiring Owner
efiring added a note

I like those suggestions. Maintaining truly bad and/or duplicate colormaps forever is just bad housekeeping, so putting them on a deprecation path makes sense, even if ends up being years before they actually disappear.

Ok, I moved the redundant grayscales into their own section and discouraged them, and added a note to the qualitative section.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
@endolith endolith mention matlab origin, add cyclic description, describe ColorBrewer s…
…chemes, discourage use of qualitative and redundant schemes, change some details based on luminance plots
cce4441
@efiring efiring merged commit 72c7887 into matplotlib:master
@endolith endolith deleted the endolith:patch-4 branch
@endolith endolith referenced this pull request from a commit in endolith/matplotlib
@endolith endolith Remove redundant colormaps from examples
`gist_yarg`, `gist_gray`, and `binary` are identical to `gray`, so they are "on a deprecation path", and `spectral` was renamed to `nipy_spectral` to avoid conflicts with `Spectral`

matplotlib#889
4279e56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Commits on May 21, 2012
  1. @endolith

    typo

    endolith authored
  2. @endolith

    some typos and small changes

    endolith authored
    ("overwrite" = original file no longer exists. "override" = file still exists, but we're ignoring what it says)
Commits on May 22, 2012
  1. @efiring

    Merge pull request #884 from endolith/patch-3

    efiring authored
    some typo fixes and small changes to the matplotlibrc stuff
Commits on May 23, 2012
  1. @endolith
  2. @endolith
Commits on May 24, 2012
  1. @endolith
Commits on May 31, 2012
  1. @endolith

    mention matlab origin, add cyclic description, describe ColorBrewer s…

    endolith authored
    …chemes, discourage use of qualitative and redundant schemes, change some details based on luminance plots
This page is out of date. Refresh to see the latest.
View
2  doc/users/customizing.rst
@@ -24,7 +24,7 @@ locations, in the following order:
is something like :file:`/usr/lib/python2.5/site-packages` on Linux, and
maybe :file:`C:\\Python25\\Lib\\site-packages` on Windows. Every time you
install matplotlib, this file will be overwritten, so if you want your
- customizations to be saved, please move this file to you :file:`.matplotlib`
+ customizations to be saved, please move this file to your :file:`.matplotlib`
directory.
To display where the currently active :file:`matplotlibrc` file was
View
239 lib/matplotlib/pyplot.py
@@ -1645,39 +1645,232 @@ def colors():
def colormaps():
"""
- matplotlib provides the following colormaps.
-
- * autumn
- * bone
- * cool
- * copper
- * flag
- * gray
- * hot
- * hsv
- * jet
- * pink
- * prism
- * spring
- * summer
- * winter
- * spectral
+ Matplotlib provides a number of colormaps, and others can be added using
+ :func:`register_cmap`. This function documents the built-in colormaps,
+ and will also return a list of all registered colormaps if called.
You can set the colormap for an image, pcolor, scatter, etc,
- either as a keyword argument::
+ using a keyword argument::
imshow(X, cmap=cm.hot)
- or post-hoc using the corresponding pylab interface function::
+ or using the :func:`set_cmap` function::
+
+ imshow(X)
+ pyplot.set_cmap('hot')
+ pyplot.set_cmap('jet')
+
+ In interactive mode, :func:`set_cmap` will update the colormap post-hoc,
+ allowing you to see which one works best for your data.
+
+ All built-in colormaps can be reversed by appending ``_r``: For instance,
+ ``gray_r`` is the reverse of ``gray``.
+
+ There are several common color schemes used in visualization:
+
+ Sequential schemes
+ for unipolar data that progresses from low to high
+ Diverging schemes
+ for bipolar data that emphasizes positive or negative deviations from a
+ central value
+ Cyclic schemes
+ meant for plotting values that wrap around at the
+ endpoints, such as phase angle, wind direction, or time of day
+ Qualitative schemes
+ for nominal data that has no inherent ordering, where color is used
+ only to distinguish categories
+
+ The base colormaps are (with the exception of `spectral`) derived from
+ those of the same name provided with Matlab:
+
+ ========= =======================================================
+ Colormap Description
+ ========= =======================================================
+ autumn sequential linearly-increasing shades of red-orange-yellow
+ bone sequential increasing black-white color map with
+ a tinge of blue, to emulate X-ray film
+ cool linearly-decreasing shades of cyan-magenta
+ copper sequential increasing shades of black-copper
+ flag repetitive red-white-blue-black pattern (not cyclic at
+ endpoints)
+ gray sequential linearly-increasing black-to-white
+ grayscale
+ hot sequential black-red-yellow-white, to emulate blackbody
+ radiation from an object at increasing temperatures
+ hsv cyclic red-yellow-green-cyan-blue-magenta-red, formed
+ by changing the hue component in the HSV color space
+ jet a spectral map with dark endpoints, blue-cyan-yellow-red;
+ based on a fluid-jet simulation by NCSA [#]_
+ pink sequential increasing pastel black-pink-white, meant
+ for sepia tone colorization of photographs
+ prism repetitive red-yellow-green-blue-purple-...-green pattern
+ (not cyclic at endpoints)
+ spring linearly-increasing shades of magenta-yellow
+ summer sequential linearly-increasing shades of green-yellow
+ winter linearly-increasing shades of blue-green
+ spectral black-purple-blue-green-yellow-red-white spectrum
+ ========= =======================================================
+
+ For the above list only, you can also set the colormap using the
+ corresponding pylab shortcut interface function, similar to Matlab::
imshow(X)
hot()
jet()
- In interactive mode, this will update the colormap allowing you to
- see which one works best for your data.
- """
- pass
+ The next set of palettes are from the `Yorick scientific visualisation
+ package <http://yorick.sourceforge.net/index.php>`_, an evolution of
+ the GIST package, both by David H. Munro:
+
+ ============ =======================================================
+ Colormap Description
+ ============ =======================================================
+ gist_earth mapmaker's colors from dark blue deep ocean to green
+ lowlands to brown highlands to white mountains
+ gist_heat sequential increasing black-red-orange-white, to emulate
+ blackbody radiation from an iron bar as it grows hotter
+ gist_ncar pseudo-spectral black-blue-green-yellow-red-purple-white
+ colormap from National Center for Atmospheric
+ Research [#]_
+ gist_rainbow runs through the colors in spectral order from red to
+ violet at full saturation (like *hsv* but not cyclic)
+ gist_stern "Stern special" color table from Interactive Data
+ Language software
+ ============ =======================================================
+
+ The following colormaps are based on the `ColorBrewer
+ <http://colorbrewer.org>`_ color specifications and designs developed by
+ Cynthia Brewer:
+
+ ColorBrewer Diverging (luminance is highest at the midpoint, and
+ decreases towards differently-colored endpoints):
+
+ ======== ===================================
+ Colormap Description
+ ======== ===================================
+ BrBG brown, white, blue-green
+ PiYG pink, white, yellow-green
+ PRGn purple, white, green
+ PuOr orange, white, purple
+ RdBu red, white, blue
+ RdGy red, white, gray
+ RdYlBu red, yellow, blue
+ RdYlGn red, yellow, green
+ Spectral red, orange, yellow, green, blue
+ ======== ===================================
+
+ ColorBrewer Sequential (luminance decreases monotonically):
+
+ ======== ====================================
+ Colormap Description
+ ======== ====================================
+ Blues white to dark blue
+ BuGn white, light blue, dark green
+ BuPu white, light blue, dark purple
+ GnBu white, light green, dark blue
+ Greens white to dark green
+ Greys white to black (not linear)
+ Oranges white, orange, dark brown
+ OrRd white, orange, dark red
+ PuBu white, light purple, dark blue
+ PuBuGn white, light purple, dark green
+ PuRd white, light purple, dark red
+ Purples white to dark purple
+ RdPu white, pink, dark purple
+ Reds white to dark red
+ YlGn light yellow, dark green
+ YlGnBu light yellow, light green, dark blue
+ YlOrBr light yellow, orange, dark brown
+ YlOrRd light yellow, orange, dark red
+ ======== ====================================
+
+ ColorBrewer Qualitative:
+
+ (For plotting nominal data, :class:`ListedColormap` should be used,
+ not :class:`LinearSegmentedColormap`. Different sets of colors are
+ recommended for different numbers of categories. These continuous
+ versions of the qualitative schemes may be removed or converted in the
+ future.)
+
+ * Accent
+ * Dark2
+ * Paired
+ * Pastel1
+ * Pastel2
+ * Set1
+ * Set2
+ * Set3
+
@efiring Owner
efiring added a note

You might want to note here or elsewhere (footnote?) that the qualitative schemes here are illustrative, and that ordinarily they should be generated as discrete maps for the particular number of colors needed, not at quasi-continuous maps. You could even include a reference to the colors.ListedColormap class.

This is issue #881, for others' reference. Maybe we should "soft deprecate" them by saying they don't really belong here and shouldn't be used? Like gist_gray is identical to gray and should never have existed, so I just list it as "identical to gray". should I go a step further and say "deprecated, use gray instead"?

@efiring Owner
efiring added a note

I like those suggestions. Maintaining truly bad and/or duplicate colormaps forever is just bad housekeeping, so putting them on a deprecation path makes sense, even if ends up being years before they actually disappear.

Ok, I moved the redundant grayscales into their own section and discouraged them, and added a note to the qualitative section.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
+ Other miscellaneous schemes:
+
+ ========= =======================================================
+ Colormap Description
+ ========= =======================================================
+ afmhot sequential black-orange-yellow-white blackbody
+ spectrum, commonly used in atomic force microscopy
+ brg blue-red-green
+ bwr diverging blue-white-red
+ coolwarm diverging blue-gray-red, meant to avoid issues with 3D
+ shading, color blindness, and ordering of colors [#]_
+ CMRmap "Default colormaps on color images often reproduce to
+ confusing grayscale images. The proposed colormap
+ maintains an aesthetically pleasing color image that
+ automatically reproduces to a monotonic grayscale with
+ discrete, quantifiable saturation levels." [#]_
+ cubehelix Unlike most other color schemes cubehelix was designed
+ by D.A. Green to be monotonically increasing in terms
+ of perceived brightness. Also, when printed on a black
+ and white postscript printer, the scheme results in a
+ greyscale with monotonically increasing brightness.
+ This color scheme is named cubehelix because the r,g,b
+ values produced can be visualised as a squashed helix
+ around the diagonal in the r,g,b color cube.
+ gnuplot gnuplot's traditional pm3d scheme
+ (black-blue-red-yellow)
+ gnuplot2 sequential color printable as gray
+ (black-blue-violet-yellow-white)
+ ocean green-blue-white
+ rainbow spectral purple-blue-green-yellow-orange-red colormap
+ with diverging luminance
+ seismic diverging blue-white-red
+ terrain mapmaker's colors, blue-green-yellow-brown-white,
+ originally from IGOR Pro
+ ========= =======================================================
+
+ The following colormaps are redundant and may be removed in future
+ versions. It's recommended to use *gray* or *gray_r* instead, which
+ produce identical output:
+
+ ========= =======================================================
+ Colormap Description
+ ========= =======================================================
+ gist_gray identical to *gray*
+ gist_yarg identical to *gray_r*
+ binary identical to *gray_r*
+ ========= =======================================================
+
+ .. rubric:: Footnotes
+
+ .. [#] Rainbow colormaps, ``jet`` in particular, are considered a poor
+ choice for scientific visualization by many researchers: `Rainbow Color
+ Map (Still) Considered Harmful
+ <http://www.jwave.vt.edu/%7Erkriz/Projects/create_color_table/color_07.pdf>`_
+
+ .. [#] Resembles "BkBlAqGrYeOrReViWh200" from NCAR Command
+ Language. See `Color Table Gallery
+ <http://www.ncl.ucar.edu/Document/Graphics/color_table_gallery.shtml>`_
+
+ .. [#] See `Diverging Color Maps for Scientific Visualization
+ <http://www.cs.unm.edu/~kmorel/documents/ColorMaps/>`_ by Kenneth
+ Moreland.
+
+ .. [#] See `A Color Map for Effective Black-and-White Rendering of
+ Color-Scale Images
+ <http://www.mathworks.com/matlabcentral/fileexchange/2662-cmrmap-m>`_
+ by Carey Rappaport
+
+ """
+ return sorted(cm.cmap_d.keys())
## Plotting part 1: manually generated functions and wrappers ##
View
14 matplotlibrc.template
@@ -3,9 +3,9 @@
# This is a sample matplotlib configuration file - you can find a copy
# of it on your system in
# site-packages/matplotlib/mpl-data/matplotlibrc. If you edit it
-# there, please note that it will be overridden in your next install.
+# there, please note that it will be overwritten in your next install.
# If you want to keep a permanent local copy that will not be
-# over-written, place it in HOME/.matplotlib/matplotlibrc (unix/linux
+# overwritten, place it in HOME/.matplotlib/matplotlibrc (unix/linux
# like systems) and C:\Documents and Settings\yourname\.matplotlib
# (win32 systems).
#
@@ -40,7 +40,7 @@ backend : %(backend)s
# "pyqt" and "pyside". The "pyqt" setting has the side effect of
# forcing the use of Version 2 API for QString and QVariant.
-# if you are runing pyplot inside a GUI and your backend choice
+# if you are running pyplot inside a GUI and your backend choice
# conflicts, we will automatically try to find a compatible one for
# you if backend_fallback is True
#backend_fallback: True
@@ -220,8 +220,8 @@ backend : %(backend)s
# For example, use ',' as a decimal
# separator in the fr_FR locale.
#axes.unicode_minus : True # use unicode for the minus symbol
- # rather than hypen. See
- # http://en.wikipedia.org/wiki/Plus_sign
+ # rather than hyphen. See
+ # http://en.wikipedia.org/wiki/Plus_and_minus_signs#Character_codes
#axes.color_cycle : b, g, r, c, m, y, k # color cycle for plot lines
# as list of string colorspecs:
# single letter, long name, or
@@ -265,7 +265,7 @@ backend : %(backend)s
#legend.numpoints : 2 # the number of points in the legend line
#legend.fontsize : large
#legend.pad : 0.0 # deprecated; the fractional whitespace inside the legend border
-#legend.borderpad : 0.5 # border whitspace in fontsize units
+#legend.borderpad : 0.5 # border whitespace in fontsize units
#legend.markerscale : 1.0 # the relative size of legend markers vs. original
# the following dimensions are in axes coords
#legend.labelsep : 0.010 # deprecated; the vertical space between the legend entries
@@ -288,7 +288,7 @@ backend : %(backend)s
#figure.facecolor : 0.75 # figure facecolor; 0.75 is scalar gray
#figure.edgecolor : white # figure edgecolor
-# The figure subplot parameters. All dimensions are fraction of the
+# The figure subplot parameters. All dimensions are a fraction of the
# figure width or height
#figure.subplot.left : 0.125 # the left side of the subplots of the figure
#figure.subplot.right : 0.9 # the right side of the subplots of the figure
Something went wrong with that request. Please try again.