There is one issue I spotted in this code. Although hard to notice from the
produced plot, only the latest grid is updated when set_ydata is called. So
a slight modification makes this code running correctly as originally
intended.
L1list = []
L2list = []
for i in range(nums): for j in range(xx*16
Thanks for the explanation! Let's discuss further on that issue page.
Michiel de Hoon writes:
> Hi Eric, Jouni,
>
> Thanks for your replies. I opened an issue here:
>
> https://github.com/matplotlib/matplotlib/issues/992
>
> and wrote an outline of how the PDF backend can be simplified by
> maki
idea to enter a Github ticket for this,
> referring to
> this email thread.
>
> Mike D. and Jouni S. have done most of the work on the pdf
> backend.
>
> Eric
>
> > Best,
> > -Michiel.
> >
> >
> >
> > --- On *Sat, 7/7/12, Gökhan Sever /
ead.
Mike D. and Jouni S. have done most of the work on the pdf backend.
Eric
> Best,
> -Michiel.
>
>
>
> --- On *Sat, 7/7/12, Gökhan Sever //* wrote:
>
>
> From: Gökhan Sever
> Subject: Re: [Matplotlib-users] Accelerating PDF saved plots
> To: &quo
Michiel de Hoon writes:
> I think it is not so bad, since it's mainly a matter of removing the
> stuff from the PDF backend that is no longer needed. Do we have a
> maintainer for the PDF backend? Because I would rather rely on him/her
> to make the changes to this backend.
That would be me. Ca
ime for it within this month.
Best,
-Michiel.
--- On Sat, 7/7/12, Gökhan Sever wrote:
From: Gökhan Sever
Subject: Re: [Matplotlib-users] Accelerating PDF saved plots
To: "Michiel de Hoon"
Cc: matplotlib-users@lists.sourceforge.net
Date: Saturday, July 7, 2012, 9:05 PM
Hi,
What kind
e same way to speed up these backends, as well as to
> reduce the output file sizes.
>
> Best,
> -Michiel.
>
> --- On *Thu, 7/5/12, Gökhan Sever * wrote:
>
>
> From: Gökhan Sever
> Subject: Re: [Matplotlib-users] Accelerating PDF saved plots
> To: "Benjamin Root
atplotlib-users] Accelerating PDF saved plots
To: "Benjamin Root"
Cc: matplotlib-users@lists.sourceforge.net
Date: Thursday, July 5, 2012, 2:11 PM
38 * 16 = 608
80 / 608 = 0.1316 seconds per plot
At this point, I doubt you are going to get much more speed-ups. Glad to be of
hel
On Thu, Jul 5, 2012 at 12:17 PM, Benjamin Root wrote:
>
> Actually, looking at Fabrice's code, you might be able to get it to be
> slightly faster. Lines 39-41 should be protected by a "if i == 0"
> statement because it only needs to be done once. Furthermore, you might
> get some more improvem
On Thu, Jul 5, 2012 at 1:55 PM, Gökhan Sever wrote:
> And you might get back more memory if you didn't have to have all the data
>> in memory at once, but that may or may not help you. The only other
>> suggestion I can make is to attempt to eliminate the overhead in the inner
>> loop. Essentia
>
>
>> 38 * 16 = 608
> 80 / 608 = 0.1316 seconds per plot
>
> At this point, I doubt you are going to get much more speed-ups. Glad to
> be of help!
>
> Fabrice -- Good suggestion! I should have thought of that given how much
> I use that technique in doing animation.
>
> Ben Root
>
>
I am includ
>
> And you might get back more memory if you didn't have to have all the data
> in memory at once, but that may or may not help you. The only other
> suggestion I can make is to attempt to eliminate the overhead in the inner
> loop. Essentially, I would try making a single figure and a single
>
On Thu, Jul 5, 2012 at 1:45 PM, Gökhan Sever wrote:
>
>
> On Thu, Jul 5, 2012 at 11:15 AM, Fabrice Silva wrote:
>
>>
>>
>> > At end of the outer loop, instead of closing the figure, you should
>> > call "remove()" for each plot element you made. Essentially, as you
>> > loop over the inner loop,
On Thu, Jul 5, 2012 at 11:15 AM, Fabrice Silva wrote:
>
>
> > At end of the outer loop, instead of closing the figure, you should
> > call "remove()" for each plot element you made. Essentially, as you
> > loop over the inner loop, save the output of the plot() call to a
> > list, and then when d
> At end of the outer loop, instead of closing the figure, you should
> call "remove()" for each plot element you made. Essentially, as you
> loop over the inner loop, save the output of the plot() call to a
> list, and then when done with those plots, pop each element of that
> list and call "r
On Thu, Jul 5, 2012 at 11:36 AM, Gökhan Sever wrote:
>
>
> On Thu, Jul 5, 2012 at 8:45 AM, Gökhan Sever wrote:
>
>> On Thu, Jul 5, 2012 at 7:29 AM, Benjamin Root wrote:
>>
>>>
>>>
>>> On Wed, Jul 4, 2012 at 1:17 PM, Gökhan Sever wrote:
>>>
Hello,
I am working on creating some dist
On Thu, Jul 5, 2012 at 8:45 AM, Gökhan Sever wrote:
> On Thu, Jul 5, 2012 at 7:29 AM, Benjamin Root wrote:
>
>>
>>
>> On Wed, Jul 4, 2012 at 1:17 PM, Gökhan Sever wrote:
>>
>>> Hello,
>>>
>>> I am working on creating some distribution plots to analyze cloud
>>> droplet and drop features. You ca
On Thu, Jul 5, 2012 at 7:29 AM, Benjamin Root wrote:
>
>
> On Wed, Jul 4, 2012 at 1:17 PM, Gökhan Sever wrote:
>
>> Hello,
>>
>> I am working on creating some distribution plots to analyze cloud droplet
>> and drop features. You can see one such plot at
>> http://atmos.uwyo.edu/~gsever/data/rf06
On Wed, Jul 4, 2012 at 1:17 PM, Gökhan Sever wrote:
> Hello,
>
> I am working on creating some distribution plots to analyze cloud droplet
> and drop features. You can see one such plot at
> http://atmos.uwyo.edu/~gsever/data/rf06_1second/rf06_belowcloud_SurfaceArea_1second.pdf
> This file conta
Your files do not seem to be readable:
http://atmos.uwyo.edu/~gsever/data/matplotlib/test_speed.py
http://atmos.uwyo.edu/~gsever/data/matplotlib/test_speed.pdf
Nicolas
On Jul 4, 2012, at 19:17 , Gökhan Sever wrote:
> Hello,
>
> I am working on creating some distribution plots to analyze cl
Hello,
I am working on creating some distribution plots to analyze cloud droplet
and drop features. You can see one such plot at
http://atmos.uwyo.edu/~gsever/data/rf06_1second/rf06_belowcloud_SurfaceArea_1second.pdf
This file contains 38 pages and each page has 16 panels created via
MPL's AxesGr
21 matches
Mail list logo
