matplotlib-users Mailing List for matplotlib

> -----Original Message-----
> From: Jae-Joon Lee [mailto:lee...@gm...]
> Sent: Tuesday, May 11, 2010 8:58 AM
> To: Matplotlib Users
> Subject: [Matplotlib-users] introducing mpl_toolkits.gridspec
> 
> Hi,
> 
> gridspec is a module that implements matplotlib’s Subplot slightly
> differently. Current matplotlib’s Subplot only allows a Subplot to
> occupy a single cell of the n x m grid. gridspec enables a Subplot to
> occupy multiple cells.
> 
> http://leejjoon.github.com/mpl_toolkits-gridspec/
This is really awesome! Thanks for all the time and hard work, JJ.
-paul

Hi folks,
I just created a tiny prototype of an 'oscilloscope'. I get live data from a
robot via UDP. My network class calls the update() of the oscilloscope. The
oscilloscope is part of an existing GTK app which runs on an Ubuntu.
I have three questions:
1) Since it's my first animation with matplotlib I'm not sure if this is really
 the best way to do it (probably not :)). I especially dislike the creation of
 np.array which could take a bit once I have a lot of data.
2) Is the integration in a GTK app like it is now ok or is there a better way?
 I don't want to loose the zoom and move ability of the standard plot figure
 though. And I need fast results so I don't want to spent to much time
 tweaking this.
3) I get a *weird* X error when calling the update method from the network
 class which probably doesn't have to do anything with matplotlib but I'm
 asking anyway :)
 robocup@robocup2-laptop:~/fumanoid/Desktop-Debug-YUV422$ ../install.py
 /usr/lib/pymodules/python2.6/matplotlib/backends/backend_gtk.py:621:
 DeprecationWarning: Use the new widget gtk.Tooltip
 test from 0: 254/508
 The program 'install.py' received an X Window System error.
 This probably reflects a bug in the program.
 The error was 'RenderBadPicture (invalid Picture parameter)'.
 (Details: serial 11627 error_code 158 request_code 148 minor_code 7)
 (Note to programmers: normally, X errors are reported asynchronously;
 that is, you will receive the error a while after causing it.
 To debug your program, run it with the --sync command line
 option to change this behavior. You can then get a meaningful
 backtrace from your debugger if you break on the gdk_x_error() function.)
 Sometimes it crashes instantly, sometimes it works for a few calls.
 Calling update() from the interactive shell works fine though and displays
 everything. So I don't know if it's really X like the error message
 suggests or what. Did anybody of you experience something like this?
This is the oscilloscope:
import numpy as np
import matplotlib
#matplotlib.use('GTKAgg') # do this before importing pylab
# does not really change anything
import pylab
import matplotlib.pyplot as plt
class Oscilloscope():
 def __init__(self):
 # var for a moving window; not implemented yet
 self.NO_OF_DATA_TO_PLOT = 0
 plt.ion()
 self.fig = plt.figure()
 self.ax = self.fig.add_subplot(111)
 self.ax.grid()
 # list of raw data
 self.raw_data_x = []
 self.raw_data_y = []
 self.graph_lim = dict(x_min=None, x_max=None,
 y_min=None, y_max=None)
 # get line of data to be able to extend it later
 self.line, = self.ax.plot(np.array(self.raw_data_x),
 np.array(self.raw_data_y))
 # open the figure window
 self.fig.canvas.draw()
 def update(self, x, y):
 """Draw new data consisting of x and y."""
 print 'in update'
 self.raw_data_x.append(x)
 self.raw_data_y.append(y)
 # add new data
 self.line.set_xdata(np.array( self.raw_data_x))
 self.line.set_ydata(np.array(self.raw_data_y))
 # redraw the canvas
 self._limit_plot(x, y)
 self.fig.canvas.draw()
Best,
 Stefan

It is version 0.99.1.2.
On 05/11/2010 12:54 PM, Michael Droettboom wrote:
> Is this with matplotlib 0.99.1.2, or SVN trunk? 0.99.1.2 has a known 
> bug in the path simplification algorithm.
>
> Mike
>
> Lane Brooks wrote:
>> I am seeing a problem with the path.simplify rcParam. When it is 
>> enabled, I see spikes in my plots appear and disappear when I resize 
>> the plotting window. When it is disabled, this does not happen. 
>> Attached are pictures showing the effect. In the first image, there 
>> is no spike at x=2559. In the second plot, I resized the window 
>> slightly and the spike appears.
>>
>> Is this the expected behavior or is this a bug?
>>
>> Thanks,
>> Lane
>>
>> ------------------------------------------------------------------------
>>
>>
>> ------------------------------------------------------------------------
>>
>> ------------------------------------------------------------------------
>>
>> ------------------------------------------------------------------------------ 
>>
>>
>> 
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> Matplotlib-users mailing list
>> Mat...@li...
>> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
>

Is this with matplotlib 0.99.1.2, or SVN trunk? 0.99.1.2 has a known 
bug in the path simplification algorithm.
Mike
Lane Brooks wrote:
> I am seeing a problem with the path.simplify rcParam. When it is 
> enabled, I see spikes in my plots appear and disappear when I resize 
> the plotting window. When it is disabled, this does not happen. 
> Attached are pictures showing the effect. In the first image, there is 
> no spike at x=2559. In the second plot, I resized the window slightly 
> and the spike appears.
>
> Is this the expected behavior or is this a bug?
>
> Thanks,
> Lane
>
> ------------------------------------------------------------------------
>
>
> ------------------------------------------------------------------------
>
> ------------------------------------------------------------------------
>
> ------------------------------------------------------------------------------
>
> 
> ------------------------------------------------------------------------
>
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
> 
-- 
Michael Droettboom
Science Software Branch
Operations and Engineering Division
Space Telescope Science Institute
Operated by AURA for NASA

I am seeing a problem with the path.simplify rcParam. When it is 
enabled, I see spikes in my plots appear and disappear when I resize the 
plotting window. When it is disabled, this does not happen. Attached are 
pictures showing the effect. In the first image, there is no spike at 
x=2559. In the second plot, I resized the window slightly and the spike 
appears.
Is this the expected behavior or is this a bug?
Thanks,
Lane

On Tue, May 11, 2010 at 11:39 AM, Jae-Joon Lee <lee...@gm...> wrote:
>> 2) Do you plan on checking this into mpl trunk (still as a mpl_toolkit module)?
This looks sufficiently general and useful that we may simply want it
to live in the main tree (not as a toolkit) and have subplot2grd
helper functionality available directly from pyplot.
JDH

Le mardi 11 mai 2010 à 12:39 -0400, Jae-Joon Lee a écrit :
> > 2) Do you plan on checking this into mpl trunk (still as a
> mpl_toolkit module)?
> Not at this moment. But, will consider if there is enough interest.
+1

On 5/11/2010 11:57 AM, Jae-Joon Lee wrote:
> http://leejjoon.github.com/mpl_toolkits-gridspec/
Yea!
Thanks!
Alan Isaac

On Tue, May 11, 2010 at 12:10 PM, Ryan May <rm...@gm...> wrote:
> 1) How does this relate to the functionality present in your axes_grid toolkit?
axes_grid toolkit is more flexible and is mainly meant to work with
axes with images. gridspec is more for normal axes.
As a matter of fact, the multiple axes created by axes_grid toolkit
usually occupies the area of a single subplot. So, to me, axes_grid
toolkit is something that allows me to divide the area of a single
subplot for multiple images, and gridspec is a replacement of the
subplot.
> 2) Do you plan on checking this into mpl trunk (still as a mpl_toolkit module)?
Not at this moment. But, will consider if there is enough interest.
Regards,
-JJ

On Tue, May 11, 2010 at 10:57 AM, Jae-Joon Lee <lee...@gm...> wrote:
> gridspec is a module that implements matplotlib’s Subplot slightly
> differently. Current matplotlib’s Subplot only allows a Subplot to
> occupy a single cell of the n x m grid. gridspec enables a Subplot to
> occupy multiple cells.
>
> http://leejjoon.github.com/mpl_toolkits-gridspec/
>
> The code is hosted in the github repo
>
> http://github.com/leejjoon/mpl_toolkits-gridspec
>
> and the source can be downloaded from
>
> http://github.com/leejjoon/mpl_toolkits-gridspec/downloads
>
> This is motivated from the discussion in the mailing list a while ago.
>
> http://sourceforge.net/mailarchive/message.php?msg_id=4A0DA94E.1040500%40american.edu
>
> I originally prepared this as a patch for matplotlib
> (http://article.gmane.org/gmane.comp.python.matplotlib.general/19097),
> but never committed. Instead, it is packaged as a mpl_tookit module.
Looks interesting, I'll have to take a look when I get a chance. Two
early questions:
1) How does this relate to the functionality present in your axes_grid toolkit?
2) Do you plan on checking this into mpl trunk (still as a mpl_toolkit module)?
Ryan
-- 
Ryan May
Graduate Research Assistant
School of Meteorology
University of Oklahoma

Hi,
 gridspec is a module that implements matplotlib’s Subplot slightly
differently. Current matplotlib’s Subplot only allows a Subplot to
occupy a single cell of the n x m grid. gridspec enables a Subplot to
occupy multiple cells.
 http://leejjoon.github.com/mpl_toolkits-gridspec/
The code is hosted in the github repo
 http://github.com/leejjoon/mpl_toolkits-gridspec
and the source can be downloaded from
 http://github.com/leejjoon/mpl_toolkits-gridspec/downloads
This is motivated from the discussion in the mailing list a while ago.
http://sourceforge.net/mailarchive/message.php?msg_id=4A0DA94E.1040500%40american.edu
I originally prepared this as a patch for matplotlib
(http://article.gmane.org/gmane.comp.python.matplotlib.general/19097),
but never committed. Instead, it is packaged as a mpl_tookit module.
Regards,
-JJ

Folks,
Is there a way to "unpick" data that was previously "picked"?
The issue is that pick, is very precise. I cannot depend on a identical 
click, in the exact same location, to create the "unpick" tool and 
behavior that I am looking for.
It occurs to me that it is possible to create an "unpick" event by 
creating a matrix of data that surrounds the unpick location and then if 
the picked data point is within this matrix of data, I can process and 
remove the originally picked point from the location I am storing the 
original pick locations.
Maybe Pygame or a collision tool might work also, but I have to study to 
find out.
Is there another preferred way that you see? or can recommend?
Thank You and Best Regards,
Michael Frauens

Hi all,
When creating a new colormap, with a script based on the example given here:
http://www.scipy.org/Cookbook/Matplotlib/Show_colormaps
When plotting the data, and when adding the colobar, I get this error:
In [27]: Exception in Tkinter callback
Traceback (most recent call last):
 File "/usr/lib/python2.6/lib-tk/Tkinter.py", line 1413, in __call__
 return self.func(*args)
 File 
"/usr/lib/pymodules/python2.6/matplotlib/backends/backend_tkagg.py", 
line 212, in resize
 self.show()
 File 
"/usr/lib/pymodules/python2.6/matplotlib/backends/backend_tkagg.py", 
line 215, in draw
 FigureCanvasAgg.draw(self)
 File 
"/usr/lib/pymodules/python2.6/matplotlib/backends/backend_agg.py", line 
314, in draw
 self.figure.draw(self.renderer)
 File "/usr/lib/pymodules/python2.6/matplotlib/artist.py", line 46, in 
draw_wrapper
 draw(artist, renderer, *kl)
 File "/usr/lib/pymodules/python2.6/matplotlib/figure.py", line 774, in 
draw
 for a in self.axes: a.draw(renderer)
 File "/usr/lib/pymodules/python2.6/matplotlib/artist.py", line 46, in 
draw_wrapper
 draw(artist, renderer, *kl)
 File "/usr/lib/pymodules/python2.6/matplotlib/axes.py", line 1721, in draw
 a.draw(renderer)
 File "/usr/lib/pymodules/python2.6/matplotlib/collections.py", line 
699, in draw
 return Collection.draw(self, renderer)
 File "/usr/lib/pymodules/python2.6/matplotlib/artist.py", line 46, in 
draw_wrapper
 draw(artist, renderer, *kl)
 File "/usr/lib/pymodules/python2.6/matplotlib/collections.py", line 
201, in draw
 self.update_scalarmappable()
 File "/usr/lib/pymodules/python2.6/matplotlib/collections.py", line 
477, in update_scalarmappable
 self._facecolors = self.to_rgba(self._A, self._alpha)
 File "/usr/lib/pymodules/python2.6/matplotlib/cm.py", line 167, in to_rgba
 x = self.cmap(x, alpha=alpha, bytes=bytes)
 File "/usr/lib/pymodules/python2.6/matplotlib/colors.py", line 488, in 
__call__
 if not self._isinit: self._init()
 File "/usr/lib/pymodules/python2.6/matplotlib/colors.py", line 632, in 
_init
 self._lut[:-3, 2] = makeMappingArray(self.N, self._segmentdata['blue'])
 File "/usr/lib/pymodules/python2.6/matplotlib/colors.py", line 416, in 
makeMappingArray
 raise TypeError("data must be convertable to an array")
TypeError: data must be convertable to an array
When I don't change the example from the cookbook, I still get the same 
error, and no image. Previously, I didn't get this error. I'm using 
Python 2.6 and MPL 0.99.0 on Ubuntu 9.10.
Any help would be great!
Marius.