matplotlib-devel Mailing List for matplotlib (Page 4)

Hello,
for the Debian package, we install sample_data directory in a custom
location, /usr/share/matplotlib/sample_data/ .
Pre-1.2.0 we could specify the examples.directory rcParam, but now
that parameter has been removed.
If we want to keep shipping sample_data in /usr/share/matplotlib/ , it
seems the only solution is to patch cbook.get_sample_data() to set
root = '/usr/share/matplotlib/'
Is that correct or is there another solution i'm not seeing?
Regards,
--
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi

On Thu, Nov 8, 2012 at 6:14 PM, Mark Lawrence <bre...@ya...> wrote:
> On 08/11/2012 17:18, Michael Droettboom wrote:
>> Thanks again to everyone for all of their hard work.
>
> Yep. And a fantastic memorial in its own right to the late John Hunter.
>
>>
>> As per the usual drill, once we have the binaries up, I'll make an ANN
>> on matplotlib-users.
>
> IIRC matplotlib is currently third in the list of libraries most wanted
> by users waiting for Python3 compatibility. I'd guess that many
> scientific users are aware of this wonderful milestone, but to spread
> the news at a minimum I'd put this on the main Python mailing list and
+1 for this
> on Python announce. Or does that happen anyway, and I'd simply
> forgotten about it?
>
>>
>> The documentation is currently being rebuilt, and the default for
>> matplotlib.org will update to 1.2.0 around the same time as that
>> announcement.
>>
>> Mike
>>
>> ------------------------------------------------------------------------------
>> Everyone hates slow websites. So do we.
>> Make your web apps faster with AppDynamics
>> Download AppDynamics Lite for free today:
>> http://p.sf.net/sfu/appdyn_d2d_nov
>>
>
> --
> Cheers.
>
> Mark Lawrence.
>
>
> ------------------------------------------------------------------------------
> Everyone hates slow websites. So do we.
> Make your web apps faster with AppDynamics
> Download AppDynamics Lite for free today:
> http://p.sf.net/sfu/appdyn_d2d_nov
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
-- 
Damon McDougall
http://www.damon-is-a-geek.com
Institute for Computational Engineering Sciences
201 E. 24th St.
Stop C0200
The University of Texas at Austin
Austin, TX 78712-1229

---------- Forwarded message ----------
From: Damon McDougall <dam...@gm...>
Date: Thu, Nov 8, 2012 at 6:16 PM
Subject: Re: [matplotlib-devel] 1.2.0 Final tagged and uploaded
To: "Russell E. Owen" <ro...@uw...>
On Thu, Nov 8, 2012 at 5:52 PM, Russell E. Owen <ro...@uw...> wrote:
> In article <509...@st...>,
> Michael Droettboom <md...@st...>
> wrote:
>
>> Thanks again to everyone for all of their hard work. This release has
>> been tagged and uploaded.
>>
>> As per the usual drill, once we have the binaries up, I'll make an ANN
>> on matplotlib-users.
>>
>> The documentation is currently being rebuilt, and the default for
>> matplotlib.org will update to 1.2.0 around the same time as that
>> announcement.
>>
>> Mike
>
> Congratulations!
>
> It looks like the binaries are all there (I uploaded the Mac binaries
> and found the Windows binaries already present).
Was waiting for your OK on this Russell. Glad to know they're building
fine. Good work.
--
Damon McDougall
http://www.damon-is-a-geek.com
Institute for Computational Engineering Sciences
201 E. 24th St.
Stop C0200
The University of Texas at Austin
Austin, TX 78712-1229
Forgot to include everybody else.
-- 
Damon McDougall
http://www.damon-is-a-geek.com
Institute for Computational Engineering Sciences
201 E. 24th St.
Stop C0200
The University of Texas at Austin
Austin, TX 78712-1229

On 08/11/2012 17:18, Michael Droettboom wrote:
> Thanks again to everyone for all of their hard work.
Yep. And a fantastic memorial in its own right to the late John Hunter.
>
> As per the usual drill, once we have the binaries up, I'll make an ANN
> on matplotlib-users.
IIRC matplotlib is currently third in the list of libraries most wanted 
by users waiting for Python3 compatibility. I'd guess that many 
scientific users are aware of this wonderful milestone, but to spread 
the news at a minimum I'd put this on the main Python mailing list and 
on Python announce. Or does that happen anyway, and I'd simply 
forgotten about it?
>
> The documentation is currently being rebuilt, and the default for
> matplotlib.org will update to 1.2.0 around the same time as that
> announcement.
>
> Mike
>
> ------------------------------------------------------------------------------
> Everyone hates slow websites. So do we.
> Make your web apps faster with AppDynamics
> Download AppDynamics Lite for free today:
> http://p.sf.net/sfu/appdyn_d2d_nov
>
-- 
Cheers.
Mark Lawrence.

Hello,
I noticed that a program I had that uses canvas.blit() to do animated graphs 
with the gtkagg backend was leaking memory.
I tracked this down to gtk gc's being allocated in agg_to_gtk_drawable with 
gdk_gc_new(), but never being destroyed.
The leak can be seen using the 'Animating selected plot elements' example 
from:
http://www.scipy.org/Cookbook/Matplotlib/Animations
(if it is modified to run forever, rather than just 50 plots and also 
changing numerix to numpy). After a few minutes, it is clear from ps that the 
memory usage is slowly but steadily climbing.
Patch below (against matplotlib-1.1.1.) fixes it.
Carl
--- _gtkagg.cpp~ 2012年06月30日 12:37:00.000000000 -0700
+++ _gtkagg.cpp 2012年11月08日 14:30:23.000000000 -0800
@@ -121,6 +121,7 @@
 destbuffer,
 deststride);
+ gdk_gc_destroy(gc);
 if (needfree)
 {
 delete [] destbuffer;

In article <509...@st...>,
 Michael Droettboom <md...@st...> 
 wrote:
> Thanks again to everyone for all of their hard work. This release has 
> been tagged and uploaded.
> 
> As per the usual drill, once we have the binaries up, I'll make an ANN 
> on matplotlib-users.
> 
> The documentation is currently being rebuilt, and the default for 
> matplotlib.org will update to 1.2.0 around the same time as that 
> announcement.
> 
> Mike
Congratulations!
It looks like the binaries are all there (I uploaded the Mac binaries 
and found the Windows binaries already present).
-- Russell

Thanks again to everyone for all of their hard work. This release has 
been tagged and uploaded.
As per the usual drill, once we have the binaries up, I'll make an ANN 
on matplotlib-users.
The documentation is currently being rebuilt, and the default for 
matplotlib.org will update to 1.2.0 around the same time as that 
announcement.
Mike

This will be addressed when I update the docs to 1.2.0 shortly.
Mike
On 11/08/2012 11:31 AM, Benjamin Root wrote:
> And I had completely missed that this was taken care of yesterday. 
> However, the changelog link from the what's new page is still dead.
>
> Ben
>
> On Thu, Nov 8, 2012 at 11:24 AM, Benjamin Root <ben...@ou... 
> <mailto:ben...@ou...>> wrote:
>
> There is a link to the CHANGELOG (are we even keeping that up to
> date anymore?) on the main page that is dead.
>
> Ben Root
>
>
>
>
> ------------------------------------------------------------------------------
> Everyone hates slow websites. So do we.
> Make your web apps faster with AppDynamics
> Download AppDynamics Lite for free today:
> http://p.sf.net/sfu/appdyn_d2d_nov
>
>
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

It's actually better to create these issues against the main matplotlib 
repository since all of the bugs are fixed over there in the source. 
matplotlib.github.com only contains generated files.
Mike
On 11/08/2012 11:50 AM, Phil Elson wrote:
> To raise (built) documentation based problems, I have been creating 
> issues in https://github.com/matplotlib/matplotlib.github.com .
> That seems to work well, but sadly, it always seems to be Michael that 
> ends up sorting it out... he is a victim of his own success (and 
> speed) ;-)
>
>
> On 8 November 2012 16:31, Benjamin Root <ben...@ou... 
> <mailto:ben...@ou...>> wrote:
>
> And I had completely missed that this was taken care of
> yesterday. However, the changelog link from the what's new page
> is still dead.
>
> Ben
>
>
> On Thu, Nov 8, 2012 at 11:24 AM, Benjamin Root <ben...@ou...
> <mailto:ben...@ou...>> wrote:
>
> There is a link to the CHANGELOG (are we even keeping that up
> to date anymore?) on the main page that is dead.
>
> Ben Root
>
>
>
> ------------------------------------------------------------------------------
> Everyone hates slow websites. So do we.
> Make your web apps faster with AppDynamics
> Download AppDynamics Lite for free today:
> http://p.sf.net/sfu/appdyn_d2d_nov
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> <mailto:Mat...@li...>
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>
>
>
>
> ------------------------------------------------------------------------------
> Everyone hates slow websites. So do we.
> Make your web apps faster with AppDynamics
> Download AppDynamics Lite for free today:
> http://p.sf.net/sfu/appdyn_d2d_nov
>
>
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

To raise (built) documentation based problems, I have been creating issues
in https://github.com/matplotlib/matplotlib.github.com .
That seems to work well, but sadly, it always seems to be Michael that ends
up sorting it out... he is a victim of his own success (and speed) ;-)
On 8 November 2012 16:31, Benjamin Root <ben...@ou...> wrote:
> And I had completely missed that this was taken care of yesterday.
> However, the changelog link from the what's new page is still dead.
>
> Ben
>
>
> On Thu, Nov 8, 2012 at 11:24 AM, Benjamin Root <ben...@ou...> wrote:
>
>> There is a link to the CHANGELOG (are we even keeping that up to date
>> anymore?) on the main page that is dead.
>>
>> Ben Root
>>
>
>
>
> ------------------------------------------------------------------------------
> Everyone hates slow websites. So do we.
> Make your web apps faster with AppDynamics
> Download AppDynamics Lite for free today:
> http://p.sf.net/sfu/appdyn_d2d_nov
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>
>

And I had completely missed that this was taken care of yesterday.
However, the changelog link from the what's new page is still dead.
Ben
On Thu, Nov 8, 2012 at 11:24 AM, Benjamin Root <ben...@ou...> wrote:
> There is a link to the CHANGELOG (are we even keeping that up to date
> anymore?) on the main page that is dead.
>
> Ben Root
>

There is a link to the CHANGELOG (are we even keeping that up to date
anymore?) on the main page that is dead.
Ben Root

See
https://github.com/matplotlib/matplotlib/pull/1463
Mike
On 11/08/2012 03:06 AM, Jens Nielsen wrote:
>
> I just noticed a small documentation issue yesterday. This table does 
> not include the
> gtk3 backend 
> http://matplotlib.org/1.2.0/faq/usage_faq.html#what-is-a-backend
>
> Should we update the table to include the gtk3 backend? (and note that 
> the qt3 backend is depreciated)
>
> Jens
>
>
>
> On Thu, Nov 8, 2012 at 3:23 AM, Michael Droettboom <md...@st... 
> <mailto:md...@st...>> wrote:
>
> The milestone is clear. Is there anything we're missing?
>
> If not, I plan to cut a final release and update the documentation
> website tomorrow morning.
>
> Mike
>
> ------------------------------------------------------------------------------
> Everyone hates slow websites. So do we.
> Make your web apps faster with AppDynamics
> Download AppDynamics Lite for free today:
> http://p.sf.net/sfu/appdyn_d2d_nov
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> <mailto:Mat...@li...>
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>
>
>
>
> ------------------------------------------------------------------------------
> Everyone hates slow websites. So do we.
> Make your web apps faster with AppDynamics
> Download AppDynamics Lite for free today:
> http://p.sf.net/sfu/appdyn_d2d_nov
>
>
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

While I think Paul's contribution in #1462 is great, I'd prefer to not 
put this in 1.2.0. There just isn't enough time to review such a large 
patch this late in the game. As our experience with Nelle's valuable 
PEP8 work shows, it's still possible to slip in accidental breakage even 
when making mostly mechanical changes. I'm fine with it going on the 
1.2.x branch after the release, however, so it would be in 1.2.1 (if we 
do one), so there's no need to change the PR target etc. at this point 
-- I'll just add a note that we don't want it to be merged until after 
1.2.0 has been tagged.
Mike
On 11/08/2012 05:38 AM, Phil Elson wrote:
> Just closed the PR which proposes this change against master (in 
> favour of the one against v1.2.x).
>
> It is very late in the day to be making so many example changes 
> (especially as we don't have tests for them).
> Personally, the balance between the risks vs the benefits doesn't give 
> me much indication of which way to go (I guess that is partly because 
> I don't actually prefer the plt.subplots() interface in some 
> situations). I guess that is a debate for inside the PR 
> (https://github.com/matplotlib/matplotlib/pull/1462).
>
> Cheers,
>
>
>
>
> On 8 November 2012 09:22, Paul Ivanov <piv...@gm... 
> <mailto:piv...@gm...>> wrote:
>
> On Wed, Nov 7, 2012 at 6:23 PM, Michael Droettboom
> <md...@st... <mailto:md...@st...>> wrote:
> > The milestone is clear. Is there anything we're missing?
> >
> > If not, I plan to cut a final release and update the documentation
> > website tomorrow morning.
>
> I just submitted #1462 against v1.2.x, (which is also pending as #1458
> against master).
>
> "use plt.subplots() in examples as much as possible"
>
> replaces a whole bunch of example code like this:
>
> fig = plt.figure()
> ax = plt.subplot(111) # or plt.add_subplot(111)
>
> to be just this:
>
> fig, ax = plt.subplots()
>
> This is a docs-only update - but I think it'll be worthwhile to start
> to give a more sensible way of creating figures and axes in one call
> for our the folks who'll be looking at matplotlib with fresh eyes
> after the 1.2 release.
>
> But I totally understand if folks feel this is too big of a pill to
> swallow this late in the game.
>
> go, team, go!
> --
> Paul Ivanov
> 314 address only used for lists, off-list direct email at:
> http://pirsquared.org | GPG/PGP key id: 0x0F3E28F7
>
> ------------------------------------------------------------------------------
> Everyone hates slow websites. So do we.
> Make your web apps faster with AppDynamics
> Download AppDynamics Lite for free today:
> http://p.sf.net/sfu/appdyn_d2d_nov
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> <mailto:Mat...@li...>
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>
>
>
>
> ------------------------------------------------------------------------------
> Everyone hates slow websites. So do we.
> Make your web apps faster with AppDynamics
> Download AppDynamics Lite for free today:
> http://p.sf.net/sfu/appdyn_d2d_nov
>
>
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

Just closed the PR which proposes this change against master (in favour of
the one against v1.2.x).
It is very late in the day to be making so many example changes (especially
as we don't have tests for them).
Personally, the balance between the risks vs the benefits doesn't give me
much indication of which way to go (I guess that is partly because I don't
actually prefer the plt.subplots() interface in some situations). I guess
that is a debate for inside the PR (
https://github.com/matplotlib/matplotlib/pull/1462).
Cheers,
On 8 November 2012 09:22, Paul Ivanov <piv...@gm...> wrote:
> On Wed, Nov 7, 2012 at 6:23 PM, Michael Droettboom <md...@st...>
> wrote:
> > The milestone is clear. Is there anything we're missing?
> >
> > If not, I plan to cut a final release and update the documentation
> > website tomorrow morning.
>
> I just submitted #1462 against v1.2.x, (which is also pending as #1458
> against master).
>
> "use plt.subplots() in examples as much as possible"
>
> replaces a whole bunch of example code like this:
>
> fig = plt.figure()
> ax = plt.subplot(111) # or plt.add_subplot(111)
>
> to be just this:
>
> fig, ax = plt.subplots()
>
> This is a docs-only update - but I think it'll be worthwhile to start
> to give a more sensible way of creating figures and axes in one call
> for our the folks who'll be looking at matplotlib with fresh eyes
> after the 1.2 release.
>
> But I totally understand if folks feel this is too big of a pill to
> swallow this late in the game.
>
> go, team, go!
> --
> Paul Ivanov
> 314 address only used for lists, off-list direct email at:
> http://pirsquared.org | GPG/PGP key id: 0x0F3E28F7
>
>
> ------------------------------------------------------------------------------
> Everyone hates slow websites. So do we.
> Make your web apps faster with AppDynamics
> Download AppDynamics Lite for free today:
> http://p.sf.net/sfu/appdyn_d2d_nov
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>

On Wed, Nov 7, 2012 at 6:23 PM, Michael Droettboom <md...@st...> wrote:
> The milestone is clear. Is there anything we're missing?
>
> If not, I plan to cut a final release and update the documentation
> website tomorrow morning.
I just submitted #1462 against v1.2.x, (which is also pending as #1458
against master).
"use plt.subplots() in examples as much as possible"
replaces a whole bunch of example code like this:
 fig = plt.figure()
 ax = plt.subplot(111) # or plt.add_subplot(111)
to be just this:
 fig, ax = plt.subplots()
This is a docs-only update - but I think it'll be worthwhile to start
to give a more sensible way of creating figures and axes in one call
for our the folks who'll be looking at matplotlib with fresh eyes
after the 1.2 release.
But I totally understand if folks feel this is too big of a pill to
swallow this late in the game.
go, team, go!
-- 
Paul Ivanov
314 address only used for lists, off-list direct email at:
http://pirsquared.org | GPG/PGP key id: 0x0F3E28F7

I just noticed a small documentation issue yesterday. This table does not
include the
gtk3 backend
http://matplotlib.org/1.2.0/faq/usage_faq.html#what-is-a-backend
Should we update the table to include the gtk3 backend? (and note that the
qt3 backend is depreciated)
Jens
On Thu, Nov 8, 2012 at 3:23 AM, Michael Droettboom <md...@st...> wrote:
> The milestone is clear. Is there anything we're missing?
>
> If not, I plan to cut a final release and update the documentation
> website tomorrow morning.
>
> Mike
>
>
> ------------------------------------------------------------------------------
> Everyone hates slow websites. So do we.
> Make your web apps faster with AppDynamics
> Download AppDynamics Lite for free today:
> http://p.sf.net/sfu/appdyn_d2d_nov
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>

The milestone is clear. Is there anything we're missing?
If not, I plan to cut a final release and update the documentation 
website tomorrow morning.
Mike

P.S.: As an aside, when I run ffmpeg on my machine it issues a
deprecation warning and suggests to use avconv instead. Is it worth
converting animation.py from ffmpeg to avconv, too? The command line
arguments should be virtually identicaly (as far as I know - I only
use it very occasionally, though).
Cheers,
Max

Hi all,
apologies for the delay in getting back to you! The end of last week
was quite busy and I was away from my computer during the weekend.
2012年11月1日 Ryan May <rm...@gm...>:
> You might have more luck using a temp-file based writer. By default,
> movies are created by piping in the data to the command; this is much
> faster, but, at least as I've done it now, requires a fixed number of
> bytes per frame. Try passing writer='ffmpeg_file' or
> writer='mencoder_file' to the command to save the animation.
Yes, this works indeed. Thanks for pointing it out! I had feared that
getting the 'bbox_inches' argument to work at all would be much more
involved.
> If I get a chance (or someone else if you want to help), I'll see if
> there's any way to make the pipe-based writers work with
> variable-sized frames.
That would be awesome of course. :)
> Failing that, we could just ignore the tight
> bbox option when using pipes for saving movies.
I like this idea. I have now updated my branch so that the save()
method checks which writer is being used. If it is not a temp
file-based one a warning is issued and the 'bbox_inches' argument is
dropped if it is present (see [1]). Please review and comment. :)
Best regards,
Max
[1] https://github.com/maxalbert/matplotlib/commit/fe44357d04fd708c616e88e386bb06100c12aaca

Can you try https://github.com/matplotlib/matplotlib/pull/1446?
Mike
On 11/01/2012 01:59 PM, Andrew Dawson wrote:
> It is possible I have spoken too soon. It certainly fixes the specific 
> issue I was having, however I am now getting serious issues with a 
> plot that uses the basemap toolkit. The contours and coastlines extend 
> way beyond the plot boundaries. I've put links to before and after 
> plots from something I'm working on, I don't have time to do a clean 
> test script tonight though.
>
> I don't know if this is a matplotlib issue or something to do with 
> basemap... some thought is probably required on this one.
>
> http://dl.dropbox.com/u/4496818/bad.pdf
> http://dl.dropbox.com/u/4496818/good.pdf
>
> Andrew
>
>
> On 1 November 2012 16:02, Andrew Dawson <da...@at... 
> <mailto:da...@at...>> wrote:
>
> Yes this seems to work for me.
>
>
> On 1 November 2012 15:25, Michael Droettboom <md...@st...
> <mailto:md...@st...>> wrote:
>
> I now have a fix attached to that issue. Andrew: can you
> confirm it works for you?
>
> Mike
>
>
> On 11/01/2012 09:06 AM, Michael Droettboom wrote:
>> I've filed an issue for this here:
>>
>> https://github.com/matplotlib/matplotlib/issues/1444
>>
>> Mike
>>
>> On 10/31/2012 12:20 PM, Andrew Dawson wrote:
>>> Hi all,
>>>
>>> I just noticed that colorbar edges are drawn in white when
>>> output in PDF and black when output in PNG. A small test
>>> script is attached along with the output to show the difference.
>>>
>>> I'd be interested in knowing if others can reproduce this?
>>> I'm using mpl-1.3.x (updated 5 minutes ago) on 64-bit Ubuntu
>>> 12.04.
>>>
>>> Cheers,
>>> Andrew
>>>
>>> bug.py
>>>
>>>
>>> import matplotlib.pyplot as plt
>>> import numpy as np
>>>
>>> # dummy data
>>> x = y = np.linspace(-np.pi, np.pi, 50)
>>> X, Y = np.meshgrid(x, y)
>>> Z = np.sin(X) * np.cos(2.*Y)
>>>
>>> # draw a filled contour plot and add a colorbar with drawedges turned on
>>> contours = plt.contourf(x, y, Z)
>>> cb = plt.colorbar(orientation='horizontal', drawedges=True)
>>>
>>> # turn off tick marks so the edges can be seen
>>> for tick in cb.ax.get_xticklines() + cb.ax.get_yticklines():
>>> tick.set_visible(False)
>>>
>>> # save as a PDF and a PNG
>>> plt.savefig('test.pdf')
>>> plt.savefig('test.png')
>>>
>>
>>
>>
>> ------------------------------------------------------------------------------
>> Everyone hates slow websites. So do we.
>> Make your web apps faster with AppDynamics
>> Download AppDynamics Lite for free today:
>> http://p.sf.net/sfu/appdyn_sfd2d_oct
>>
>>
>> _______________________________________________
>> Matplotlib-devel mailing list
>> Mat...@li... <mailto:Mat...@li...>
>> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>
>
> ------------------------------------------------------------------------------
> Everyone hates slow websites. So do we.
> Make your web apps faster with AppDynamics
> Download AppDynamics Lite for free today:
> http://p.sf.net/sfu/appdyn_sfd2d_oct
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> <mailto:Mat...@li...>
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>
>
>
>
> -- 
> Dr Andrew Dawson
> Atmospheric, Oceanic & Planetary Physics
> Clarendon Laboratory
> Parks Road
> Oxford OX1 3PU, UK
> Tel: +44 (0)1865 282438 <tel:%2B44%20%280%291865%20282438>
> Email: da...@at... <mailto:da...@at...>
> Web Site: http://www2.physics.ox.ac.uk/contacts/people/dawson
>
>

Thanks. I think the clipping is getting thrown away by what I just 
did. It should be an easy fix.
Mike
On 11/01/2012 01:59 PM, Andrew Dawson wrote:
> It is possible I have spoken too soon. It certainly fixes the specific 
> issue I was having, however I am now getting serious issues with a 
> plot that uses the basemap toolkit. The contours and coastlines extend 
> way beyond the plot boundaries. I've put links to before and after 
> plots from something I'm working on, I don't have time to do a clean 
> test script tonight though.
>
> I don't know if this is a matplotlib issue or something to do with 
> basemap... some thought is probably required on this one.
>
> http://dl.dropbox.com/u/4496818/bad.pdf
> http://dl.dropbox.com/u/4496818/good.pdf
>
> Andrew
>
>
> On 1 November 2012 16:02, Andrew Dawson <da...@at... 
> <mailto:da...@at...>> wrote:
>
> Yes this seems to work for me.
>
>
> On 1 November 2012 15:25, Michael Droettboom <md...@st...
> <mailto:md...@st...>> wrote:
>
> I now have a fix attached to that issue. Andrew: can you
> confirm it works for you?
>
> Mike
>
>
> On 11/01/2012 09:06 AM, Michael Droettboom wrote:
>> I've filed an issue for this here:
>>
>> https://github.com/matplotlib/matplotlib/issues/1444
>>
>> Mike
>>
>> On 10/31/2012 12:20 PM, Andrew Dawson wrote:
>>> Hi all,
>>>
>>> I just noticed that colorbar edges are drawn in white when
>>> output in PDF and black when output in PNG. A small test
>>> script is attached along with the output to show the difference.
>>>
>>> I'd be interested in knowing if others can reproduce this?
>>> I'm using mpl-1.3.x (updated 5 minutes ago) on 64-bit Ubuntu
>>> 12.04.
>>>
>>> Cheers,
>>> Andrew
>>>
>>> bug.py
>>>
>>>
>>> import matplotlib.pyplot as plt
>>> import numpy as np
>>>
>>> # dummy data
>>> x = y = np.linspace(-np.pi, np.pi, 50)
>>> X, Y = np.meshgrid(x, y)
>>> Z = np.sin(X) * np.cos(2.*Y)
>>>
>>> # draw a filled contour plot and add a colorbar with drawedges turned on
>>> contours = plt.contourf(x, y, Z)
>>> cb = plt.colorbar(orientation='horizontal', drawedges=True)
>>>
>>> # turn off tick marks so the edges can be seen
>>> for tick in cb.ax.get_xticklines() + cb.ax.get_yticklines():
>>> tick.set_visible(False)
>>>
>>> # save as a PDF and a PNG
>>> plt.savefig('test.pdf')
>>> plt.savefig('test.png')
>>>
>>
>>
>>
>> ------------------------------------------------------------------------------
>> Everyone hates slow websites. So do we.
>> Make your web apps faster with AppDynamics
>> Download AppDynamics Lite for free today:
>> http://p.sf.net/sfu/appdyn_sfd2d_oct
>>
>>
>> _______________________________________________
>> Matplotlib-devel mailing list
>> Mat...@li... <mailto:Mat...@li...>
>> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>
>
> ------------------------------------------------------------------------------
> Everyone hates slow websites. So do we.
> Make your web apps faster with AppDynamics
> Download AppDynamics Lite for free today:
> http://p.sf.net/sfu/appdyn_sfd2d_oct
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> <mailto:Mat...@li...>
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>
>
>
>
> -- 
> Dr Andrew Dawson
> Atmospheric, Oceanic & Planetary Physics
> Clarendon Laboratory
> Parks Road
> Oxford OX1 3PU, UK
> Tel: +44 (0)1865 282438 <tel:%2B44%20%280%291865%20282438>
> Email: da...@at... <mailto:da...@at...>
> Web Site: http://www2.physics.ox.ac.uk/contacts/people/dawson
>
>

It is possible I have spoken too soon. It certainly fixes the specific
issue I was having, however I am now getting serious issues with a plot
that uses the basemap toolkit. The contours and coastlines extend way
beyond the plot boundaries. I've put links to before and after plots from
something I'm working on, I don't have time to do a clean test script
tonight though.
I don't know if this is a matplotlib issue or something to do with
basemap... some thought is probably required on this one.
http://dl.dropbox.com/u/4496818/bad.pdf
http://dl.dropbox.com/u/4496818/good.pdf
Andrew
On 1 November 2012 16:02, Andrew Dawson <da...@at...> wrote:
> Yes this seems to work for me.
>
>
> On 1 November 2012 15:25, Michael Droettboom <md...@st...> wrote:
>
>> I now have a fix attached to that issue. Andrew: can you confirm it
>> works for you?
>>
>> Mike
>>
>>
>> On 11/01/2012 09:06 AM, Michael Droettboom wrote:
>>
>> I've filed an issue for this here:
>>
>> https://github.com/matplotlib/matplotlib/issues/1444
>>
>> Mike
>>
>> On 10/31/2012 12:20 PM, Andrew Dawson wrote:
>>
>> Hi all,
>>
>> I just noticed that colorbar edges are drawn in white when output in
>> PDF and black when output in PNG. A small test script is attached along
>> with the output to show the difference.
>>
>> I'd be interested in knowing if others can reproduce this? I'm using
>> mpl-1.3.x (updated 5 minutes ago) on 64-bit Ubuntu 12.04.
>>
>> Cheers,
>> Andrew
>>
>> bug.py
>>
>> import matplotlib.pyplot as plt
>> import numpy as np
>>
>> # dummy data
>> x = y = np.linspace(-np.pi, np.pi, 50)
>> X, Y = np.meshgrid(x, y)
>> Z = np.sin(X) * np.cos(2.*Y)
>>
>> # draw a filled contour plot and add a colorbar with drawedges turned on
>> contours = plt.contourf(x, y, Z)
>> cb = plt.colorbar(orientation='horizontal', drawedges=True)
>>
>> # turn off tick marks so the edges can be seen
>> for tick in cb.ax.get_xticklines() + cb.ax.get_yticklines():
>> tick.set_visible(False)
>>
>> # save as a PDF and a PNG
>> plt.savefig('test.pdf')
>> plt.savefig('test.png')
>>
>>
>>
>>
>>
>> ------------------------------------------------------------------------------
>> Everyone hates slow websites. So do we.
>> Make your web apps faster with AppDynamics
>> Download AppDynamics Lite for free today:http://p.sf.net/sfu/appdyn_sfd2d_oct
>>
>>
>>
>> _______________________________________________
>> Matplotlib-devel mailing lis...@li...https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>>
>>
>>
>>
>> ------------------------------------------------------------------------------
>> Everyone hates slow websites. So do we.
>> Make your web apps faster with AppDynamics
>> Download AppDynamics Lite for free today:
>> http://p.sf.net/sfu/appdyn_sfd2d_oct
>> _______________________________________________
>> Matplotlib-devel mailing list
>> Mat...@li...
>> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>>
>>
>
>
> --
> Dr Andrew Dawson
> Atmospheric, Oceanic & Planetary Physics
> Clarendon Laboratory
> Parks Road
> Oxford OX1 3PU, UK
> Tel: +44 (0)1865 282438
> Email: da...@at...
> Web Site: http://www2.physics.ox.ac.uk/contacts/people/dawson
>
>

I now have a fix attached to that issue. Andrew: can you confirm it 
works for you?
Mike
On 11/01/2012 09:06 AM, Michael Droettboom wrote:
> I've filed an issue for this here:
>
> https://github.com/matplotlib/matplotlib/issues/1444
>
> Mike
>
> On 10/31/2012 12:20 PM, Andrew Dawson wrote:
>> Hi all,
>>
>> I just noticed that colorbar edges are drawn in white when output in 
>> PDF and black when output in PNG. A small test script is attached 
>> along with the output to show the difference.
>>
>> I'd be interested in knowing if others can reproduce this? I'm using 
>> mpl-1.3.x (updated 5 minutes ago) on 64-bit Ubuntu 12.04.
>>
>> Cheers,
>> Andrew
>>
>> bug.py
>>
>>
>> import matplotlib.pyplot as plt
>> import numpy as np
>>
>> # dummy data
>> x = y = np.linspace(-np.pi, np.pi, 50)
>> X, Y = np.meshgrid(x, y)
>> Z = np.sin(X) * np.cos(2.*Y)
>>
>> # draw a filled contour plot and add a colorbar with drawedges turned on
>> contours = plt.contourf(x, y, Z)
>> cb = plt.colorbar(orientation='horizontal', drawedges=True)
>>
>> # turn off tick marks so the edges can be seen
>> for tick in cb.ax.get_xticklines() + cb.ax.get_yticklines():
>> tick.set_visible(False)
>>
>> # save as a PDF and a PNG
>> plt.savefig('test.pdf')
>> plt.savefig('test.png')
>>
>
>
>
> ------------------------------------------------------------------------------
> Everyone hates slow websites. So do we.
> Make your web apps faster with AppDynamics
> Download AppDynamics Lite for free today:
> http://p.sf.net/sfu/appdyn_sfd2d_oct
>
>
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

On Thu, Nov 1, 2012 at 5:38 AM, Maximilian Albert
<max...@gm...> wrote:
> Hi all,
>
> quick update on this: I pushed a small change to make the default
> argument immutable (thanks to Jens for pointing this out). Just a
> couple more questions/comments:
>
> 1) Should there be a test for this? I couldn't find any tests for the
> Animation class, so I haven't added one. But perhaps I just missed
> them.
Sadly there are no tests. Partially because I'm lazy, and partially
because I'm not sure how exactly that would work. I'd gladly take a PR
with some if someone can figure it out, but I realize that's more than
you signed up for.
> 2) I discovered this morning that my change uncovers/introduces a bug
> in the Animation class, so I'd appreciate a bit more input on whether
> it should be merged in the current state. Here is an explanation:
>
> My original use case the suggested change was to be able to set tight
> bounding boxes when saving animation frames. At the time I simply
> saved all frames to separate images and combined them manually using
> avconv, which worked fine. I saw that in the development version of
> matplotlib there is built-in support for this, so that the video file
> is created automatically. Now whenever I change the bounding box, e.g.
> by passing something like savefig_kwargs={'bbox_inches': 'tight'} to
> Animation.save(), then the output video shows complete garbage
> (similar to white noise). I presume this is because the 'frame_size'
> property in the MovieWriter class is not aware of the bounding box
> changes introduced by savefig_kwargs and thus reports a frame size to
> the video converter that is different from the actual size of the
> saved frames.
>
> I don't have much time to look into this at the moment, but I just
> wanted to point it out. Does anyone have a quick idea for a good fix,
> before I get the time to look into the details of how the MovieWriter
> class works?
You might have more luck using a temp-file based writer. By default,
movies are created by piping in the data to the command; this is much
faster, but, at least as I've done it now, requires a fixed number of
bytes per frame. Try passing writer='ffmpeg_file' or
writer='mencoder_file' to the command to save the animation.
If I get a chance (or someone else if you want to help), I'll see if
there's any way to make the pipe-based writers work with
variable-sized frames. Failing that, we could just ignore the tight
bbox option when using pipes for saving movies.
Thanks for the work!
Ryan
-- 
Ryan May
Graduate Research Assistant
School of Meteorology
University of Oklahoma