matplotlib-devel Mailing List for matplotlib

 I am generating a few hundred graphs and doing so takes on the order of
about 10-15 minutes. Which seems to me rather slow. When I profile my cod=
e
it identifies the calls to get_yticklabels and get_xticklabels as taking
over 90% of the time. This seems strange but my calls to these functions
are merely a sort round about way of setting the font size of the axis tick
labels and suppressing the text for the xticklabels. Is there a more
efficient and cleaner way to do this?
 artist.setp(axes.get_yticklabels(), visible=3DTrue, fontsize=3D7)
 artist.setp(axes.get_xticklabels(), visible=3DFalse)
I am using matplotlib version 0.83.1 and the .png format for my output, if
that helps. Though the profiler seems to suggest that the output is
blazingly fast and it is only these calls to the get_?ticklabels that are
slow.

Note:
 The "crash" only occurs if you run the script and press directly the
replot button.
If you click on the second page of the notebook then back to the first and
"replot"
no problem. Though no problem at all if the "# GTK+ 2.x style draw()" is
used in
matplotlib_gtk.py
Regards,
David
2006年2月19日, David TREMOUILLES <dav...@gm...>:
>
> Here is a quick and dirty minimal code reproducing the problem.
>
> David
>
> 2006年2月17日, Steve Chaplin <ste...@ya...>:
> >
> > On Wed, 2006年02月15日 at 20:36 -0800,
> > mat...@li... wrote:
> > > Hello,
> > >
> > > I'm using matplotlib figures in several places at a time in my GT=
K
> >
> > > based app (means different page in a notebook).
> > > I have trace a bug I partially solved but still doubting if it is a
> > > matplotlib bug or a bad design of my app.
> > >
> > > Matplotlib 0.86.2
> > > pygtk-2.8.4
> > > gtk+-2.8.6
> > >
> > > Here is the problem:
> > >
> > > in matplotlib/backends/backend_gtk.py file, in
> > > class FigureCanvasGTK (gtk.DrawingArea, FigureCanvasBase):
> > > ... in:
> > >
> > > def draw(self):
> > > # synchronous window redraw (like GTK+ 1.2 used to do)
> > > # Note: this does not follow the usual way that GTK redraws,
> > > # which is asynchronous redraw using calls to
> > > gtk_widget_queue_draw(),
> > > # which triggers an expose-event
> > >
> > > # GTK+ 2.x style draw()
> > > 1- self._need_redraw =3D True
> > > 1- self.queue_draw()
> > >
> > > # synchronous draw (needed for animation)
> > > 2- x, y, w, h =3D self.allocation
> > > 2- if w<3 or h<3: return # empty fig
> > >
> > > 2- self._pixmap_prepare (w, h)
> > > 2- self._render_figure(self._pixmap, w, h)
> > > 2- self._need_redraw =3D False
> > > 2- self.window.draw_drawable (self.style.fg_gc[self.state],
> > > 2- self._pixmap, 0, 0, 0, 0, w, h)
> > >
> > >
> > > If I use method 1- (and comment 2-) no problem, all run smoothly...
> > > But using the default method, switching on method 2- (and comment 1-)
> > > I get the followig error message when trying to redraw one of the
> > > figure
> > > (the figure is plotted correctly the first time. No change made to th=
e
> > > figure, just redrawing...)
> > >
> > > ***/python2.4/site-packages/matplotlib/backends/backend_gtk.py:298:
> > > GtkWarning: gdk_pixmap_new: assertion `(drawable !=3D NULL) || (depth=
 !=3D
> >
> > > -1)' failed
> > > self._pixmap_height)
> > > Traceback (most recent call last):
> > > ...
> > > self.canvas_leak.draw()
> > > File
> > > "***/python2.4/site-packages/matplotlib/backends/backend_gtk.py", lin=
e
> >
> > > 250, in draw
> > > self._pixmap_prepare (w, h)
> > > File
> > > "***/python2.4/site-packages/matplotlib/backends/backend_gtk.py", lin=
e
> > > 298, in _pixmap_prepare
> > > self._pixmap_height)
> > > RuntimeError: could not create GdkPixmap object
> > >
> > > Somebody has a clue ???
> > >
> > Its difficult to say if its bug in backend_gtk.py, it depends on exactl=
y
> > what your application is doing. You would need to post a minimal test
> > case that demonstrates the bug so we could see whats going on.
> >
> > Steve
> >
> > Send instant messages to your online friends
> > http://au.messenger.yahoo.com
> >
> >
>
>

Here is a quick and dirty minimal code reproducing the problem.
David
2006年2月17日, Steve Chaplin <ste...@ya...>:
>
> On Wed, 2006年02月15日 at 20:36 -0800,
> mat...@li... wrote:
> > Hello,
> >
> > I'm using matplotlib figures in several places at a time in my GTK
> > based app (means different page in a notebook).
> > I have trace a bug I partially solved but still doubting if it is a
> > matplotlib bug or a bad design of my app.
> >
> > Matplotlib 0.86.2
> > pygtk-2.8.4
> > gtk+-2.8.6
> >
> > Here is the problem:
> >
> > in matplotlib/backends/backend_gtk.py file, in
> > class FigureCanvasGTK (gtk.DrawingArea, FigureCanvasBase):
> > ... in:
> >
> > def draw(self):
> > # synchronous window redraw (like GTK+ 1.2 used to do)
> > # Note: this does not follow the usual way that GTK redraws,
> > # which is asynchronous redraw using calls to
> > gtk_widget_queue_draw(),
> > # which triggers an expose-event
> >
> > # GTK+ 2.x style draw()
> > 1- self._need_redraw = True
> > 1- self.queue_draw()
> >
> > # synchronous draw (needed for animation)
> > 2- x, y, w, h = self.allocation
> > 2- if w<3 or h<3: return # empty fig
> >
> > 2- self._pixmap_prepare (w, h)
> > 2- self._render_figure(self._pixmap, w, h)
> > 2- self._need_redraw = False
> > 2- self.window.draw_drawable (self.style.fg_gc[self.state],
> > 2- self._pixmap, 0, 0, 0, 0, w, h)
> >
> >
> > If I use method 1- (and comment 2-) no problem, all run smoothly...
> > But using the default method, switching on method 2- (and comment 1-)
> > I get the followig error message when trying to redraw one of the
> > figure
> > (the figure is plotted correctly the first time. No change made to the
> > figure, just redrawing...)
> >
> > ***/python2.4/site-packages/matplotlib/backends/backend_gtk.py:298:
> > GtkWarning: gdk_pixmap_new: assertion `(drawable != NULL) || (depth !=
> > -1)' failed
> > self._pixmap_height)
> > Traceback (most recent call last):
> > ...
> > self.canvas_leak.draw()
> > File
> > "***/python2.4/site-packages/matplotlib/backends/backend_gtk.py", line
> > 250, in draw
> > self._pixmap_prepare (w, h)
> > File
> > "***/python2.4/site-packages/matplotlib/backends/backend_gtk.py", line
> > 298, in _pixmap_prepare
> > self._pixmap_height)
> > RuntimeError: could not create GdkPixmap object
> >
> > Somebody has a clue ???
> >
> Its difficult to say if its bug in backend_gtk.py, it depends on exactly
> what your application is doing. You would need to post a minimal test
> case that demonstrates the bug so we could see whats going on.
>
> Steve
>
> Send instant messages to your online friends http://au.messenger.yahoo.com
>
>

Hi,
I've got a situation where I'd like to create several instances of Axes
but not set their position until later. It seems I have to jump through
hoops to actually create a new axes, contrary to my expectation:
$ ipython -pylab
In [1]: a=axes()
In [2]: a
Out[2]: <matplotlib.axes.Subplot instance at 0x2aaab158a758>
In [3]: b=axes()
In [4]: b
Out[4]: <matplotlib.axes.Subplot instance at 0x2aaab158a758>
I can see what's happening here:
 1. pylab.axes() calls subplot(111) when no arguments are given.
 2. subplot(111) uses some smarts to figure out if an Axes instance for
subplot(111) has already been given and, if so, returns a reference to that.
Both points 1 and 2 seem reasonable on their own, but when combined, as
in my example, the outcome is not intuitive. Is this behavior desired?
Does anyone depend on it?
It goes deeper -- even Figure.add_axes() returns an old Axes instance if
the rect given has been seen before. I'd argue that people delving into
the OO innards of matplotlib should be able to handle keeping a
reference to instances of Axes they've created. Can we change this
behavior or would it cause massive breakage somewhere?
Cheers!
Andrew