matplotlib-users Mailing List for matplotlib

matplotlib list: I've moved this thread over to the ipython list.
f

This is a bit bizarre.
It took me a couple looks to figure out what was happening.
I am using the 'run' command under IPython.
Error tracebacks print the correct line number of the 
current file but *list* (and therefore highlight) that
line from an *earlier* version of the file.
This is particularly obvious when deleted lines
appear in the traceback printout.
After a bit of exploration, it seems that the lines
printed corrrespond to the file as first run. Changes
to the file are correctly run and traced, but the lines
printed appear to be from a cached (and obsolete)
version of the file.
Has anyone else seen this?
Any thoughts on how to fix it?
Cheers,
Alan Isaac

Great thank you. 
One more question. I also want to change the tick mark attributes like
color, fontsize, rotation etc. I used these lines of code:
 # set x-axes tick label attributes
 axesA.set_yticklabels(axesA.get_xticklabels(), rotation=0,
fontsize=5, color='k')
 axesD.set_yticklabels(axesD.get_xticklabels(), rotation=0,
fontsize=5, color='k')
 # set y-axes tick label attributes 
 axesA.set_yticklabels(axesA.get_yticklabels(), rotation=0,
fontsize=5, color='k')
 axesD.set_yticklabels(axesD.get_yticklabels(), rotation=0,
fontsize=5, color='k')
I get an error because get_ticklabels() returns an instance of label
strings, not the strings themselves. How can I convert these into a
useful string so the above code works? Or is there a better way to do
this?
Thanks again! 
-----Original Message-----
From: John Hunter [mailto:jdh...@ni...] 
Sent: Wednesday, July 13, 2005 10:41 AM
To: Jeff Peery
Cc: mat...@li...
Subject: Re: [Matplotlib-users] transparent symbols
>>>>> "Jeff" == Jeff Peery <jef...@se...> writes:
 Jeff> Hello, I attached a sample. I'm trying to plot a line using
 Jeff> markers and I would like those markers to be transparent. I
 Jeff> use the keyword 'alpha=0.2' to set the transparency although
 Jeff> the marker are not transparent? Does anyone know how to make
 Jeff> this work? Thanks for the help!
See the recent thread "transparent markerfacecolors"
 http://sourceforge.net/mailarchive/message.php?msg_id=12261949
Basically, this is a bug but you can work around it with scatter.
 Jeff> Also, is it possible to set autoscale for just x-axis or
 Jeff> just y-axis? I haven't found a way to do this. Thanks again.
You can do this by setting a custom ticker.locator for the axis that
you don't want autoscaled, following the examples major_minor_demo*.py
and Chapter 5 of the user's guide.
JDH

>>>>> "Jeff" == Jeff Peery <jef...@se...> writes:
 Jeff> Hello, I attached a sample. I'm trying to plot a line using
 Jeff> markers and I would like those markers to be transparent. I
 Jeff> use the keyword 'alpha=0.2' to set the transparency although
 Jeff> the marker are not transparent? Does anyone know how to make
 Jeff> this work? Thanks for the help!
See the recent thread "transparent markerfacecolors"
 http://sourceforge.net/mailarchive/message.php?msg_id=12261949
Basically, this is a bug but you can work around it with scatter.
 Jeff> Also, is it possible to set autoscale for just x-axis or
 Jeff> just y-axis? I haven't found a way to do this. Thanks again.
You can do this by setting a custom ticker.locator for the axis that
you don't want autoscaled, following the examples major_minor_demo*.py
and Chapter 5 of the user's guide.
JDH

John Hunter wrote:
>>>>>>"Eugen" == Eugen Wintersberger <eug...@jk...> writes:
> 
> 
> Eugen> Hi there I have a problem with matplotlib (0.8) and IPython
> Eugen> (0.6.15) on a Debian 3.1 system together with the GTK
> Eugen> interface. Ipython crashes when one tries to make a simple
> Eugen> plot. This is quite strange since I changes from a former
> Eugen> setup with ipython (0.6.13) to iptyon (0.6.15) to use the
> Eugen> GTK interface and it worked quite well. It seems that
> Eugen> maybe changing from Debian testing to stable maybe messed
> Eugen> up the setup. Has anyone an idea where the problem
> Eugen> described below comes from.
> 
> I took a quick look over your strace and didn't see anything obviou.
> You might want to bring this up with the debian maintainer, because I
> have never seen this error before and so it may not be a matplotlib
> problem per se.
I also had a look, and on first guess I'd venture it's a GTK bug. All the 
internal errors seem to be related to GTK font handling and interactions with 
X11. It certainly doesn't look like anything caused by matplotlib (and since 
ipython is pure python, it can't cause segfaults by itself).
Cheers,
f

Hello, I attached a sample. I'm trying to plot a line using markers and
I would like those markers to be transparent. I use the keyword
'alpha=0.2' to set the transparency although the marker are not
transparent? Does anyone know how to make this work? Thanks for the
help!
Also, is it possible to set autoscale for just x-axis or just y-axis? I
haven't found a way to do this. Thanks again.
Jeff

>>>>>> "Alan" == Alan G Isaac <ai...@am...> writes: 
> Alan> Not a big deal but ... Would it not be natural for date2num 
> Alan> to accept an rrule as an argument? I.e., why force us to 
> Alan> make a list of an rrule? 
On 2005年7月13日, John Hunter apparently wrote: 
> But rrules need a before and after to define their endpoints. What 
> would this interface to date2num look like? 
> I have no problem with this suggestions, but it might be more natural 
> to define 
> def rrule2num(after, before, rrule): 
> return date2num(rrule.between(after, before)) 
> where after and before are datetime instances... 
> return date2num(rrule.between(after, before)) 
I had in mind only rrules that specified the sample exactly,
so that they were already a finite iterable. E.g.,
x = rrule(MONTHLY,dtstart=date(1990,1,1),until=date(2005,1,1),inc=True)
Unfortunately rrule.count() will count forever, so I'm not 
sure how best to check for finitude. I do *not* want to 
propose a new function. It just seemed obvious that date2num 
could easily handle such rrules, but I was thinking only of 
fully delimited rrules.
Thanks,
Alan

On 2005年7月12日, Eric Firing apparently wrote: 
>>> import numarray as N 
>>> from numarray.ieeespecial import isnan, nan 
>>> import numarray.ma as ma 
>>> a = N.array([1, 2, nan, 3, 4]) 
>>> b = ma.masked_where(isnan(a), a) 
> Now you can plot b and it will have a gap in the middle. 
Thanks.
Alan

>I don't think that "plot" has the "set_data" attribute that I need in or=
der
>to interact with every single point of the plot, but I may be wrong.
>
>Andrea.
Sorry, I have said something stupid. Of course I can use plot, now it's
working. However, I have another (probably basic) question. In order to
reverse the y-axis, for example, the only way I found is to get the minim=
um
and the maximum of my data and then do something like:
myaxes.set_ylim(mymax, mymin)
Is there a more intelligent way? I mean, in this way I have to calculate
the minimum and maximum values for every series of point I have, then low=
er
the minimum and increase the maximum by a small quantity in order to make=
the plot looking better (and not tighten to the data) and then use set_yl=
im.
In the standard case (no axis reverse), is matplotlib that does all the
job and it presents me the plot, nice scaled. What I usually do in Matlab=
,
is something like set(myaxes, 'ydir', 'reverse'), and it does the job...
does anything similar exists for matplotlib? 
Sorry if it is a very basic question.
Andrea.

>can't you use plot() instead of Line2D? something like:
>
>b =3D fig.subplot
>b.plot(your_data, marker=3D'0', linestyle=3DNone)
I don't think that "plot" has the "set_data" attribute that I need in ord=
er
to interact with every single point of the plot, but I may be wrong.
Andrea.

On Jul 13, 2005, at 9:57 AM, and...@ti... wrote:
>> Have you seen examples/poly_editor.py? It plots a polygon and at each
>> vertex plots a marker. You can click on the marker and drag it and
>> move the vertex around, as well as insert and delete vertices. It
>> would be easy to modify the callback to change the marker color, size
>> etc, to indicate that it is selected. The example doesn't do what you
>> are want precisely, but does provide a lot of code illustrating how to
>> do these things with mpl event handling.
>
> Thanks John for the pointer! You gave me a lot of new ideas...
> Just another (probably stupid) question, but I'm becoming crazy to 
> solve
> it. In my plot, I would like to have the points plotted as dots and 
> *without*
> the line that connects them. I am using Line2D from 
> matplotlib.lines.Line2D
> as:
>
> axdata = self.fig.add_subplot(111)
> self.line = Line2D(pressure, depths, marker='o', markerfacecolor='r', 
> linestyle=None)
> axdata.add_line(self.line)
>
> But whatever option I use, the connecting line is still there... is 
> there
> a way to have only the dots?
>
> Thank you a lot.
>
> Andrea.
>
>
can't you use plot() instead of Line2D? something like:
b = fig.subplot
b.plot(your_data, marker='0', linestyle=None)
donour
|Donour Sizemore do...@cs...|
|Technical Programmer & Numerical Analyst |
|Economics Research Center Ph: 773-834-4399 |
|University of Chicago Office: Walker 303-a |

>Have you seen examples/poly_editor.py? It plots a polygon and at each
>vertex plots a marker. You can click on the marker and drag it and
>move the vertex around, as well as insert and delete vertices. It
>would be easy to modify the callback to change the marker color, size
>etc, to indicate that it is selected. The example doesn't do what you
>are want precisely, but does provide a lot of code illustrating how to
>do these things with mpl event handling.
Thanks John for the pointer! You gave me a lot of new ideas...
Just another (probably stupid) question, but I'm becoming crazy to solve
it. In my plot, I would like to have the points plotted as dots and *with=
out*
the line that connects them. I am using Line2D from matplotlib.lines.Line=
2D
as:
axdata =3D self.fig.add_subplot(111)
self.line =3D Line2D(pressure, depths, marker=3D'o', markerfacecolor=3D'r=
', linestyle=3DNone)
axdata.add_line(self.line)
But whatever option I use, the connecting line is still there... is there=
a way to have only the dots? 
Thank you a lot.
Andrea.

>>>>> "Eugen" == Eugen Wintersberger <eug...@jk...> writes:
 Eugen> Hi there I have a problem with matplotlib (0.8) and IPython
 Eugen> (0.6.15) on a Debian 3.1 system together with the GTK
 Eugen> interface. Ipython crashes when one tries to make a simple
 Eugen> plot. This is quite strange since I changes from a former
 Eugen> setup with ipython (0.6.13) to iptyon (0.6.15) to use the
 Eugen> GTK interface and it worked quite well. It seems that
 Eugen> maybe changing from Debian testing to stable maybe messed
 Eugen> up the setup. Has anyone an idea where the problem
 Eugen> described below comes from.
I took a quick look over your strace and didn't see anything obviou.
You might want to bring this up with the debian maintainer, because I
have never seen this error before and so it may not be a matplotlib
problem per se.
JDH

>>>>> "Alan" == Alan G Isaac <ai...@am...> writes:
 Alan> Not a big deal but ... Would it not be natural for date2num
 Alan> to accept an rrule as an argument? I.e., why force us to
 Alan> make a list of an rrule?
But rrules need a before and after to define their endpoints. What
would this interface to date2num look like?
I have no problem with this suggestions, but it might be more natural
to define 
 def rrule2num(after, before, rrule):
 return date2num(rrule.between(after, before))
where after and before are datetime instances...
JDH

>>>>> "andrea" == andrea gavana <and...@ti...> writes:
 andrea> Now, the question: Which is the best approach with
 andrea> Matplotlib for this kind of interaction? Should I plot
 andrea> every point using plot(x1, y1), plot(x2, y2) etc...? Or
 andrea> should I use Collections (i have no idea on what to do
 andrea> with collections)? Scattered plots? Does anyone have any
 andrea> suggestion/pointer for me? Some examples of
 andrea> editing/interacting with plots?
Have you seen examples/poly_editor.py? It plots a polygon and at each
vertex plots a marker. You can click on the marker and drag it and
move the vertex around, as well as insert and delete vertices. It
would be easy to modify the callback to change the marker color, size
etc, to indicate that it is selected. The example doesn't do what you
are want precisely, but does provide a lot of code illustrating how to
do these things with mpl event handling.
Note particularly the "i" functionality for inserting a vertex. To
insert a vertex your cursor must be over a line segment connecting two
vertices. From your description of needing to interact with the line
between two points, it should like this lass might be helpful.
class PolygonInteractor:
 """
 An polygon editor.
 Key-bindings
 't' toggle vertex markers on and off. When vertex markers are on,
 you can move them, delete them
 'd' delete the vertex under point
 'i' insert a vertex at point. You must be within epsilon of the
 line connecting two existing vertices
You might want to define your own "interactor" classes similar to
PolygonInteractor (eg a LineSegmentInteractor). Then the line segment
will encompass all the intelligence you need and can easily be plugged
into your graph.
If you come up with useful widgets like these, please send them our
way. Also feel free to post partially working code if you get stuck,
On a related note, to make something like this work efficiently it
helps to be able to redraw just part of a figure. The current release
of mpl has support for this with GTKAgg only, but only a few new
backend methods that need to be defined to support this. This makes
things like moving objects around the canvas much more efficiently.
It would be nice to have them for the various *Agg backends
The required methods are:
 region = canvas.copy_from_bbox(bbox)
 canvas.restore_region(region)
 canvas.blit(bbox)
region can be any backend dependent object -- the front end doesn't
use it, only passes it around. bbox is a transforms.BBox instance.
If anyone is interested in animation and knows something about Tk, WX,
Qt, FLTK, you may want to take a crack at implementing these methods.
Below is another interaction/widget which provides a Rectangle widget
that can be resized or moved around (GTKAgg only). When you click on
the edge of the rectangle the edgecolor turns red and when you release
it the color is restored. There are some bugs, but it does illustrate
more interaction code as well as provide a test script for anyone who
wants to understand how to use the three methods shown above.
import matplotlib
matplotlib.use('GTKAgg')
from pylab import *
from matplotlib.transforms import lbwh_to_bbox
from matplotlib.mlab import dist_point_to_segment
class RectangleWidget(Rectangle):
 def __init__(self, figure, *args, **kwargs):
 Rectangle.__init__(self, *args, **kwargs)
 self.figure = figure
 self.idle = True
 self.oldbox = self.get_window_extent()
 self.newbox = self.get_window_extent()
 
 self.region = self.figure.canvas.copy_from_bbox(self.oldbox)
 self.figure.canvas.mpl_connect('motion_notify_event', self.move)
 self.figure.canvas.mpl_connect('button_press_event', self.press)
 self.figure.canvas.mpl_connect('button_release_event', self.release) 
 
 self.figure.draw_artist(self) 
 self._resize = False
 self._drag = False
 def redraw(self):
 canvas = self.figure.canvas
 canvas.restore_region(self.region)
 self.region = canvas.copy_from_bbox(self.newbox)
 self.figure.draw_artist(self) 
 canvas.blit(self.oldbox)
 canvas.blit(self.newbox)
 
 def press(self, event):
 if event.button!=1: return
 x, y = self.xy
 w, h = self.width, self.height
 # the four line segments of the rectangle
 lb = x, y
 lt = x, y+h
 rb = x+w, y
 rt = x+w, y+h
 segments = {
 'left' : (lb, lt),
 'right' : (rb, rt),
 'top' : (lt, rt),
 'bottom' : (lb, rb),
 }
 p = event.x, event.y
 near = []
 for name, segment in segments.items():
 s0, s1 = segment
 d = dist_point_to_segment(p, s0, s1)
 if d<5: near.append(name)
 info = event.x, event.y, self.xy[0], self.xy[1], self.width, self.height, near
 if len(near):
 self._resize = info
 self.set_edgecolor('red')
 self.set_linewidth(2)
 else:
 self._resize = False
 if self.get_window_extent().contains(event.x, event.y):
 self._drag = info
 self.redraw()
 def release(self, event):
 if event.button!=1: return
 self._resize = False
 self._drag = False
 self.idle = True
 self.set_edgecolor('black')
 self.set_linewidth(0.5)
 self.redraw()
 
 def move(self, event):
 if not (self.idle and (self._resize or self._drag)): return 
 self.idle = False
 canvas = self.figure.canvas
 if self._resize:
 exo, eyo, xo, yo, wo, ho, near = self._resize
 else:
 exo, eyo, xo, yo, wo, ho, near = self._drag
 scalex=0; scaley=0; scalew=0; scaleh=0
 if 'left' in near:
 scalex = 1
 scalew = -1
 if 'right' in near:
 scalew = 1
 if 'bottom' in near:
 scaley = 1
 scaleh = -1
 if 'top' in near:
 scaleh = 1
 if self._drag:
 scalex = 1
 scaley = 1
 
 dx = event.x - exo
 dy = event.y - eyo
 if event.button ==1:
 self.oldbox = self.get_padded_box()
 newx = xo + scalex*dx
 if scalew==0 or newx<xo+wo:
 self.xy[0] = newx
 newy = yo + scaley*dy
 if scaleh==0 or newy<yo+ho:
 self.xy[1] = newy
 neww = wo + scalew*dx
 if neww>0: self.width = neww
 
 newh = ho + scaleh*dy
 if newh>0: self.height = newh
 
 #self.xy = event.x, event.y
 self.newbox = self.get_padded_box()
 #print event.x, event.y, self.get_padded_box().get_bounds()
 self.redraw()
 self.idle = True
 def get_padded_box(self, pad=5):
 xmin = self.xy[0]-pad
 ymin = self.xy[1]-pad
 return lbwh_to_bbox(xmin, ymin, self.width+2*pad, self.height+2*pad)
 
 
 
ion() 
fig = figure()
def keypress(event):
 if event.key=='n':
 widget = RectangleWidget( fig, (100,100), 20, 30)
 fig.canvas.blit()
fig.canvas.mpl_connect('key_press_event', keypress)
fig.text(0.1, 0.9, "Press n for new rectangle and then resize it or move it")
draw()
show()

Hi there
 I have a problem with matplotlib (0.8) and IPython (0.6.15) on a 
Debian 3.1 system together with the GTK interface. 
Ipython crashes when one tries to make a simple plot. This is quite
strange since I changes from a former setup with ipython (0.6.13) to
iptyon (0.6.15) to use the GTK interface and it worked quite well. 
It seems that maybe changing from Debian testing to stable maybe 
messed up the setup. Has anyone an idea where the problem described 
below comes from.
Starting ipython with the -pylab option and typing
In [1]: x = arrayrange(1,100)
In [2]: plot(x)
gives
 *** Break *** segmentation violation
 Generating stack trace...
 0x40d3cff1 in <unknown> from /usr/X11R6/lib/libX11.so.6
 0x40d28439 in XrmQGetResource + 0x149 from /usr/X11R6/lib/libX11.so.6
 0x40d08896 in XGetDefault + 0xd6 from /usr/X11R6/lib/libX11.so.6
 0x40dd4456 in <unknown> from /usr/lib/libXft.so.2
 0x40dd4592 in <unknown> from /usr/lib/libXft.so.2
 0x40dd4728 in <unknown> from /usr/lib/libXft.so.2
 0x40dd4806 in XftDefaultGetInteger + 0x26 from /usr/lib/libXft.so.2
 0x40dd3e62 in _XftDisplayInfoGet + 0x152 from /usr/lib/libXft.so.2
 0x40dd4218 in XftDefaultHasRender + 0x28 from /usr/lib/libXft.so.2
 0x40dd4ce0 in XftDefaultSubstitute + 0x470 from /usr/lib/libXft.so.2
 0x40ca0a93 in <unknown> from /usr/lib/libpangoxft-1.0.so.0
 0x40ea7503 in <unknown> from /usr/lib/libpangoft2-1.0.so.0
 0x40ea75ab in <unknown> from /usr/lib/libpangoft2-1.0.so.0
 0x40ea78c4 in <unknown> from /usr/lib/libpangoft2-1.0.so.0
 0x40cc48b1 in pango_font_map_load_fontset + 0x81
from /usr/lib/libpango-1.0.so.0
 0x40cc2eb3 in <unknown> from /usr/lib/libpango-1.0.so.0
 0x40cc2f86 in <unknown> from /usr/lib/libpango-1.0.so.0
 0x40cc3258 in pango_itemize_with_base_dir + 0xa8
from /usr/lib/libpango-1.0.so.0
 0x40cca69f in <unknown> from /usr/lib/libpango-1.0.so.0
 0x40cc8b86 in <unknown> from /usr/lib/libpango-1.0.so.0
 0x40cc8ef7 in pango_layout_get_extents + 0x37
from /usr/lib/libpango-1.0.so.0
 0x40cc8f84 in pango_layout_get_pixel_extents + 0x54
from /usr/lib/libpango-1.0.so.0
 0x40977136 in <unknown> from /usr/lib/libgtk-x11-2.0.so.0
 0x409774c1 in <unknown> from /usr/lib/libgtk-x11-2.0.so.0
 0x40971c63 in gtk_cell_renderer_get_size + 0xb3
from /usr/lib/libgtk-x11-2.0.so.0
 0x40b0ca24 in gtk_tree_view_column_cell_get_size + 0x144
from /usr/lib/libgtk-x11-2.0.so.0
 0x40af9ef5 in <unknown> from /usr/lib/libgtk-x11-2.0.so.0
 0x40afaddb in <unknown> from /usr/lib/libgtk-x11-2.0.so.0
 0x40afb165 in <unknown> from /usr/lib/libgtk-x11-2.0.so.0
 0x40af4a25 in <unknown> from /usr/lib/libgtk-x11-2.0.so.0
 0x406e4b63 in g_cclosure_marshal_VOID__BOXED + 0x83
from /usr/lib/libgobject-2.0.so.0
 0x406d29c9 in <unknown> from /usr/lib/libgobject-2.0.so.0
 0x406d2736 in g_closure_invoke + 0xb6 from /usr/lib/libgobject-2.0.so.0
 0x406e3651 in <unknown> from /usr/lib/libgobject-2.0.so.0
 0x406e2e9c in g_signal_emit_valist + 0x73c
from /usr/lib/libgobject-2.0.so.0
 0x406e3216 in g_signal_emit_by_name + 0xe6
from /usr/lib/libgobject-2.0.so.0
 0x40a78ece in <unknown> from /usr/lib/libgtk-x11-2.0.so.0
 0x40a79248 in _gtk_size_group_compute_requisition + 0x68
from /usr/lib/libgtk-x11-2.0.so.0
 0x40b1c61c in gtk_widget_size_request + 0x4c
from /usr/lib/libgtk-x11-2.0.so.0
 0x40a6e113 in <unknown> from /usr/lib/libgtk-x11-2.0.so.0
 0x406e4b63 in g_cclosure_marshal_VOID__BOXED + 0x83
from /usr/lib/libgobject-2.0.so.0
 0x406d29c9 in <unknown> from /usr/lib/libgobject-2.0.so.0
 0x406d2736 in g_closure_invoke + 0xb6 from /usr/lib/libgobject-2.0.so.0
 0x406e3651 in <unknown> from /usr/lib/libgobject-2.0.so.0
 0x406e2e9c in g_signal_emit_valist + 0x73c
from /usr/lib/libgobject-2.0.so.0
 0x406e3216 in g_signal_emit_by_name + 0xe6
from /usr/lib/libgobject-2.0.so.0
 0x40a78ece in <unknown> from /usr/lib/libgtk-x11-2.0.so.0
 0x40a79248 in _gtk_size_group_compute_requisition + 0x68
from /usr/lib/libgtk-x11-2.0.so.0
 0x40b1c61c in gtk_widget_size_request + 0x4c
from /usr/lib/libgtk-x11-2.0.so.0
 0x40b14c23 in <unknown> from /usr/lib/libgtk-x11-2.0.so.0
 0x406e4b63 in g_cclosure_marshal_VOID__BOXED + 0x83
from /usr/lib/libgobject-2.0.so.0
 0x406d29c9 in <unknown> from /usr/lib/libgobject-2.0.so.0
 0x406d2736 in g_closure_invoke + 0xb6 from /usr/lib/libgobject-2.0.so.0
 0x406e3651 in <unknown> from /usr/lib/libgobject-2.0.so.0
 0x406e2e9c in g_signal_emit_valist + 0x73c
from /usr/lib/libgobject-2.0.so.0
 0x406e3216 in g_signal_emit_by_name + 0xe6
from /usr/lib/libgobject-2.0.so.0
 0x40a78ece in <unknown> from /usr/lib/libgtk-x11-2.0.so.0
 0x40a79248 in _gtk_size_group_compute_requisition + 0x68
from /usr/lib/libgtk-x11-2.0.so.0
 0x40b1c61c in gtk_widget_size_request + 0x4c
from /usr/lib/libgtk-x11-2.0.so.0
 0x409f4dcf in <unknown> from /usr/lib/libgtk-x11-2.0.so.0
 0x406e4b63 in g_cclosure_marshal_VOID__BOXED + 0x83
from /usr/lib/libgobject-2.0.so.0
 0x406d29c9 in <unknown> from /usr/lib/libgobject-2.0.so.0
 0x406d2736 in g_closure_invoke + 0xb6 from /usr/lib/libgobject-2.0.so.0
 0x406e3651 in <unknown> from /usr/lib/libgobject-2.0.so.0
 0x406e2e9c in g_signal_emit_valist + 0x73c
from /usr/lib/libgobject-2.0.so.0
 0x406e3216 in g_signal_emit_by_name + 0xe6
from /usr/lib/libgobject-2.0.so.0
 0x40a78ece in <unknown> from /usr/lib/libgtk-x11-2.0.so.0
 0x40a79248 in _gtk_size_group_compute_requisition + 0x68
from /usr/lib/libgtk-x11-2.0.so.0
 0x40b1c61c in gtk_widget_size_request + 0x4c
from /usr/lib/libgtk-x11-2.0.so.0
 0x40b14c23 in <unknown> from /usr/lib/libgtk-x11-2.0.so.0
 0x406e4b63 in g_cclosure_marshal_VOID__BOXED + 0x83
from /usr/lib/libgobject-2.0.so.0
 0x406d29c9 in <unknown> from /usr/lib/libgobject-2.0.so.0
 0x406d2736 in g_closure_invoke + 0xb6 from /usr/lib/libgobject-2.0.so.0
 0x406e3651 in <unknown> from /usr/lib/libgobject-2.0.so.0
 0x406e2e9c in g_signal_emit_valist + 0x73c
from /usr/lib/libgobject-2.0.so.0
 0x406e3216 in g_signal_emit_by_name + 0xe6
from /usr/lib/libgobject-2.0.so.0
 0x40a78ece in <unknown> from /usr/lib/libgtk-x11-2.0.so.0
 0x40a79248 in _gtk_size_group_compute_requisition + 0x68
from /usr/lib/libgtk-x11-2.0.so.0
 0x40b1c61c in gtk_widget_size_request + 0x4c
from /usr/lib/libgtk-x11-2.0.so.0
 0x40b14c23 in <unknown> from /usr/lib/libgtk-x11-2.0.so.0
 0x406e4b63 in g_cclosure_marshal_VOID__BOXED + 0x83
from /usr/lib/libgobject-2.0.so.0
 0x406d29c9 in <unknown> from /usr/lib/libgobject-2.0.so.0
 0x406d2736 in g_closure_invoke + 0xb6 from /usr/lib/libgobject-2.0.so.0
 0x406e3651 in <unknown> from /usr/lib/libgobject-2.0.so.0
 0x406e2e9c in g_signal_emit_valist + 0x73c
from /usr/lib/libgobject-2.0.so.0
 0x406e3216 in g_signal_emit_by_name + 0xe6
from /usr/lib/libgobject-2.0.so.0
 0x40a78ece in <unknown> from /usr/lib/libgtk-x11-2.0.so.0
 0x40a79248 in _gtk_size_group_compute_requisition + 0x68
from /usr/lib/libgtk-x11-2.0.so.0
 0x40b1c61c in gtk_widget_size_request + 0x4c
from /usr/lib/libgtk-x11-2.0.so.0
 0x409dbecf in <unknown> from /usr/lib/libgtk-x11-2.0.so.0
 0x409dbf65 in <unknown> from /usr/lib/libgtk-x11-2.0.so.0
 0x409d1818 in _gtk_file_chooser_embed_get_default_size + 0x78
from /usr/lib/libgtk-x11-2.0.so.0
 0x409d15d5 in <unknown> from /usr/lib/libgtk-x11-2.0.so.0
 0x409d1818 in _gtk_file_chooser_embed_get_default_size + 0x78
from /usr/lib/libgtk-x11-2.0.so.0
 0x409d0eec in <unknown> from /usr/lib/libgtk-x11-2.0.so.0
 0x406e42a6 in g_cclosure_marshal_VOID__VOID + 0x76
from /usr/lib/libgobject-2.0.so.0
 0x406d2736 in g_closure_invoke + 0xb6 from /usr/lib/libgobject-2.0.so.0
 0x406e3dcf in <unknown> from /usr/lib/libgobject-2.0.so.0
 0x406e2e9c in g_signal_emit_valist + 0x73c
from /usr/lib/libgobject-2.0.so.0
 0x406e3216 in g_signal_emit_by_name + 0xe6
from /usr/lib/libgobject-2.0.so.0
 0x409d16a9 in <unknown> from /usr/lib/libgtk-x11-2.0.so.0
 0x406e42a6 in g_cclosure_marshal_VOID__VOID + 0x76
from /usr/lib/libgobject-2.0.so.0
 0x406d2736 in g_closure_invoke + 0xb6 from /usr/lib/libgobject-2.0.so.0
 0x406e3dcf in <unknown> from /usr/lib/libgobject-2.0.so.0
 0x406e2e9c in g_signal_emit_valist + 0x73c
from /usr/lib/libgobject-2.0.so.0
 0x406e3216 in g_signal_emit_by_name + 0xe6
from /usr/lib/libgobject-2.0.so.0
 0x409d99e8 in <unknown> from /usr/lib/libgtk-x11-2.0.so.0
 0x406e4ca3 in g_cclosure_marshal_VOID__OBJECT + 0x83
from /usr/lib/libgobject-2.0.so.0
 0x406d29c9 in <unknown> from /usr/lib/libgobject-2.0.so.0
 0x406d2736 in g_closure_invoke + 0xb6 from /usr/lib/libgobject-2.0.so.0
 0x406e3651 in <unknown> from /usr/lib/libgobject-2.0.so.0
 0x406e2e9c in g_signal_emit_valist + 0x73c
from /usr/lib/libgobject-2.0.so.0
 0x406e3126 in g_signal_emit + 0x26 from /usr/lib/libgobject-2.0.so.0
 0x40b1fc7c in <unknown> from /usr/lib/libgtk-x11-2.0.so.0
 0x40b1f44a in <unknown> from /usr/lib/libgtk-x11-2.0.so.0
 0x40a78ea8 in <unknown> from /usr/lib/libgtk-x11-2.0.so.0
 0x40a79248 in _gtk_size_group_compute_requisition + 0x68
from /usr/lib/libgtk-x11-2.0.so.0
 0x40b1c61c in gtk_widget_size_request + 0x4c
from /usr/lib/libgtk-x11-2.0.so.0
 0x409dbecf in <unknown> from /usr/lib/libgtk-x11-2.0.so.0
 0x409dbf65 in <unknown> from /usr/lib/libgtk-x11-2.0.so.0
 0x409d1818 in _gtk_file_chooser_embed_get_default_size + 0x78
from /usr/lib/libgtk-x11-2.0.so.0
 0x409d15d5 in <unknown> from /usr/lib/libgtk-x11-2.0.so.0
 0x409d1818 in _gtk_file_chooser_embed_get_default_size + 0x78
from /usr/lib/libgtk-x11-2.0.so.0
Aborted
Thanks for answering my question
 cu 
 Eugen

Hello NG,
 I am building a GUI with wxPython+Matplotlib, using the WXAgg backend=
.
Basically, what I would like to do, is the following:
1) Having a series of points (x and y coordinates), plot these points (ob=
vious
;-) );
2) I would like to be able to interact with every single point in this se=
ries
(using the buttondown and buttonmotion functions of Matplotlib);
3) The interaction should include point selection (with some kind of "hig=
hlight"
when I select one or more point), point editing (move a point in the x or=
y direction using the mouse);
4) I would like to be able to plot an interpolation of the selected point=
s,
with a straight line (in a least squares sense), and then be able to inte=
ract
with this line (move it, delete it and so on).
Now, the question: Which is the best approach with Matplotlib for this ki=
nd
of interaction? Should I plot every point using plot(x1, y1), plot(x2, y2=
)
etc...? Or should I use Collections (i have no idea on what to do with co=
llections)?
Scattered plots? Does anyone have any suggestion/pointer for me? Some exa=
mples
of editing/interacting with plots?
Thanks for every suggestion.
Andrea.

Alan,
> 
> But I still feel something is missing from this discussion. 
> Would it be odd/hard for plot() to have an option that says, 
> effectively, mask NaNs so that the expected behavior results? 
Again, the problem is that automatic masking of nans would be easy with 
numarray but not at all easy with Numeric. Given that mpl is designed 
to work the same with numarray and Numeric, it is not easy to build good 
nan support into mpl. This will change when the successor to Numeric 
becomes common enough that support for old Numeric can be dropped, but 
not soon. In the meantime, if you want to use nans, you can do 
something like this:
 >>> import numarray as N
 >>> from numarray.ieeespecial import isnan, nan
 >>> import numarray.ma as ma
 >>> a = N.array([1, 2, nan, 3, 4])
 >>> b = ma.masked_where(isnan(a), a)
Now you can plot b and it will have a gap in the middle.
Eric

Not a big deal but ...
Would it not be natural for date2num to accept an rrule as 
an argument? I.e., why force us to make a list of an rrule?
fwiw,
Alan Isaac

>> x=[1,2,nan,4,5] plot(x) plots a single line. 
>> I expect two segments and a gap. 
On 2005年7月11日, Eric Firing apparently wrote: 
> Slightly modifying a reply to a similar question not long ago: 
> At present, you need to use masked arrays instead of NaN. 
So if I use masked arrays, 
I should get two segments and a gap in the above case? 
I'm not familiar with masked arrays. 
Sounds like I'll have to learn about them. 
But I still feel something is missing from this discussion. 
Would it be odd/hard for plot() to have an option that says, 
effectively, mask NaNs so that the expected behavior results? 
Thanks, 
Alan