matplotlib-devel Mailing List for matplotlib (Page 4)

Russell Owen <ro...@uw...> writes:
> By the way: I installed ghostscript from source and Inkscape
> application from binary. More tests pass, but many still show K. My
> guess is that matplotlib can see ghostscript but not the Inkscape
> application (no surprise). Inkscape has too many dependencies for me
> to want to try to build it from source.
The following should help matplotlib find Inkscape:
PATH=$PATH:/Applications/Inkscape.app/Contents/Resources/bin \
 python -c 'import matplotlib; matplotlib.test(1)'
-- 
Jouni K. Seppänen
http://www.iki.fi/jks

On 07/05/2012 01:41 PM, Russell Owen wrote:
> By the way: I installed ghostscript from source and Inkscape application
> from binary. More tests pass, but many still show K. My guess is that
> matplotlib can see ghostscript but not the Inkscape application (no
> surprise). Inkscape has too many dependencies for me to want to try to
> build it from source.
>
> That leaves one unexpected failure with matplotlib 1.1.1 with the 64-bit
> 10.6-and-later binary and no failures with the 32-bit 10.3.9-and-later
> binary.
That one Stix failure is nothing to worry about; it seems there has been 
some subtle Stix change such that a baseline image that works on one 
machine fails on another.
Eric
>
> Regards,
>
> -- Russell
>
> On Jul 5, 2012, at 12:47 PM, John Hunter wrote:
>
>> On Thu, Jul 5, 2012 at 2:43 PM, Russell E. Owen <ro...@uw...
>> <mailto:ro...@uw...>> wrote:
>>
>>
>> When I tested on Mac OS X 10.6 I found that most unit tests were
>> somehow
>> missing. Rather than try to diagnose the problem, I built a new binary
>> on 10.6, confirmed that it installed properly (with all unit tests) on
>> 10.6 and 10.7, then uploaded it to replace the earlier 10.6 binary.
>>
>> The same test I mentioned in my previous post still fails using
>> the new
>> binary, on both 10.6 and 10.7.
>>
>>
>> Almost all of the test failures you ported were 'K' ie KNOWNFAIL.
>> Usually when you get a bunch of knownfails, it is because you don't
>> have a prereq installed, eg inkscape for converting SVG.
>>
>> Are you sure you have the requirements on all of the platforms
>>
>> http://matplotlib.sourceforge.net/devel/coding_guide.html#requirements
>>
>> Thanks,
>> JDH
>
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>
>
>
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>

By the way: I installed ghostscript from source and Inkscape application from binary. More tests pass, but many still show K. My guess is that matplotlib can see ghostscript but not the Inkscape application (no surprise). Inkscape has too many dependencies for me to want to try to build it from source.
That leaves one unexpected failure with matplotlib 1.1.1 with the 64-bit 10.6-and-later binary and no failures with the 32-bit 10.3.9-and-later binary.
Regards,
-- Russell
On Jul 5, 2012, at 12:47 PM, John Hunter wrote:
> On Thu, Jul 5, 2012 at 2:43 PM, Russell E. Owen <ro...@uw...> wrote:
> 
> When I tested on Mac OS X 10.6 I found that most unit tests were somehow
> missing. Rather than try to diagnose the problem, I built a new binary
> on 10.6, confirmed that it installed properly (with all unit tests) on
> 10.6 and 10.7, then uploaded it to replace the earlier 10.6 binary.
> 
> The same test I mentioned in my previous post still fails using the new
> binary, on both 10.6 and 10.7.
> 
> 
> Almost all of the test failures you ported were 'K' ie KNOWNFAIL. Usually when you get a bunch of knownfails, it is because you don't have a prereq installed, eg inkscape for converting SVG.
> 
> Are you sure you have the requirements on all of the platforms
> 
> http://matplotlib.sourceforge.net/devel/coding_guide.html#requirements
> 
> Thanks,
> JDH 

When I say "somehow missing" I'm not referring to the K (known fail). I'm referring to exceptions and tracebacks caused by trying to import test_X for various value of X: the modules were actually missing. I've never seen that before, so I was quite shocked. Normally I build on the oldest version of Mac OS X I can for the desired binary, but in this case I wanted to see what would happen if I built on 10.7 for a binary that works on 10.6 and 10.7. It resulted in this odd situation: the binary installed everything correctly on 10.7 but somehow failed to install some sub-packages on 10.6. Unfortunately I don't have time to look into it right now; I just took the simple way out of building again on 10.6. Unfortunately that meant a binary with known issues was up for a few hours. I do have the defective binary installer if anyone wants a look at it.
-- Russell
On Jul 5, 2012, at 12:47 PM, John Hunter wrote:
> 
> 
> On Thu, Jul 5, 2012 at 2:43 PM, Russell E. Owen <ro...@uw...> wrote:
> 
> When I tested on Mac OS X 10.6 I found that most unit tests were somehow
> missing. Rather than try to diagnose the problem, I built a new binary
> on 10.6, confirmed that it installed properly (with all unit tests) on
> 10.6 and 10.7, then uploaded it to replace the earlier 10.6 binary.
> 
> The same test I mentioned in my previous post still fails using the new
> binary, on both 10.6 and 10.7.
> 
> 
> Almost all of the test failures you ported were 'K' ie KNOWNFAIL. Usually when you get a bunch of knownfails, it is because you don't have a prereq installed, eg inkscape for converting SVG.
> 
> Are you sure you have the requirements on all of the platforms
> 
> http://matplotlib.sourceforge.net/devel/coding_guide.html#requirements
> 
> Thanks,
> JDH 

On Thu, Jul 5, 2012 at 2:43 PM, Russell E. Owen <ro...@uw...> wrote:
>
> When I tested on Mac OS X 10.6 I found that most unit tests were somehow
> missing. Rather than try to diagnose the problem, I built a new binary
> on 10.6, confirmed that it installed properly (with all unit tests) on
> 10.6 and 10.7, then uploaded it to replace the earlier 10.6 binary.
>
> The same test I mentioned in my previous post still fails using the new
> binary, on both 10.6 and 10.7.
>
>
Almost all of the test failures you ported were 'K' ie KNOWNFAIL. Usually
when you get a bunch of knownfails, it is because you don't have a prereq
installed, eg inkscape for converting SVG.
Are you sure you have the requirements on all of the platforms
http://matplotlib.sourceforge.net/devel/coding_guide.html#requirements
Thanks,
JDH

In article <EF3...@uw...>,
 Russell Owen <ro...@uw...> wrote:
> I just uploaded the Mac binaries.
> 
> Several minor concerns:
> - Many unit tests failed on Mac OS X 10.4 (which is where I build the 10.3.9 
> version) due to "too many files open", but the same binary looks fine on 
> 10.5.
> - The 64-bit version (10.6 and later) had one unexpected failure on 10.7 (I 
> have not yet had time to test it on 10.6)...
When I tested on Mac OS X 10.6 I found that most unit tests were somehow 
missing. Rather than try to diagnose the problem, I built a new binary 
on 10.6, confirmed that it installed properly (with all unit tests) on 
10.6 and 10.7, then uploaded it to replace the earlier 10.6 binary.
The same test I mentioned in my previous post still fails using the new 
binary, on both 10.6 and 10.7.
-- Russell

I just uploaded the Mac binaries.
Several minor concerns:
- Many unit tests failed on Mac OS X 10.4 (which is where I build the 10.3.9 version) due to "too many files open", but the same binary looks fine on 10.5.
- The 64-bit version (10.6 and later) had one unexpected failure on 10.7 (I have not yet had time to test it on 10.6)
localhost$ python -c "import matplotlib as m ; m.test(verbosity=1)"
..K..............KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK..KK.KK.KK.KK.KK.KK.KKK...KK...KK.KK..KKKK..KK.KK.KK.KK.KK.KK..KK.KK.KK.............................................................................F..........................................................................................................KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK...KK.KK.KK.KK.KK.KK.KK.KK..............................................................KK.KK
======================================================================
FAIL: matplotlib.tests.test_mathtext.mathfont_stix_14_test.test
----------------------------------------------------------------------
Traceback (most recent call last):
 File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/nose/case.py", line 197, in runTest
 self.test(*self.arg)
 File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/matplotlib/testing/decorators.py", line 36, in failer
 result = f(*args, **kwargs)
 File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/matplotlib/testing/decorators.py", line 140, in do_test
 '(RMS %(rms).3f)'%err)
ImageComparisonFailure: images not close: /Users/rowen/result_images/test_mathtext/mathfont_stix_14.png vs. /Users/rowen/result_images/test_mathtext/expected-mathfont_stix_14.png (RMS 3377.889)
----------------------------------------------------------------------
Ran 1068 tests in 161.293s
-- Russell
On Jun 9, 2012, at 2:14 PM, John Hunter wrote:
> I just uploaded the v1.1.1rc2 tarballs to the sourceforge site
> 
> https://sourceforge.net/projects/matplotlib/files/matplotlib/matplotlib-1.1.1/
> 
> As soon as we get binaries, I'll send out another call for testing on
> the users list. Russell and Christoph, easiest if you just upload the
> binaries directly. You should both have permissions on the sf site.
> 
> A copy of the site docs are available at
> http://matplotlib.sourceforge.net/rc/v1.1.1rc2/

On 6/30/2012 1:24 PM, Christoph Gohlke wrote:
> On 6/30/2012 12:55 PM, John Hunter wrote:
>>
>>
>> On Sat, Jun 30, 2012 at 2:40 PM, Fernando Perez <fpe...@gm...
>> <mailto:fpe...@gm...>> wrote:
>>
>> On Sat, Jun 30, 2012 at 11:46 AM, John Hunter <jd...@gm...
>> <mailto:jd...@gm...>> wrote:
>> > Well, looks like we better get moving then ;-)
>>
>> Go MPL! It would be great to have matching releases of IPython and
>> MPL, just in time for the Debian freeze and SciPy 2012 :)
>>
>>
>> OK, the v1.1.1 tarball is up at
>> https://sourceforge.net/projects/matplotlib/files/matplotlib/matplotlib-1.1.1
>> and this is now the download folder the main site points to. I'm
>> leaving up the rc2 binaries til Russell and Christoph can build v1.1.1
>> binaries and we get them uploaded. Sandro, if you're around, you are
>> good to go for including this in debian, hopefully squeaking in under
>> the freeze (sorry for the last minute push).
>>
>> I will hold off on the users and announce list emails til the updated
>> binaries are up.
>>
>> Tagged: git tag v1.1.1 7e47149a7b05f8e5cf1cc899a7e4e7c90dd4244f
>>
>> Thanks to all!
>> JDH
>
> Here are the Windows installers, built against numpy 1.6.2. Sorry, I can
> not upload them to SF. There seems to be some permission problems that
> the SF admins would need to fix manually.
>
> <http://www.lfd.uci.edu/~gohlke/pythonlibs/#matplotlib>
>
> Christoph
>
Sourceforge has fixed the permissions. I uploaded the Windows installers.
Christoph

On Tue, Jul 3, 2012 at 10:03 AM, Tony Yu <ts...@gm...> wrote:
>
>
> On Tue, Jul 3, 2012 at 10:22 AM, Ryan May <rm...@gm...> wrote:
>>
>> On Tue, Jul 3, 2012 at 9:14 AM, Tony Yu <ts...@gm...> wrote:
>> > On Mon, Jul 2, 2012 at 11:42 PM, Tony Yu <ts...@gm...> wrote:
>> >> On Sun, Jun 24, 2012 at 10:02 AM, Tony Yu <ts...@gm...> wrote:
>> >>>
>> >>> I'm having a tough time figuring this out: Saving an animation seems
>> >>> to
>> >>> hang when using `streamplot`. The exact same animation runs without
>> >>> issue
>> >>> when calling show.
>> >>>
>> >>> On my system, the example below hangs consistently at frame 173.
>> >>> However,
>> >>> the number of saved frames (before hanging) varies with density of
>> >>> stream
>> >>> lines (i.e. number of line segments in streamplot): More frames saved
>> >>> for
>> >>> lower density.
>> >>>
>> >>> Seems to be a memory or file-size issue, but
>> >>>
>> >>> * Memory use doesn't seem to grow. (this suggests that ffmpeg adds
>> >>> frames to disk as opposed to memory.)
>> >>> * Saving the animation up to the frame just before it hangs gives
>> >>> modest (~1MB) videos.
>> >>> Maybe this is a limitation of `ffmpeg`?
>> >>>
>> >>> Can someone confirm that the example hangs on their system? (Somehow,
>> >>> I
>> >>> often run into bugs that are not reproducible.)
>> >>>
>> >>> In case this is system dependent:
>> >>> * OSX 10.6
>> >>> * Python 2.6.1 (system install)
>> >>> * matplotlib master
>> >>> * ffmpeg 0.10
>> >>>
>> >>> Simple plots seem to work fine, but I should probably try to reproduce
>> >>> using something other than streamplot (maybe create the equivalent
>> >>> number of
>> >>> line and arrow collections).
>> >>>
>> >>> -Tony
>> >>>
>> >>> #~~~ Example
>> >>> import numpy as np
>> >>> import matplotlib.pyplot as plt
>> >>> import matplotlib.animation as animation
>> >>>
>> >>> fig, ax = plt.subplots()
>> >>>
>> >>> # do nothing function that prints frame
>> >>> def update(frame_num):
>> >>> print frame_num
>> >>> return []
>> >>>
>> >>> Y, X = np.mgrid[:1:100j, :1:100j]
>> >>> U = np.ones_like(X)
>> >>> V = np.ones_like(X)
>> >>> ax.streamplot(X, Y, U, V, density=1)
>> >>>
>> >>> ani = animation.FuncAnimation(fig, update, save_count=500)
>> >>>
>> >>> # save hangs at frame 173 (this probably varies by system, if it's
>> >>> reproducible).
>> >>> ani.save('animation.avi')
>> >>> # show animates all frames w/o issue.
>> >>> #plt.show()
>> >>>
>> >>>
>> >>
>> >> I finally had some time to revisit this issue. It seems that subprocess
>> >> PIPEs have fairly limited buffers [1] (also see docs for
>> >> `subprocess.Popen.communicate` [2]) and ffmpeg tends to generate a
>> >> decent
>> >> amount of output to stderr. A simple solution is to redirect stderr to
>> >> a
>> >> temporary file. This change fixes the issue on my system.
>> >>
>> >> If this bug is reproducible, I can submit a PR. The temporary file here
>> >> could be created using tempfile so it gets cleaned up automatically, or
>> >> maybe a more permanent log file for debugging. Thoughts?
>> >>
>> >> -Tony
>> >>
>> >> [1]
>> >>
>> >> http://thraxil.org/users/anders/posts/2008/03/13/Subprocess-Hanging-PIPE-is-your-enemy/
>> >>
>> >> [2]
>> >>
>> >> http://docs.python.org/library/subprocess.html#subprocess.Popen.communicate
>> >>
>> >
>> > And just to clarify: My original email mentioned that saving would hang
>> > only
>> > when `streamplot` was used to create the figure. It turns out that
>> > ffmpeg
>> > prints more output (keyframes?) for more complex images, so when I ran
>> > simpler plots, they didn't produce enough output to fill the subprocess
>> > `PIPE` (although they would eventually).
>> >
>> > Also, theres's a simpler fix than piping ffmpeg output to a file: Just
>> > set
>> > `-loglevel quiet` in the ffmpeg command.
>> >
>> > -Tony
>>
>> It's not a bad idea to have it logged to a file in a temp directory.
>> We could potentially just do this if debug is set to verbose, however,
>> and just use -loglevel quiet otherwise. Can you manage PR for this or
>> do I need to?
>>
>> Ryan
>>
>
> Hey Ryan,
>
> If you have time, that'd be great. Otherwise, I should have some time at the
> end of the week to submit a PR.
>
> -Tony
>
I might be able to squeeze it in. If you don't see anything by the end
of the week, hit me up.
Ryan
-- 
Ryan May
Graduate Research Assistant
School of Meteorology
University of Oklahoma

On Tue, Jul 3, 2012 at 10:22 AM, Ryan May <rm...@gm...> wrote:
> On Tue, Jul 3, 2012 at 9:14 AM, Tony Yu <ts...@gm...> wrote:
> > On Mon, Jul 2, 2012 at 11:42 PM, Tony Yu <ts...@gm...> wrote:
> >> On Sun, Jun 24, 2012 at 10:02 AM, Tony Yu <ts...@gm...> wrote:
> >>>
> >>> I'm having a tough time figuring this out: Saving an animation seems to
> >>> hang when using `streamplot`. The exact same animation runs without
> issue
> >>> when calling show.
> >>>
> >>> On my system, the example below hangs consistently at frame 173.
> However,
> >>> the number of saved frames (before hanging) varies with density of
> stream
> >>> lines (i.e. number of line segments in streamplot): More frames saved
> for
> >>> lower density.
> >>>
> >>> Seems to be a memory or file-size issue, but
> >>>
> >>> * Memory use doesn't seem to grow. (this suggests that ffmpeg adds
> >>> frames to disk as opposed to memory.)
> >>> * Saving the animation up to the frame just before it hangs gives
> >>> modest (~1MB) videos.
> >>> Maybe this is a limitation of `ffmpeg`?
> >>>
> >>> Can someone confirm that the example hangs on their system? (Somehow, I
> >>> often run into bugs that are not reproducible.)
> >>>
> >>> In case this is system dependent:
> >>> * OSX 10.6
> >>> * Python 2.6.1 (system install)
> >>> * matplotlib master
> >>> * ffmpeg 0.10
> >>>
> >>> Simple plots seem to work fine, but I should probably try to reproduce
> >>> using something other than streamplot (maybe create the equivalent
> number of
> >>> line and arrow collections).
> >>>
> >>> -Tony
> >>>
> >>> #~~~ Example
> >>> import numpy as np
> >>> import matplotlib.pyplot as plt
> >>> import matplotlib.animation as animation
> >>>
> >>> fig, ax = plt.subplots()
> >>>
> >>> # do nothing function that prints frame
> >>> def update(frame_num):
> >>> print frame_num
> >>> return []
> >>>
> >>> Y, X = np.mgrid[:1:100j, :1:100j]
> >>> U = np.ones_like(X)
> >>> V = np.ones_like(X)
> >>> ax.streamplot(X, Y, U, V, density=1)
> >>>
> >>> ani = animation.FuncAnimation(fig, update, save_count=500)
> >>>
> >>> # save hangs at frame 173 (this probably varies by system, if it's
> >>> reproducible).
> >>> ani.save('animation.avi')
> >>> # show animates all frames w/o issue.
> >>> #plt.show()
> >>>
> >>>
> >>
> >> I finally had some time to revisit this issue. It seems that subprocess
> >> PIPEs have fairly limited buffers [1] (also see docs for
> >> `subprocess.Popen.communicate` [2]) and ffmpeg tends to generate a
> decent
> >> amount of output to stderr. A simple solution is to redirect stderr to a
> >> temporary file. This change fixes the issue on my system.
> >>
> >> If this bug is reproducible, I can submit a PR. The temporary file here
> >> could be created using tempfile so it gets cleaned up automatically, or
> >> maybe a more permanent log file for debugging. Thoughts?
> >>
> >> -Tony
> >>
> >> [1]
> >>
> http://thraxil.org/users/anders/posts/2008/03/13/Subprocess-Hanging-PIPE-is-your-enemy/
> >>
> >> [2]
> >>
> http://docs.python.org/library/subprocess.html#subprocess.Popen.communicate
> >>
> >
> > And just to clarify: My original email mentioned that saving would hang
> only
> > when `streamplot` was used to create the figure. It turns out that ffmpeg
> > prints more output (keyframes?) for more complex images, so when I ran
> > simpler plots, they didn't produce enough output to fill the subprocess
> > `PIPE` (although they would eventually).
> >
> > Also, theres's a simpler fix than piping ffmpeg output to a file: Just
> set
> > `-loglevel quiet` in the ffmpeg command.
> >
> > -Tony
>
> It's not a bad idea to have it logged to a file in a temp directory.
> We could potentially just do this if debug is set to verbose, however,
> and just use -loglevel quiet otherwise. Can you manage PR for this or
> do I need to?
>
> Ryan
>
>
Hey Ryan,
If you have time, that'd be great. Otherwise, I should have some time at
the end of the week to submit a PR.
-Tony

On Tue, Jul 3, 2012 at 9:14 AM, Tony Yu <ts...@gm...> wrote:
> On Mon, Jul 2, 2012 at 11:42 PM, Tony Yu <ts...@gm...> wrote:
>> On Sun, Jun 24, 2012 at 10:02 AM, Tony Yu <ts...@gm...> wrote:
>>>
>>> I'm having a tough time figuring this out: Saving an animation seems to
>>> hang when using `streamplot`. The exact same animation runs without issue
>>> when calling show.
>>>
>>> On my system, the example below hangs consistently at frame 173. However,
>>> the number of saved frames (before hanging) varies with density of stream
>>> lines (i.e. number of line segments in streamplot): More frames saved for
>>> lower density.
>>>
>>> Seems to be a memory or file-size issue, but
>>>
>>> * Memory use doesn't seem to grow. (this suggests that ffmpeg adds
>>> frames to disk as opposed to memory.)
>>> * Saving the animation up to the frame just before it hangs gives
>>> modest (~1MB) videos.
>>> Maybe this is a limitation of `ffmpeg`?
>>>
>>> Can someone confirm that the example hangs on their system? (Somehow, I
>>> often run into bugs that are not reproducible.)
>>>
>>> In case this is system dependent:
>>> * OSX 10.6
>>> * Python 2.6.1 (system install)
>>> * matplotlib master
>>> * ffmpeg 0.10
>>>
>>> Simple plots seem to work fine, but I should probably try to reproduce
>>> using something other than streamplot (maybe create the equivalent number of
>>> line and arrow collections).
>>>
>>> -Tony
>>>
>>> #~~~ Example
>>> import numpy as np
>>> import matplotlib.pyplot as plt
>>> import matplotlib.animation as animation
>>>
>>> fig, ax = plt.subplots()
>>>
>>> # do nothing function that prints frame
>>> def update(frame_num):
>>> print frame_num
>>> return []
>>>
>>> Y, X = np.mgrid[:1:100j, :1:100j]
>>> U = np.ones_like(X)
>>> V = np.ones_like(X)
>>> ax.streamplot(X, Y, U, V, density=1)
>>>
>>> ani = animation.FuncAnimation(fig, update, save_count=500)
>>>
>>> # save hangs at frame 173 (this probably varies by system, if it's
>>> reproducible).
>>> ani.save('animation.avi')
>>> # show animates all frames w/o issue.
>>> #plt.show()
>>>
>>>
>>
>> I finally had some time to revisit this issue. It seems that subprocess
>> PIPEs have fairly limited buffers [1] (also see docs for
>> `subprocess.Popen.communicate` [2]) and ffmpeg tends to generate a decent
>> amount of output to stderr. A simple solution is to redirect stderr to a
>> temporary file. This change fixes the issue on my system.
>>
>> If this bug is reproducible, I can submit a PR. The temporary file here
>> could be created using tempfile so it gets cleaned up automatically, or
>> maybe a more permanent log file for debugging. Thoughts?
>>
>> -Tony
>>
>> [1]
>> http://thraxil.org/users/anders/posts/2008/03/13/Subprocess-Hanging-PIPE-is-your-enemy/
>>
>> [2]
>> http://docs.python.org/library/subprocess.html#subprocess.Popen.communicate
>>
>
> And just to clarify: My original email mentioned that saving would hang only
> when `streamplot` was used to create the figure. It turns out that ffmpeg
> prints more output (keyframes?) for more complex images, so when I ran
> simpler plots, they didn't produce enough output to fill the subprocess
> `PIPE` (although they would eventually).
>
> Also, theres's a simpler fix than piping ffmpeg output to a file: Just set
> `-loglevel quiet` in the ffmpeg command.
>
> -Tony
It's not a bad idea to have it logged to a file in a temp directory.
We could potentially just do this if debug is set to verbose, however,
and just use -loglevel quiet otherwise. Can you manage PR for this or
do I need to?
Ryan
-- 
Ryan May
Graduate Research Assistant
School of Meteorology
University of Oklahoma

On Mon, Jul 2, 2012 at 11:42 PM, Tony Yu <ts...@gm...> wrote:
>
>
> On Sun, Jun 24, 2012 at 10:02 AM, Tony Yu <ts...@gm...> wrote:
>
>> I'm having a tough time figuring this out: Saving an animation seems to
>> hang when using `streamplot`. The exact same animation runs without issue
>> when calling show.
>>
>> On my system, the example below hangs consistently at frame 173. However,
>> the number of saved frames (before hanging) varies with density of stream
>> lines (i.e. number of line segments in streamplot): More frames saved for
>> lower density.
>>
>> Seems to be a memory or file-size issue, but
>>
>> * Memory use doesn't seem to grow. (this suggests that ffmpeg adds
>> frames to disk as opposed to memory.)
>> * Saving the animation up to the frame just before it hangs gives
>> modest (~1MB) videos.
>> Maybe this is a limitation of `ffmpeg`?
>>
>> Can someone confirm that the example hangs on their system? (Somehow, I
>> often run into bugs that are not reproducible.)
>>
>> In case this is system dependent:
>> * OSX 10.6
>> * Python 2.6.1 (system install)
>> * matplotlib master
>> * ffmpeg 0.10
>>
>> Simple plots seem to work fine, but I should probably try to reproduce
>> using something other than streamplot (maybe create the equivalent number
>> of line and arrow collections).
>>
>> -Tony
>>
>> #~~~ Example
>> import numpy as np
>> import matplotlib.pyplot as plt
>> import matplotlib.animation as animation
>>
>> fig, ax = plt.subplots()
>>
>> # do nothing function that prints frame
>> def update(frame_num):
>> print frame_num
>> return []
>>
>> Y, X = np.mgrid[:1:100j, :1:100j]
>> U = np.ones_like(X)
>> V = np.ones_like(X)
>> ax.streamplot(X, Y, U, V, density=1)
>>
>> ani = animation.FuncAnimation(fig, update, save_count=500)
>>
>> # save hangs at frame 173 (this probably varies by system, if it's
>> reproducible).
>> ani.save('animation.avi')
>> # show animates all frames w/o issue.
>> #plt.show()
>>
>>
>>
> I finally had some time to revisit this issue. It seems that subprocess
> PIPEs have fairly limited buffers [1] (also see docs for
> `subprocess.Popen.communicate` [2]) and ffmpeg tends to generate a decent
> amount of output to stderr. A simple solution is to redirect stderr to a
> temporary file. This change fixes the issue on my system.
>
> If this bug is reproducible, I can submit a PR. The temporary file here
> could be created using tempfile so it gets cleaned up automatically, or
> maybe a more permanent log file for debugging. Thoughts?
>
> -Tony
>
> [1]
> http://thraxil.org/users/anders/posts/2008/03/13/Subprocess-Hanging-PIPE-is-your-enemy/
>
> [2]
> http://docs.python.org/library/subprocess.html#subprocess.Popen.communicate
>
>
And just to clarify: My original email mentioned that saving would hang
only when `streamplot` was used to create the figure. It turns out that
ffmpeg prints more output (keyframes?) for more complex images, so when I
ran simpler plots, they didn't produce enough output to fill the subprocess
`PIPE` (although they would eventually).
Also, theres's a simpler fix than piping ffmpeg output to a file: Just
set `-loglevel quiet` in the ffmpeg command.
-Tony

On Sun, Jun 24, 2012 at 10:02 AM, Tony Yu <ts...@gm...> wrote:
> I'm having a tough time figuring this out: Saving an animation seems to
> hang when using `streamplot`. The exact same animation runs without issue
> when calling show.
>
> On my system, the example below hangs consistently at frame 173. However,
> the number of saved frames (before hanging) varies with density of stream
> lines (i.e. number of line segments in streamplot): More frames saved for
> lower density.
>
> Seems to be a memory or file-size issue, but
>
> * Memory use doesn't seem to grow. (this suggests that ffmpeg adds
> frames to disk as opposed to memory.)
> * Saving the animation up to the frame just before it hangs gives
> modest (~1MB) videos.
> Maybe this is a limitation of `ffmpeg`?
>
> Can someone confirm that the example hangs on their system? (Somehow, I
> often run into bugs that are not reproducible.)
>
> In case this is system dependent:
> * OSX 10.6
> * Python 2.6.1 (system install)
> * matplotlib master
> * ffmpeg 0.10
>
> Simple plots seem to work fine, but I should probably try to reproduce
> using something other than streamplot (maybe create the equivalent number
> of line and arrow collections).
>
> -Tony
>
> #~~~ Example
> import numpy as np
> import matplotlib.pyplot as plt
> import matplotlib.animation as animation
>
> fig, ax = plt.subplots()
>
> # do nothing function that prints frame
> def update(frame_num):
> print frame_num
> return []
>
> Y, X = np.mgrid[:1:100j, :1:100j]
> U = np.ones_like(X)
> V = np.ones_like(X)
> ax.streamplot(X, Y, U, V, density=1)
>
> ani = animation.FuncAnimation(fig, update, save_count=500)
>
> # save hangs at frame 173 (this probably varies by system, if it's
> reproducible).
> ani.save('animation.avi')
> # show animates all frames w/o issue.
> #plt.show()
>
>
>
I finally had some time to revisit this issue. It seems that subprocess
PIPEs have fairly limited buffers [1] (also see docs for
`subprocess.Popen.communicate` [2]) and ffmpeg tends to generate a decent
amount of output to stderr. A simple solution is to redirect stderr to a
temporary file. This change fixes the issue on my system.
If this bug is reproducible, I can submit a PR. The temporary file here
could be created using tempfile so it gets cleaned up automatically, or
maybe a more permanent log file for debugging. Thoughts?
-Tony
[1]
http://thraxil.org/users/anders/posts/2008/03/13/Subprocess-Hanging-PIPE-is-your-enemy/
[2]
http://docs.python.org/library/subprocess.html#subprocess.Popen.communicate

On Sun, Jul 1, 2012 at 2:25 AM, John Hunter <jd...@gm...> wrote:
> It certainly was outside you control Sandro. You gave us ample warning and
> reminders. I misinterpreted the June 30th freeze date to mean we needed to
> get it in by that date, but maybe it meant before, or maybe at some earlier
> time today.
Timezones suck :) I need to balance the importance of the update with
the additional work the release team will need to carry to accept it
(so read another email from someone for a not-so-breaking-the-world
update, read the diff, understand it, comment it, reply - it seems few
steps, but multiply for all the possible minor updates to debian
packages and you'll see) so I think better leave time to deal with the
other problems they already have at hand without extra burden.
> In any care, I apologize for missing the deadline and for the trouble.
Oh don't! there's nothing to be sorry about, it's life and constraints
- we're still have a very stable mpl in wheezy, even if the version
has a RC in it :)
Cheers,
-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi

On Jun 30, 2012, at 6:27 PM, Derek Homeier <de...@as...> wrote:
>> 
>> And none of the rules match this situation. RC2 will be :)
> 
> What about the very last one?
> 
> "For packages which missed the freeze only for reasons outside of the control of the maintainers, we might be generous, but you need to contact us on your own, and you need to contact us soon."
> 
> 
It certainly was outside you control Sandro. You gave us ample warning and reminders. I misinterpreted the June 30th freeze date to mean we needed to get it in by that date, but maybe it meant before, or maybe at some earlier time today. 
In any care, I apologize for missing the deadline and for the trouble.