On Sat, Jan 10, 2009 at 2:49 PM, Darren Dale wrote:
>> Never had any luck getting a tester, so I went ahead and committed
>> this to the trunk. I should probably get a working qt backend for
>> testing on one of the machines I use
>
> I'm sorry John, I didnt see your original request for tes
On Sat, Jan 10, 2009 at 3:09 PM, John Hunter wrote:
> On Tue, Dec 30, 2008 at 10:57 AM, John Hunter wrote:
> > On Fri, Dec 26, 2008 at 8:40 AM, Michiel de Hoon
> wrote:
> >
> >> I have written such a function for the qt4 backend; see patch #2468809
> at
> >>
> >>
> https://sourceforge.net/track
On Tue, Dec 30, 2008 at 10:57 AM, John Hunter wrote:
> On Fri, Dec 26, 2008 at 8:40 AM, Michiel de Hoon wrote:
>
>> I have written such a function for the qt4 backend; see patch #2468809 at
>>
>> https://sourceforge.net/tracker/index.php?func=detail&aid=2468809&group_id=80706&atid=560722
>>
>> I
On Fri, Dec 26, 2008 at 8:40 AM, Michiel de Hoon wrote:
> I have written such a function for the qt4 backend; see patch #2468809 at
>
> https://sourceforge.net/tracker/index.php?func=detail&aid=2468809&group_id=80706&atid=560722
>
> I am not a big qt4 user, so it would be good if somebody else co
> This seems like a reasonable change and I have added it to
> the trunk.
> It would be nice to get a canvas.draw_idle on the qt
> backend, so
> perhaps Darren you can add this to your list if you get
> some free
> time.
>
I have written such a function for the qt4 backend; see patch #2468809 at
On Fri, Dec 19, 2008 at 9:07 AM, Paul Kienzle wrote:
>> Interactive is not the best word, but it is the rc parameter meaning
>> "you are using mpl from the interactive prompt and want every pyplot
>> command to update the plot". If the macosx backend is not doing this
>> it should. If tkagg is
> The interactive backends (wx, tk, gtk) all handle draw_idle
> in a way which delays the drawing until there are no
> more commands to run.
>
> By changing draw_if_interactive to use draw_idle instead of
> draw,
> wouldn't this automatically smooth over the performance
> issues without
> the user
> Could you post the script you are using to do the
> profiling?
This is the code that I was using
from pylab import *
import numpy
figure()
x=numpy.arange(20)
y=1+x**2
n = 4
for i in range(n*n):
subplot(n,n,i+1)
bar(x,y,log=True)
xlim(-5,25)
ylim(1,1e4)
> The call to subplot/
On Dec 19, 2008, at 7:52 AM, John Hunter wrote:
> Could you post the script you are using to do the profiling? The call
> to subplot/plot/bar should not trigger a draw, unless "interactive" is
> set to True
>
> http://matplotlib.sourceforge.net/users/shell.html
>
> Interactive is not the best
On Fri, Dec 19, 2008 at 2:20 AM, Michiel de Hoon wrote:
>> This looks great -- in particular I am intrigued by the
>> final timing results which show your backend 12 times
>> faster than tkagg. I am not sure where this speedup is
>> coming from -- do you have some ideas?
>
> In this example, I am
> This looks great -- in particular I am intrigued by the
> final timing results which show your backend 12 times
> faster than tkagg. I am not sure where this speedup is
> coming from -- do you have some ideas?
In this example, I am drawing 16 subplots in a 4x4 grid. With Tkagg, I am
noticing t
Hi Michiel,
+1 to Chris Barker's request for information on where Agg makes extra
calls to draw(). The 20% speedup in scatter performance is nice, and
is clearly related to Agg.
Any idea why the pcolormesh example is so much slower in Mac OS X than TkAgg?
Thanks for your continued work on this.
John Hunter wrote:
> Hi Michiel,
>
> This looks great -- in particular I am intrigued by the final timing
> results which show your backend 12 times faster than tkagg. I am not
> sure where this speedup is coming from -- do you have some ideas?
> Because you are creating lots-o-subplots in that e
Hi Michiel,
This looks great -- in particular I am intrigued by the final timing
results which show your backend 12 times faster than tkagg. I am not
sure where this speedup is coming from -- do you have some ideas?
Because you are creating lots-o-subplots in that example, there is a
lot of overh
Dear all,
I have now implemented the draw_path_collection, draw_quad_mesh, and
draw_markers methods in the Mac OS X native backend (see patch 2179017 at
http://sourceforge.net/tracker/?func=detail&atid=560722&aid=2179017&group_id=80706).
Some timings are below. In terms of raw drawing speed, the
Michiel de Hoon wrote:
> --- On Tue, 10/28/08, Christopher Barker <[EMAIL PROTECTED]>
> wrote:
>> I'm still curious where all this speed comes from.
> At this point, most of it is coming from having complete control over
> the event loop, which allows to avoid superfluous calls to draw().
well, w
--- On Tue, 10/28/08, John Hunter <[EMAIL PROTECTED]> wrote:
> I haven't had a chance to look at the code yet, but I
> suspect he
> hasn't implemented the path collection draw method. If
> it's not
> implemented, we fall back on drawing each path separately,
> which is a
> lot slower. scatter ulti
--- On Tue, 10/28/08, Christopher Barker <[EMAIL PROTECTED]> wrote:
> > 4) One drawback compared to the existing cocoa-agg
> >backend is that the latter allows easy integration
> >of matplotlib into a larger cocoa application,
> >whereas my backend only cares about matplotlib.
>
...
On Tue, Oct 28, 2008 at 12:24 PM, Eric Bruning <[EMAIL PROTECTED]> wrote:
> Nice work ... and an ambitious effort.
>
> I've gotten it running, and am a bit perplexed by some of the
> performance I'm seeing. Specifically, the following bit takes well
> over twice as long to run as does WxAgg. Does t
Nice work ... and an ambitious effort.
I've gotten it running, and am a bit perplexed by some of the
performance I'm seeing. Specifically, the following bit takes well
over twice as long to run as does WxAgg. Does this align with others'
testing?
The only difference I detect is that the Mac backe
Michiel de Hoon wrote:
> I wrote a backend for matplotlib on Mac OS X. This is a native
> backend for Mac OS X
very nice!
> 4) One drawback compared to the existing cocoa-agg backend is that
> the latter allows easy integration of matplotlib into a larger cocoa
> application, whereas my backend o
21 matches
Mail list logo
