matplotlib-users Mailing List for matplotlib

"John Hunter" <jd...@gm...> writes:

>> But this fails to plot the first rectange in the resulting plot. The
>> second, red rectangle is painted correctly in the resulting plot, but
>> the first one is totaly missing in the plot, leaving only a line in
>> the plot. Is there some kind of internal status that has to be
>> resettet in the actors?
>
> When you add an artist to the Axes, it checks to see if you have set a
> transformation.  If you haven't, it will set the default axes
> transformation.  If you have, it leaves the transformation unchanged.
> This is why you are seeing the problems you see.
>
> Before adding them to the second axes, you need to reset the
> transformation for each line, text, etc....
>
>
> for artist in ax.get_child_artists():
>    artist.set_transform(ax2.transData)
>    if isinstance(artist, Line2D):
>        ax2.add_line(artist)
>    elif ....
>
> should work....

It does. It helps me a lot, thank you.

Regards
Berthold
--=20
ber...@xn... / <http://h=C3=B6llmanns.de/>
bh...@we...                 / <http://starship.python.net/crew/bhoel/>

Hi,

> > I want to import binary files generated from C/FORTRAN into matplotlib for
> > plotting.
> > Can this be done using 'load'?
>
> If you are using SciPy, scipy.io has a few functions which may
> help. scipy.io.fromfile, for example.

Ah - just to be clear, for scipy 0.5.2, scipy.io.fromfile is in fact
numpy.fromfile - that was just a goofy import error on my part when
writing the matlab file loading routines.  For clarity, I think it is
best to pull this from the scipy.io namespace for the next release, so
please use numpy.fromfile for this.

Best,

Matthew

Hi all,

Is there a way to add the coordinates in text form to each plus in the
attached figure ?
ERach plus in the plot is generated by
plot([data[-1].real],[data[-1].imag],'k+')

For example the rightmost plus (in the upper right half plane) should
have a text (1.049+0.692j)
Can I use text for this purpose ?
 
Any pointer would be appreciated.

Thanks in advance
                                       Nils

Does anybody understand why CXX extensions don't pickle?
I have the same problem with my own CXX extensions, which I make with SWIG.
On the other hand, FORTRAN extensions using f2py pickle fine!
Mark

From: "John Hunter" <jd...@gm...>
> Subject: Re: [Matplotlib-users] Native file format
> To: "Edin Salkovic" <edi...@gm...>
> Cc: Jan Strube <cur...@gm...>,
>         mat...@li..., Eric Firing
>         <ef...@ha...>
> Message-ID:
>         <88e...@ma...>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> On 2/7/07, Edin Salkovic <edi...@gm...> wrote:
>
> > Why can't mpl's figures be pickled?
>
> The main thing is we need to add pickle support for all of mpl's extension
> code
>
>   http://docs.python.org/lib/node321.html
>
> In earlier attempts people got stuck with trying to pickle the
> CXX extension code, which was causing some problems, but these
> problems may be fixed in more recent versions of CXX.  Todd Miller was
> the last person to look at this in some detail, I think.
>
> Other hinderances may come from the GUI layer, since figures store
> pointers to their canvases which in some cases come from GUI extension
> code that may not support pickling.  But we can fairly easy decouple
> the figure from the canvas at pickle time and deal with pure mpl,
> numpy and python objects.  The main work is to add pickle
> serialization to the mpl extension code.
>

Angus McMorland wrote:
> Hi all,
> 
> Did any progress get made beyond this discussion below? I'm trying to
> get contourf3D working, using latest svn, and it still seems to be
> out-of-order. Contour3D works, but I get exactly the same errors (and
> went exactly the same route trying to fix them) as Matthew.
> 
> On 13/01/07, Eric Firing <ef...@ha...> wrote:
>> I don't know if everything 3D works, but the first error you note below
> 
> Which one is supposed to be the 'first' error mentioned here? In my
> latest svn checkout, the line:
> 
> levels, colls = self.contourf(X, Y, Z, 20)
> 
> still appears to be present.
> 
>> is fixed in svn, and I suspect in 0.87.7, the last release.  0.87.5 is
>> rather old--quite a bit has changed between minor releases.

Aha!  What is fixed is the corresponding error in contour3D--but 
strangely, the same error in contourf3D was never fixed.  I took a stab 
at it just now but failed--there is more wrong with it than this simple 
error--so I made it raise NotImplementedError.  I don't know whether 
contourf3D ever *did* work.  Nor am I sure exactly what it should do if 
it worked. The problem is that no one has taken on the maintenance of 
the 3D plotting.

Eric

Hi all,

Did any progress get made beyond this discussion below? I'm trying to
get contourf3D working, using latest svn, and it still seems to be
out-of-order. Contour3D works, but I get exactly the same errors (and
went exactly the same route trying to fix them) as Matthew.

On 13/01/07, Eric Firing <ef...@ha...> wrote:
> I don't know if everything 3D works, but the first error you note below

Which one is supposed to be the 'first' error mentioned here? In my
latest svn checkout, the line:

levels, colls = self.contourf(X, Y, Z, 20)

still appears to be present.

> is fixed in svn, and I suspect in 0.87.7, the last release.  0.87.5 is
> rather old--quite a bit has changed between minor releases.
>
> Eric
>
> Matthew Koichi Grimes wrote:
> > contourf3D and contour3D seem to be broken in my copy of matplotlib
> > 0.87.5 that I installed from ubuntu edgy's repositories. Is this a known
> > problem? I started going through axes3d.py etc and fixing the reported
> > errors, but the error trail seems to go pretty deep across multiple
> > files. Now I'm wondering if maybe this is something major that has
> > already been fixed by more experienced hands in SVN or something.
> >
> > In the off chance that this is an unknown problem, I've enumerated the
> > errors below. These all happened while attempting to run the example
> > code in http://www.scipy.org/Cookbook/Matplotlib/mplot3D
> >
> > If it's fixed in SVN, I'll try installing that, but I haven't seen this
> > bug mentioned in matplotlib's bug list on sourceforge.net.
> >
> > -- Matt
> >
> > When I called contourf3D the first time, I got the following error:
> >
> > <snip>
> > File "/usr/lib/python2.4/site-packages/matplotlib/axes3d.py", line 596,
> > in contourf3D
> >     levels, colls = self.contourf(X, Y, Z, 20)
> > TypeError: unpack non-sequence
> > </snip>
> >
> > As suggested in the examples page above, I went into contourf3D's
> > function definition in axes3d.py and replaced:
> >
> >     levels, colls = self.contourf(X, Y, Z, 20)
> >
> > with
> >
> >     C = self.contourf(X, Y, Z, *args, **kwargs)
> >     levels, colls = (C.levels, C.collections)
> >
> > I then got a new error when calling contourf3D:
> >
> > <snip>
> > exceptions.NameError                                 Traceback (most
> > recent call last)
> >
> > /home/mkg/Desktop/<ipython console>
> >
> > /usr/lib/python2.4/site-packages/matplotlib/axes3d.py in
> > contourf3D(self, X, Y, Z, *args, **kwargs)
> >     604             zs = [z1] * (len(linec._verts[0])/2)
> >     605             zs += [z2] * (len(linec._verts[0])/2)
> > --> 606             art3d.wrap_patch(linec, zs, fn=draw_polyc)
> >     607         self.auto_scale_xyz(X,Y,Z, had_data)
> >     608         return levels,colls
> >
> > NameError: global name 'draw_polyc' is not defined
> > </snip>
> >
> > After changing draw_polyc to art3d.draw_polyc, it complained that
> > art3d.wrap_patch in fact only takes two arguments. So I changed
> >
> >     art3d.wrap_patch(linec, zs, fn=draw_polyc)
> >
> > to
> >
> >     art3d.wrap_patch(linec, zs)
> >
> > Which led to the latest error message:
> >
> > <snip>
> > Traceback (most recent call last):
> >   File
> > "/usr/lib/python2.4/site-packages/matplotlib/backends/backend_gtk.py",
> > line 284, in expose_event
> >     self._render_figure(self._pixmap, w, h)
> >   File
> > "/usr/lib/python2.4/site-packages/matplotlib/backends/backend_gtkagg.py",
> > line 73, in _render_figure
> >     FigureCanvasAgg.draw(self)
> >   File
> > "/usr/lib/python2.4/site-packages/matplotlib/backends/backend_agg.py",
> > line 391, in draw
> >     self.figure.draw(renderer)
> >   File "/usr/lib/python2.4/site-packages/matplotlib/figure.py", line
> > 538, in draw
> >     for a in self.axes: a.draw(renderer)
> >   File "/usr/lib/python2.4/site-packages/matplotlib/axes3d.py", line
> > 172, in draw
> >     Axes.draw(self, renderer)
> >   File "/usr/lib/python2.4/site-packages/matplotlib/axes.py", line 1057,
> > in draw
> >     a.draw(renderer)
> >   File "/usr/lib/python2.4/site-packages/matplotlib/art3d.py", line 56,
> > in call_draw3d
> >     self.draw3d(renderer)
> >   File "/usr/lib/python2.4/site-packages/matplotlib/art3d.py", line 184,
> > in draw3d
> >     xs,ys = zip(*self._offsets)
> > TypeError: zip() argument after * must be a sequence
> > </snip>
> >
> > Contour3D (not contourf3D) does work in that it successfully displays a
> > plot, but when I mouseover this plot, my python console fills with the
> > following error message (one repetition for each mouse event):
> >
> > <snip>
> > /usr/lib/python2.4/site-packages/matplotlib/backends/backend_gtk.py in
> > motion_notify_event(self, widget, event)
> >     178         # flipy so y=0 is bottom of canvas
> >     179         y = self.allocation.height - y
> > --> 180         FigureCanvasBase.motion_notify_event(self, x, y)
> >     181         return False  # finish event propagation?
> >     182
> >
> > /usr/lib/python2.4/site-packages/matplotlib/backend_bases.py in
> > motion_notify_event(self, x, y, guiEvent)
> >     885         event = MouseEvent('motion_notify_event', self, x, y,
> > self._button, self._key, guiEvent=guiEvent)
> >     886         for func in self.callbacks.get('motion_notify_event',
> > {}).values():
> > --> 887             func(event)
> >     888
> >     889     def draw(self, *args, **kwargs):
> >
> > /usr/lib/python2.4/site-packages/matplotlib/axes3d.py in on_move(self,
> > event)
> >     396         """
> >     397         #NOTE - this shouldn't be called before the graph has
> > been drawn for the first time!
> > --> 398         if event.inaxes != self or not self.M:
> >     399             return
> >     400         #
> >
> > ValueError: The truth value of an array with more than one element is
> > ambiguous. Use a.any() or a.all()
> > </snip>
-- 
AJC McMorland, PhD Student
Physiology, University of Auckland