> Or are you effectively doing a scatter plot? Could you use scatter?
>
> Eric
>
Yes, I've already tried doing the trick with a scatter plot, but since the
filling colors correspond to a "physical quantity" and the radius of the
scatters are the "real" circle radius, using RegularPolygons is
John Hunter wrote:
> On Sun, Jun 15, 2008 at 7:48 AM, sidimok <[EMAIL PROTECTED]> wrote:
>
>> The code above was working for me as a charm, but since the new matlplotlib
>> flavor 0.98, I'm getting this error message:
>>
AttributeError: 'CirclePolygon' object has no attribute 'get_verts' <<
>
On Sun, Jun 15, 2008 at 7:48 AM, sidimok <[EMAIL PROTECTED]> wrote:
> The code above was working for me as a charm, but since the new matlplotlib
> flavor 0.98, I'm getting this error message:
>
>>> AttributeError: 'CirclePolygon' object has no attribute 'get_verts' <<
>
> Any idea?
The new patch
There was recently a post on Radar/Spider plotting
(http://sourceforge.net/mailarchive/message.php?msg_id=4845303A.9050204%40epcc.ed.ac.uk).
I too am interested in creating Radar plots with matplot. Is there a
simple way to do this?
Thanks,
Curtis
I realize this is way outdated now, but I came across the same
problem. My imshow command would display fine in the
xwindow and all plotting devices except for .ps. Taking the advice
you guys gave, I tracked it down
to pdftops in the backends.ps.py file. I changed the command from:
command = '
Hi everyone,
The code below was working for me as a charm, but since the new matlplotlib
flavor 0.98, I'm getting this error message:
>> AttributeError: 'CirclePolygon' object has no attribute 'get_verts' <<
Any idea?
- - - - - - - - - - - - - - - - - - -
import matplotlib
from matplotli
import matplotlib
from matplotlib.patches import CirclePolygon
from matplotlib.collections import PolyCollection
import pylab
fig=pylab.figure()
ax=fig.add_subplot(111)
resolution = 50 # the number of vertices
N = 20
x = pylab.rand(N)
y = pylab.rand(N)
radii = 0.1*pylab.rand(N
Eric Firing wrote:
> Michael Droettboom wrote:
>> As a quick-fix workaround, you can do:
>>
>> from matplotlib.pyplot import *
>> p = scatter([0,1,2,3], [4,5,6,7], c ='k', alpha=0, edgecolor = 'k')
>> p._alpha = 1.0
>> p.set_edgecolor('k')
>> show()
>>
>> But the deeper question is for the rest of
Michael Droettboom wrote:
> Thanks. I had seen these threads already -- I was hoping you had some
> more.
sorry :-(
> It also is different from what I was talking about in the sense of
> clipping. The effect I see is that when an explicit clipping rectangle
> is applied (e.g. the axes), spee
Michael Droettboom wrote:
> As a quick-fix workaround, you can do:
>
> from matplotlib.pyplot import *
> p = scatter([0,1,2,3], [4,5,6,7], c ='k', alpha=0, edgecolor = 'k')
> p._alpha = 1.0
> p.set_edgecolor('k')
> show()
>
> But the deeper question is for the rest of the list is... what's the
>
As a quick-fix workaround, you can do:
from matplotlib.pyplot import *
p = scatter([0,1,2,3], [4,5,6,7], c ='k', alpha=0, edgecolor = 'k')
p._alpha = 1.0
p.set_edgecolor('k')
show()
But the deeper question is for the rest of the list is... what's the
correct behavior? Should we just revert to w
Christopher Barker wrote:
> Michael Droettboom wrote:
>
>> Christopher Barker wrote:
>>
> A number of threads on the wxPython list. Here's a couple:
>
> http://aspn.activestate.com/ASPN/Mail/Message/wxpython-users/3519845
>
Thanks. I had seen these threads already -- I was hoping you ha
Michael Droettboom wrote:
> Christopher Barker wrote:
>> For what it's worth, apparently you can speed up GraphicsContext code
>> substantially if you use it right --
> Can you be more specific about this
no. I haven't done much with it myself.
> or provide a reference?
A number of threads
Christopher Barker wrote:
> Michael Droettboom wrote:
>
>> If you're using 0.98.x with the wx backend, things are *very* slow. The
>> performance of wx.GraphicsContext (that is uses under the hood) is
>> terrible.
>>
>
> For what it's worth, apparently you can speed up GraphicsContext c
Michael Droettboom wrote:
> If you're using 0.98.x with the wx backend, things are *very* slow. The
> performance of wx.GraphicsContext (that is uses under the hood) is
> terrible.
For what it's worth, apparently you can speed up GraphicsContext code
substantially if you use it right -- i.e.
There seems to have been a change to the behavior of the 'alpha' keyword option
to scatter(): where previously alpha only affected the facecolor, and the
edgecolor always had an alpha of 1.0, alpha now seems to affect both facecolor
and edgecolor. Tested with 0.93.1 and 0.98. Tested with new A
Quoting Fabrice Silva:
> Using version 0.91.2, I do not manage to push ticks labels to
> the right side of the axis, keeping ticks lines on both
> sides. How can I do it ?
One solution is
yax = gca().yaxis
yax.set_ticks_position('right')
# labels right side; removes left ticks
On Sun, Jun 15, 2008 at 3:50 PM, Dan Murphy <[EMAIL PROTECTED]> wrote:
> Moving (finally) to the matplotlib step. I had previously downloaded
> wxPython2.8. My ubuntu-knowledgeable son helped me with the configure and
> make install part or your instructions and everything now works fine: numpy
> w
Are you using the wxAgg backend or just wx? Which version of matplotlib?
If you're using 0.98.x with the wx backend, things are *very* slow. The
performance of wx.GraphicsContext (that is uses under the hood) is
terrible. You may want to try switching to the WxAgg backend, which,
among other
Dear all,
I have been using the WXAgg backend with matplotlib and have been
coming across an occasional error. Unfortunately, it is a little
difficult to trap as it doesn't happen every time! Running on Windows
with python 2.5.2, matplotlib 0.98.0 (installed from the binary) and
wx version 2.8.7
I have developed a wxPython GUI that uses matplotlib to plot line traces
(using plot()). If I were to plot about 250,000 data points, it takes
nearly 1 minute to load the plot (using a intel dual core), although once
this plot is loaded, it is easy to interact with it - changing the x/y scale
& sc
21 matches
Mail list logo
