In [ ]:# Let printing work the same in Python 2 and 3 from __future__ import print_function
Matplotlib is a library for producing publication-quality figures. mpl (for short) was designed from the beginning to serve two purposes. First, allow for interactive, cross-platform control of figures and plots, and second, to make it very easy to produce static raster or vector graphics files without the need for any GUIs. Furthermore, mpl -- much like Python itself -- gives the developer complete control over the appearance of their plots, while still being very usable through a powerful defaults system.
Many users of Matplotlib are often faced with the question, "I want to make a figure that has X with Y in the same figure, but it needs to look like Z". Good luck getting an answer from a web search with that query! This is why the gallery is so useful, because it showcases the variety of ways one can make figures. Browse through the gallery, click on any figure that has pieces of what you want to see and the code that generated it. Soon enough, you will be like a chef, mixing and matching components to produce your masterpiece!
As always, if you have a new and interesting plot that demonstrates a feature of Matplotlib, feel free to submit a concise, well-commented version of the code for inclusion in the gallery.
When you are just simply stuck, and cannot figure out how to get something to work, or just need some hints on how to get started, you will find much of the community at the matplotlib-users mailing list. This mailing list is an excellent resource of information with many friendly members who just love to help out newcomers. The number one rule to remember with this list is to be persistant. While many questions do get answered fairly quickly, some do fall through the cracks, or the one person who knows the answer isn't available. Therefore, try again with your questions rephrased, or with a plot showing your attempts so far. We love plots, so an image showing what is wrong often gets the quickest responses.
Matplotlib is hosted by GitHub.
So, you think you found a bug? Or maybe you think some feature is just too difficult to use? Or missing altogether? Submit your bug reports here at Matplotlib's issue tracker. We even have a process for submitting and discussing Matplotlib Enhancement Proposals (MEPs).
In [ ]:import matplotlib print(matplotlib.__version__) print(matplotlib.get_backend())
Normally we wouldn't need to think about this too much, but IPython/Jupyter notebooks behave a touch differently than "normal" python.
Inside of IPython, it's often easiest to use the Jupyter
notebook backend. This allows plots to be displayed and interacted with in the browser in a Jupyter notebook. Otherwise, figures will pop up in a separate GUI window.
We can do this in two ways:
%matplotlib backend_name "magic" command (or
plt.ion(), which behaves similarly)
Here, we'll use the second method for one simple reason: it allows our code to behave the same way regardless of whether we run it inside of an Jupyter notebook or from a python script at the command line. Feel free to use the
%matplotlib magic command if you'd prefer.
One final note: You will always need to do this before you
import matplotlib.pyplot as plt.
In [ ]:matplotlib.use('nbagg')
Matplotlib is a large project and can seem daunting at first. However, by learning the components, it should begin to feel much smaller and more approachable.
People use "plot" to mean many different things. Here, we'll be using a consistent terminology (mirrored by the names of the underlying classes, etc):
Figure is the top-level container in this hierarchy. It is the overall window/page that everything is drawn on. You can have multiple independent figures and
Figures can contain multiple
Most plotting ocurs on an
Axes. The axes is effectively the area that we plot data on and any ticks/labels/etc associated with it. Usually we'll set up an Axes with a call to
subplot (which places Axes on a regular grid), so in most cases,
Subplot are synonymous.
Axes has an
XAxis and a
YAxis. These contain the ticks, tick locations, labels, etc. In this tutorial, we'll mostly control ticks, tick labels, and data limits through other mechanisms, so we won't touch the individual
Axis part of things all that much. However, it is worth mentioning here to explain where the term
Axes comes from.
In [ ]:import numpy as np import matplotlib.pyplot as plt
In [ ]:fig = plt.figure()
Awww, nothing happened! This is because by default mpl will not show anything until told to do so, as we mentioned earlier in the "backend" discussion.
Instead, we'll need to call
In [ ]:plt.show()
Great, a blank figure! Not terribly useful yet.
However, while we're on the topic, you can control the size of the figure through the
figsize argument, which expects a tuple of
(width, height) in inches.
A really useful utility function is
In [ ]:# Twice as tall as it is wide: fig = plt.figure(figsize=plt.figaspect(2.0)) plt.show()
All plotting is done with respect to an
Axes. An Axes is made up of
Axis objects and many other things. An Axes object must belong to a Figure (and only one Figure). Most commands you will ever issue will be with respect to this Axes object.
Typically, you'll set up a
Figure, and then add an
Axes to it.
You can use
fig.add_axes, but in most cases, you'll find that adding a subplot will fit your needs perfectly. (Again a "subplot" is just an axes on a grid system.)
In [ ]:fig = plt.figure() ax = fig.add_subplot(111) # We'll explain the "111" later. Basically, 1 row and 1 column. ax.set(xlim=[0.5, 4.5], ylim=[-2, 8], title='An Example Axes', ylabel='Y-Axis', xlabel='X-Axis') plt.show()
Notice the call to
set. Matplotlib's objects typically have lots of "explicit setters" -- in other words, functions that start with
set_<something> and control a particular option.
To demonstrate this (and as an example of IPython's tab-completion), try typing
ax.set_ in a code cell, then hit the
<Tab> key. You'll see a long list of
Axes methods that start with
For example, we could have written the third line above as:
In [ ]:ax.set_xlim([0.5, 4.5]) ax.set_ylim([-2, 8]) ax.set_title('An Example Axes') ax.set_ylabel('Y-Axis') ax.set_xlabel('X-Axis')
Clearly this can get repitive quickly. Therefore, Matplotlib's
set method can be very handy. It takes each kwarg you pass it and tries to call the corresponding "setter". For example,
foo.set(bar='blah') would call
Note that the
set method doesn't just apply to
Axes; it applies to more-or-less all matplotlib objects.
However, there are cases where you'll want to use things like
ax.set_xlabel('Some Label', size=25) to control other options for a particular function.
Most plotting happens on an
Axes. Therefore, if you're plotting something on an axes, then you'll use one of its methods.
We'll talk about different plotting methods in more depth in the next section. For now, let's focus on two methods:
plot draws points with lines connecting them.
scatter draws unconnected points, optionally scaled or colored by additional variables.
As a basic example:
In [ ]:fig = plt.figure() ax = fig.add_subplot(111) ax.plot([1, 2, 3, 4], [10, 20, 25, 30], color='lightblue', linewidth=3) ax.scatter([0.3, 3.8, 1.2, 2.5], [11, 25, 9, 26], color='darkgreen', marker='^') ax.set_xlim(0.5, 4.5) plt.show()
Interestingly, just about all methods of an Axes object exist as a function in the pyplot module (and vice-versa). For example, when calling
plt.xlim(1, 10), pyplot calls
ax.set_xlim(1, 10) on whichever Axes is "current". Here is an equivalent version of the above example using just pyplot.
In [ ]:plt.plot([1, 2, 3, 4], [10, 20, 25, 30], color='lightblue', linewidth=3) plt.scatter([0.3, 3.8, 1.2, 2.5], [11, 25, 9, 26], color='darkgreen', marker='^') plt.xlim(0.5, 4.5) plt.show()
Much cleaner, and much clearer! So, why will most of my examples not follow the pyplot approach? Because PEP20 "The Zen of Python" says:
"Explicit is better than implicit"
While very simple plots, with short scripts would benefit from the conciseness of the pyplot implicit approach, when doing more complicated plots, or working within larger scripts, you will want to explicitly pass around the Axes and/or Figure object to operate upon.
The advantage of keeping which axes we're working with very clear in our code will become more obvious when we start to have multiple axes in one figure.
In [ ]:fig, axes = plt.subplots(nrows=2, ncols=2) plt.show()
plt.subplots(...) created a new figure and added 4 subplots to it. The
axes object that was returned is a 2D numpy object array. Each item in the array is one of the subplots. They're laid out as you see them on the figure.
Therefore, when we want to work with one of these axes, we can index the
axes array and use that item's methods.
In [ ]:fig, axes = plt.subplots(nrows=2, ncols=2) axes[0,0].set(title='Upper Left') axes[0,1].set(title='Upper Right') axes[1,0].set(title='Lower Left') axes[1,1].set(title='Lower Right') # To iterate over all items in a multidimensional numpy array, use the `flat` attribute for ax in axes.flat: # Remove all xticks and yticks... ax.set(xticks=, yticks=) plt.show()
One really nice thing about
plt.subplots() is that when it's called with no arguments, it creates a new figure with a single subplot.
Any time you see something like
fig = plt.figure() ax = fig.add_subplot(111)
You can replace it with:
fig, ax = plt.subplots()
We'll be using that approach for the rest of the examples. It's much cleaner.
However, keep in mind that we're still creating a figure and adding axes to it. When we start making plot layouts that can't be described by
subplots, we'll go back to creating the figure first and then adding axes to it one-by-one.
In [ ]:%load exercises/1.1-subplots_and_basic_plotting.py
In [ ]:import numpy as np import matplotlib.pyplot as plt # Try to reproduce the figure shown in images/exercise_1-1.png # Our data... x = np.linspace(0, 10, 100) y1, y2, y3 = np.cos(x), np.cos(x + 1), np.cos(x + 2) names = ['Signal 1', 'Signal 2', 'Signal 3'] # Can you figure out what to do next to plot x vs y1, y2, and y3 on one figure?