Hi,
I recently upgraded to matplotlib v1.2.0 on my Linux machine. For some reason, plots are not appearing at all on my screen whenever I try to plot any routines.
When I open the interpreter with “ipython --pylab” and do
In [1]: plot(1,1)
Out[1]: [<matplotlib.lines.Line2D object at 0x2a40450>]
No plot shows up. This is somewhat strange as no other error shows up either. Does anyone know of a way to debug this? I’m not sure where to start.
I also tried to run a simple plot in a script with
from matplotlib.pyplot import *
figure()
plot(1,1)
draw(); show()
and still had no success.
Thanks,
Tim
Which backend are you using?
In [1]: import matplotlib
In [2]: matplotlib.rcParams['backend']
Out[2]: 'Qt4Agg'
···
On Mon, Dec 10, 2012 at 12:15 PM, Timothy Duly <timduly4@...287...> wrote:
Hi,
I recently upgraded to matplotlib v1.2.0 on my Linux machine. For some
reason, plots are not appearing at all on my screen whenever I try to plot
any routines.
When I open the interpreter with "ipython --pylab" and do
In [1]: plot(1,1)
Out[1]: [<matplotlib.lines.Line2D object at 0x2a40450>]
No plot shows up. This is somewhat strange as no other error shows up
either. Does anyone know of a way to debug this? I'm not sure where to
start.
I also tried to run a simple plot in a script with
from matplotlib.pyplot import *
figure()
plot(1,1)
draw(); show()
and still had no success.
Thanks,
Tim
Paul,
I am using the “agg” backend:
In [1]: import matplotlib
In [2]: matplotlib.rcParams[‘backend’]
Out[2]: ‘agg’
I was able to switch it to the one you have:
In [12]: import matplotlib
In [13]: matplotlib.rcParams[‘backend’] = ‘Qt4Agg’
but still a simple “plot(1,1)” resulted in no plot being shown.
Thanks,
Tim
···
On Mon, Dec 10, 2012 at 2:20 PM, Paul Hobson <pmhobson@…287…> wrote:
On Mon, Dec 10, 2012 at 12:15 PM, Timothy Duly <timduly4@…287…> wrote:
Hi,
I recently upgraded to matplotlib v1.2.0 on my Linux machine. For some reason, plots are not appearing at all on my screen whenever I try to plot any routines.
When I open the interpreter with “ipython --pylab” and do
In [1]: plot(1,1)
Out[1]: [<matplotlib.lines.Line2D object at 0x2a40450>]
No plot shows up. This is somewhat strange as no other error shows up either. Does anyone know of a way to debug this? I’m not sure where to start.
I also tried to run a simple plot in a script with
from matplotlib.pyplot import *
figure()
plot(1,1)
draw(); show()
and still had no success.
Thanks,
Tim
Which backend are you using?
In [1]: import matplotlib
In [2]: matplotlib.rcParams[‘backend’]
Out[2]: ‘Qt4Agg’
Paul,
Actually, I didn’t realize that you had to change the backend in the matplotlibrc file. Once I changed it to ‘Qt4Agg’, everything worked. Thanks!
(to find out where your matplotlibrc file is: “matplotlib.matplotlib_fname()” )
Tim
···
On Mon, Dec 10, 2012 at 2:34 PM, Timothy Duly <timduly4@…287…> wrote:
Paul,
I am using the “agg” backend:
In [1]: import matplotlib
In [2]: matplotlib.rcParams[‘backend’]
Out[2]: ‘agg’
I was able to switch it to the one you have:
In [12]: import matplotlib
In [13]: matplotlib.rcParams[‘backend’] = ‘Qt4Agg’
but still a simple “plot(1,1)” resulted in no plot being shown.
Thanks,
Tim
On Mon, Dec 10, 2012 at 2:20 PM, Paul Hobson <pmhobson@…287…> wrote:
On Mon, Dec 10, 2012 at 12:15 PM, Timothy Duly <timduly4@…1972…> wrote:
Hi,
I recently upgraded to matplotlib v1.2.0 on my Linux machine. For some reason, plots are not appearing at all on my screen whenever I try to plot any routines.
When I open the interpreter with “ipython --pylab” and do
In [1]: plot(1,1)
Out[1]: [<matplotlib.lines.Line2D object at 0x2a40450>]
No plot shows up. This is somewhat strange as no other error shows up either. Does anyone know of a way to debug this? I’m not sure where to start.
I also tried to run a simple plot in a script with
from matplotlib.pyplot import *
figure()
plot(1,1)
draw(); show()
and still had no success.
Thanks,
Tim
Which backend are you using?
In [1]: import matplotlib
In [2]: matplotlib.rcParams[‘backend’]
Out[2]: ‘Qt4Agg’
Usually, you don’t have to, but I guess something happened with your install at some point that messed around with your rc file. Glad to see it fixed.
Ben Root