You can subscribe to this list here.
2003 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(3) |
Jun
|
Jul
|
Aug
(12) |
Sep
(12) |
Oct
(56) |
Nov
(65) |
Dec
(37) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2004 |
Jan
(59) |
Feb
(78) |
Mar
(153) |
Apr
(205) |
May
(184) |
Jun
(123) |
Jul
(171) |
Aug
(156) |
Sep
(190) |
Oct
(120) |
Nov
(154) |
Dec
(223) |
2005 |
Jan
(184) |
Feb
(267) |
Mar
(214) |
Apr
(286) |
May
(320) |
Jun
(299) |
Jul
(348) |
Aug
(283) |
Sep
(355) |
Oct
(293) |
Nov
(232) |
Dec
(203) |
2006 |
Jan
(352) |
Feb
(358) |
Mar
(403) |
Apr
(313) |
May
(165) |
Jun
(281) |
Jul
(316) |
Aug
(228) |
Sep
(279) |
Oct
(243) |
Nov
(315) |
Dec
(345) |
2007 |
Jan
(260) |
Feb
(323) |
Mar
(340) |
Apr
(319) |
May
(290) |
Jun
(296) |
Jul
(221) |
Aug
(292) |
Sep
(242) |
Oct
(248) |
Nov
(242) |
Dec
(332) |
2008 |
Jan
(312) |
Feb
(359) |
Mar
(454) |
Apr
(287) |
May
(340) |
Jun
(450) |
Jul
(403) |
Aug
(324) |
Sep
(349) |
Oct
(385) |
Nov
(363) |
Dec
(437) |
2009 |
Jan
(500) |
Feb
(301) |
Mar
(409) |
Apr
(486) |
May
(545) |
Jun
(391) |
Jul
(518) |
Aug
(497) |
Sep
(492) |
Oct
(429) |
Nov
(357) |
Dec
(310) |
2010 |
Jan
(371) |
Feb
(657) |
Mar
(519) |
Apr
(432) |
May
(312) |
Jun
(416) |
Jul
(477) |
Aug
(386) |
Sep
(419) |
Oct
(435) |
Nov
(320) |
Dec
(202) |
2011 |
Jan
(321) |
Feb
(413) |
Mar
(299) |
Apr
(215) |
May
(284) |
Jun
(203) |
Jul
(207) |
Aug
(314) |
Sep
(321) |
Oct
(259) |
Nov
(347) |
Dec
(209) |
2012 |
Jan
(322) |
Feb
(414) |
Mar
(377) |
Apr
(179) |
May
(173) |
Jun
(234) |
Jul
(295) |
Aug
(239) |
Sep
(276) |
Oct
(355) |
Nov
(144) |
Dec
(108) |
2013 |
Jan
(170) |
Feb
(89) |
Mar
(204) |
Apr
(133) |
May
(142) |
Jun
(89) |
Jul
(160) |
Aug
(180) |
Sep
(69) |
Oct
(136) |
Nov
(83) |
Dec
(32) |
2014 |
Jan
(71) |
Feb
(90) |
Mar
(161) |
Apr
(117) |
May
(78) |
Jun
(94) |
Jul
(60) |
Aug
(83) |
Sep
(102) |
Oct
(132) |
Nov
(154) |
Dec
(96) |
2015 |
Jan
(45) |
Feb
(138) |
Mar
(176) |
Apr
(132) |
May
(119) |
Jun
(124) |
Jul
(77) |
Aug
(31) |
Sep
(34) |
Oct
(22) |
Nov
(23) |
Dec
(9) |
2016 |
Jan
(26) |
Feb
(17) |
Mar
(10) |
Apr
(8) |
May
(4) |
Jun
(8) |
Jul
(6) |
Aug
(5) |
Sep
(9) |
Oct
(4) |
Nov
|
Dec
|
2017 |
Jan
(5) |
Feb
(7) |
Mar
(1) |
Apr
(5) |
May
|
Jun
(3) |
Jul
(6) |
Aug
(1) |
Sep
|
Oct
(2) |
Nov
(1) |
Dec
|
2018 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2020 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2025 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
S | M | T | W | T | F | S |
---|---|---|---|---|---|---|
|
1
|
2
(1) |
3
|
4
|
5
|
6
|
7
|
8
|
9
|
10
|
11
|
12
|
13
|
14
|
15
(1) |
16
|
17
|
18
|
19
|
20
|
21
|
22
(1) |
23
|
24
(6) |
25
(1) |
26
(2) |
27
(3) |
28
|
29
(2) |
|
|
|
|
|
Try running with '--verbose-debug' as in: python basic_example_writer.py --verbose-debug That should give you standard out and standard error from running ffmpeg, which might be illustrative. x264 is probably the most universally supported codec for html5 video. Another option would be to use imagemagick with the ImagemagickWriter and make an animated gif. Ryan On Wed, Feb 24, 2016 at 1:34 PM, Kyle Douglass <kyl...@gm...> wrote: > Hi all, > I would like to use matplotlib's animation API to create a movie that can > be embedded into an html5 video tag. To do this, I am following a couple > 2012 blog posts from Jake VanderPlas: > http://jakevdp.github.io/blog/2012/08/18/matplotlib-animation-tutorial/ > and > http://jakevdp.github.io/blog/2013/05/12/embedding-matplotlib-animations/ > > My understanding is that I need to use the x264 codec to do this. > Unfortunately, I get a Broken Pipe Error when running the basic example > below. I get the same error when calling the animation.to_html5_video() > method. > > Does anyone have an idea about why I'm getting the Broken Pipe error? Do I > really need the x264 codec to embed matplotlib animations into html? Thanks! > > Kyle > > *Example code:* > > *import numpy as np* > > *import matplotlib.pyplot as plt* > > *from matplotlib import animate* > > > > > > > > > > > > > > > > > > > > > > > > > *fig = plt.figure()ax = plt.axes(xlim = (0, 2), ylim = (-2, 2))line, > = ax.plot([], [], linewidth = 2)# initialization function: plot the > background of each framedef init(): line.set_data([], []) return > line,# animation function. This is called sequentiallydef animate(i): x > = np.linspace(0, 2, 1000) y = np.sin(2 * np.pi * (x - 0.01 * i)) > line.set_data(x, y) return line,# call the animatoranim = > animation.FuncAnimation(fig, animate, > init_func=init, frames=200, interval=20, > blit=True)myWriter = animation.FFMpegWriter(fps = 30, > extra_args=['-vcodec', 'libx264'])anim.save('basic_animation.mp4', writer = > myWriter)* > *plt.show()* > > *Traceback:* > > > > > > > > > > > > > > > > > > > > > > *Traceback (most recent call last): File "test.py", line 26, in > <module> anim.save('basic_animation.mp4', writer = myWriter) File > "/home/kmdouglass/anaconda3/lib/python3.5/site-packages/matplotlib/animation.py", > line 810, in save > writer.grab_frame(**savefig_kwargs) File > "/home/kmdouglass/anaconda3/lib/python3.5/site-packages/matplotlib/animation.py", > line 230, in grab_frame > dpi=self.dpi, **savefig_kwargs) File > "/home/kmdouglass/anaconda3/lib/python3.5/site-packages/matplotlib/figure.py", > line 1565, in savefig > self.canvas.print_figure(*args, **kwargs) File > "/home/kmdouglass/anaconda3/lib/python3.5/site-packages/matplotlib/backends/backend_qt5agg.py", > line 196, in print_figure > FigureCanvasAgg.print_figure(self, *args, **kwargs) File > "/home/kmdouglass/anaconda3/lib/python3.5/site-packages/matplotlib/backend_bases.py", > line 2232, in print_figure > **kwargs) File > "/home/kmdouglass/anaconda3/lib/python3.5/site-packages/matplotlib/backends/backend_agg.py", > line 519, in print_raw > fileobj.write(renderer._renderer.buffer_rgba())BrokenPipeError: [Errno 32] > Broken pipe* > > I'm using Anaconda/Python 3.5 with matplotlib 1.5.1. I installed FFmpeg > 3.0 in Debian Jessie by compiling FFmpeg from source into a dpkg according > to these instructions: > http://superuser.com/questions/286675/how-to-install-ffmpeg-on-debian I > also have Debian packages x264 and libx264-142 installed. > > > > ------------------------------------------------------------------------------ > Site24x7 APM Insight: Get Deep Visibility into Application Performance > APM + Mobile APM + RUM: Monitor 3 App instances at just 35ドル/Month > Monitor end-to-end web transactions and take corrective actions now > Troubleshoot faster and improve end-user experience. Signup Now! > http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140 > _______________________________________________ > Matplotlib-users mailing list > Mat...@li... > https://lists.sourceforge.net/lists/listinfo/matplotlib-users > > -- Ryan May
Dear colleagues, Thanks for the quick feedback. I've installed the "faulthandler" package, added it to the import and enabled it with faulthandler.enable(). Below the console trace of the test using the pcolormesh function and the traceback information: python test3.py Fatal Python error: Segmentation fault Current thread 0x000003ffa45f7710 (most recent call first): File "/usr/lib64/python2.7/site-packages/matplotlib/collections.py", line 1877 in draw File "/usr/lib64/python2.7/site-packages/matplotlib/artist.py", line 61 in draw_wrapper File "/usr/lib64/python2.7/site-packages/matplotlib/axes/_base.py", line 2324 in draw File "/usr/lib64/python2.7/site-packages/matplotlib/artist.py", line 61 in draw_wrapper File "/usr/lib64/python2.7/site-packages/matplotlib/figure.py", line 1159 in draw File "/usr/lib64/python2.7/site-packages/matplotlib/artist.py", line 61 in draw_wrapper File "/usr/lib64/python2.7/site-packages/matplotlib/backends/backend_agg.py", line 474 in draw File "/usr/lib64/python2.7/site-packages/matplotlib/backends/backend_agg.py", line 527 in print_png File "/usr/lib64/python2.7/site-packages/matplotlib/backend_bases.py", line 2232 in print_figure File "/usr/lib64/python2.7/site-packages/matplotlib/figure.py", line 1565 in savefig File "/usr/lib64/python2.7/site-packages/matplotlib/pyplot.py", line 688 in savefig File "test3.py", line 47 in <module> Segmentation fault Hope this information helps to circle the issue. Regards, Claude Falbriard Certified IT Specialist L2 - Middleware Phone: 55-13-99662-5703 | Mobile: 55-13-98117-3316 E-mail: cl...@br... From: Benjamin Root <ben...@gm...> To: Claude Falbriard/Brazil/IBM@IBMBR Cc: Matplotlib Users <mat...@li...> Date: 24/02/2016 17:35 Subject: Re: [Matplotlib-users] Matplotlib 1.5.1 - Function pcolormesh throws Segmentation Fault Sorry, forgot to post the link: https://pypi.python.org/pypi/faulthandler/ On Wed, Feb 24, 2016 at 3:33 PM, Benjamin Root <ben...@gm...> wrote: Could you try using faulthandler and post the traceback please? That'll help us isolate the problem better. Ben Root On Wed, Feb 24, 2016 at 3:04 PM, Claude Falbriard <cl...@br...> wrote: Dear colleagues, I've done a build from source of latest Matplotlib package and deployed it at our IBM z13 machine (s390x). It uses the current release 1.5.1. During the unit tests I found an issue with a test case from NOAA which uses a pcolormesh draw function with basemap. Example 2: Plot data from an NWW3 GRiB2 file - [ here: http://polar.ncep.noaa.gov/waves/examples/usingpython.shtml] The following line is causing a Segmentation fault error even when adding an 8GB swap memory to the process: cs = m.pcolormesh(x,y,data,shading='flat',cmap=plt.cm.jet) I also tryed to execute other, similar samples that use pcolormesh, but receiving the same error. Is this a known issue or might it be be related to the memory environment ? Any hints how to debug this error? Regards, Claude Falbriard Certified IT Specialist L2 - Middleware Phone:55-13-99662-5703 | Mobile:55-13-98117-3316 E-mail: cl...@br... ------------------------------------------------------------------------------ Site24x7 APM Insight: Get Deep Visibility into Application Performance APM + Mobile APM + RUM: Monitor 3 App instances at just 35ドル/Month Monitor end-to-end web transactions and take corrective actions now Troubleshoot faster and improve end-user experience. Signup Now! http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140 _______________________________________________ Matplotlib-users mailing list Mat...@li... https://lists.sourceforge.net/lists/listinfo/matplotlib-users
Sorry, forgot to post the link: https://pypi.python.org/pypi/faulthandler/ On Wed, Feb 24, 2016 at 3:33 PM, Benjamin Root <ben...@gm...> wrote: > Could you try using faulthandler and post the traceback please? That'll > help us isolate the problem better. > > Ben Root > > On Wed, Feb 24, 2016 at 3:04 PM, Claude Falbriard <cl...@br...> > wrote: > >> Dear colleagues, >> >> I've done a build from source of latest *Matplotlib* package and >> deployed it at our IBM z13 machine (s390x). It uses the current release >> 1.5.1. >> During the unit tests I found an issue with a test case from NOAA which >> uses a* pcolormesh* draw function with *basemap*. >> >> Example 2: Plot data from an NWW3 GRiB2 file - [ here: >> *http://polar.ncep.noaa.gov/waves/examples/usingpython.shtml* >> <http://polar.ncep.noaa.gov/waves/examples/usingpython.shtml>*]* >> >> The following line is causing a *Segmentation fault* error even when >> adding an 8GB swap memory to the process: >> >> cs = m.pcolormesh(x,y,data,shading='flat',cmap=plt.cm.jet) >> >> I also tryed to execute other, similar samples that use pcolormesh, but >> receiving the same error. Is this a known issue or might it be be related >> to the memory environment ? Any hints how to debug this error? >> >> Regards, >> >> *Claude Falbriard* >> Certified IT Specialist L2 - Middleware >> ------------------------------ >> *Phone:*55-13-99662-5703 | *Mobile:*55-13-98117-3316 >> *E-mail:* *cl...@br...* <cl...@br...> >> >> >> >> ------------------------------------------------------------------------------ >> Site24x7 APM Insight: Get Deep Visibility into Application Performance >> APM + Mobile APM + RUM: Monitor 3 App instances at just 35ドル/Month >> Monitor end-to-end web transactions and take corrective actions now >> Troubleshoot faster and improve end-user experience. Signup Now! >> http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140 >> _______________________________________________ >> Matplotlib-users mailing list >> Mat...@li... >> https://lists.sourceforge.net/lists/listinfo/matplotlib-users >> >> >
Hi all, I would like to use matplotlib's animation API to create a movie that can be embedded into an html5 video tag. To do this, I am following a couple 2012 blog posts from Jake VanderPlas: http://jakevdp.github.io/blog/2012/08/18/matplotlib-animation-tutorial/ and http://jakevdp.github.io/blog/2013/05/12/embedding-matplotlib-animations/ My understanding is that I need to use the x264 codec to do this. Unfortunately, I get a Broken Pipe Error when running the basic example below. I get the same error when calling the animation.to_html5_video() method. Does anyone have an idea about why I'm getting the Broken Pipe error? Do I really need the x264 codec to embed matplotlib animations into html? Thanks! Kyle *Example code:* *import numpy as np* *import matplotlib.pyplot as plt* *from matplotlib import animate* *fig = plt.figure()ax = plt.axes(xlim = (0, 2), ylim = (-2, 2))line, = ax.plot([], [], linewidth = 2)# initialization function: plot the background of each framedef init(): line.set_data([], []) return line,# animation function. This is called sequentiallydef animate(i): x = np.linspace(0, 2, 1000) y = np.sin(2 * np.pi * (x - 0.01 * i)) line.set_data(x, y) return line,# call the animatoranim = animation.FuncAnimation(fig, animate, init_func=init, frames=200, interval=20, blit=True)myWriter = animation.FFMpegWriter(fps = 30, extra_args=['-vcodec', 'libx264'])anim.save('basic_animation.mp4', writer = myWriter)* *plt.show()* *Traceback:* *Traceback (most recent call last): File "test.py", line 26, in <module> anim.save('basic_animation.mp4', writer = myWriter) File "/home/kmdouglass/anaconda3/lib/python3.5/site-packages/matplotlib/animation.py", line 810, in save writer.grab_frame(**savefig_kwargs) File "/home/kmdouglass/anaconda3/lib/python3.5/site-packages/matplotlib/animation.py", line 230, in grab_frame dpi=self.dpi, **savefig_kwargs) File "/home/kmdouglass/anaconda3/lib/python3.5/site-packages/matplotlib/figure.py", line 1565, in savefig self.canvas.print_figure(*args, **kwargs) File "/home/kmdouglass/anaconda3/lib/python3.5/site-packages/matplotlib/backends/backend_qt5agg.py", line 196, in print_figure FigureCanvasAgg.print_figure(self, *args, **kwargs) File "/home/kmdouglass/anaconda3/lib/python3.5/site-packages/matplotlib/backend_bases.py", line 2232, in print_figure **kwargs) File "/home/kmdouglass/anaconda3/lib/python3.5/site-packages/matplotlib/backends/backend_agg.py", line 519, in print_raw fileobj.write(renderer._renderer.buffer_rgba())BrokenPipeError: [Errno 32] Broken pipe* I'm using Anaconda/Python 3.5 with matplotlib 1.5.1. I installed FFmpeg 3.0 in Debian Jessie by compiling FFmpeg from source into a dpkg according to these instructions: http://superuser.com/questions/286675/how-to-install-ffmpeg-on-debian I also have Debian packages x264 and libx264-142 installed.
Could you try using faulthandler and post the traceback please? That'll help us isolate the problem better. Ben Root On Wed, Feb 24, 2016 at 3:04 PM, Claude Falbriard <cl...@br...> wrote: > Dear colleagues, > > I've done a build from source of latest *Matplotlib* package and > deployed it at our IBM z13 machine (s390x). It uses the current release > 1.5.1. > During the unit tests I found an issue with a test case from NOAA which > uses a* pcolormesh* draw function with *basemap*. > > Example 2: Plot data from an NWW3 GRiB2 file - [ here: > *http://polar.ncep.noaa.gov/waves/examples/usingpython.shtml* > <http://polar.ncep.noaa.gov/waves/examples/usingpython.shtml>*]* > > The following line is causing a *Segmentation fault* error even when > adding an 8GB swap memory to the process: > > cs = m.pcolormesh(x,y,data,shading='flat',cmap=plt.cm.jet) > > I also tryed to execute other, similar samples that use pcolormesh, but > receiving the same error. Is this a known issue or might it be be related > to the memory environment ? Any hints how to debug this error? > > Regards, > > *Claude Falbriard* > Certified IT Specialist L2 - Middleware > ------------------------------ > *Phone:*55-13-99662-5703 | *Mobile:*55-13-98117-3316 > *E-mail:* *cl...@br...* <cl...@br...> > > > > ------------------------------------------------------------------------------ > Site24x7 APM Insight: Get Deep Visibility into Application Performance > APM + Mobile APM + RUM: Monitor 3 App instances at just 35ドル/Month > Monitor end-to-end web transactions and take corrective actions now > Troubleshoot faster and improve end-user experience. Signup Now! > http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140 > _______________________________________________ > Matplotlib-users mailing list > Mat...@li... > https://lists.sourceforge.net/lists/listinfo/matplotlib-users > >
Dear colleagues, I've done a build from source of latest Matplotlib package and deployed it at our IBM z13 machine (s390x). It uses the current release 1.5.1. During the unit tests I found an issue with a test case from NOAA which uses a pcolormesh draw function with basemap. Example 2: Plot data from an NWW3 GRiB2 file - [ here: http://polar.ncep.noaa.gov/waves/examples/usingpython.shtml ] The following line is causing a Segmentation fault error even when adding an 8GB swap memory to the process: cs = m.pcolormesh(x,y,data,shading='flat',cmap=plt.cm.jet) I also tryed to execute other, similar samples that use pcolormesh, but receiving the same error. Is this a known issue or might it be be related to the memory environment ? Any hints how to debug this error? Regards, Claude Falbriard Certified IT Specialist L2 - Middleware Phone: 55-13-99662-5703 | Mobile: 55-13-98117-3316 E-mail: cl...@br...