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
|
3
(4) |
4
|
5
|
6
|
7
|
8
|
9
(4) |
10
(1) |
11
|
12
|
13
|
14
|
15
|
16
(4) |
17
(3) |
18
(3) |
19
|
20
|
21
|
22
|
23
|
24
(1) |
25
|
26
(1) |
27
|
28
(8) |
29
(4) |
30
(1) |
|
|
|
From: Benjamin R. <ben...@gm...> - 2015-09-10 03:09:01
|
What might be more generally useful is to make it easier to specify which coordinate system you wish some spec to apply to. To be frank, I can never keep the transform names straight, and it isn't possible to specify it at all in some places. On Sep 9, 2015 6:04 PM, "Thomas Robitaille" <tho...@gm...> wrote: > I managed to write an Axes sub-class to do this: > > https://gist.github.com/astrofrog/8d579ea83e578a9cdb99 > > Try running this then resize the figure and the margin between axes > and figure edge will stay constant. > > Is this something that would be useful to have in Matplotlib itself? I > could foresee something like: > > fig.add_axes([0.1, 0.1, 0.8, 0.8], preserve_absolute_margins=True) > > If this would be useful, I can open a pull request. > > Cheers, > Tom > > On 9 September 2015 at 23:29, Thomas Robitaille > <tho...@gm...> wrote: > > Thanks Eric - unfortunately I need to be able to resize the figure > > interactively and have the axes follow. > > > > So an alternative that would be equally useful for me would be to > > specify axes using add_subplot or add_axes but then essentially have > > an option to say that the distance to the edge of the figure should be > > preserved when resizing. In other words, I'm not too concerned about > > whether I specify the original axes position in relative units or in > > inches, but the important thing is that the distance to the edge of > > the figure stays constant in absolute terms. > > > > Is this something that would be easy to build as an Axes subclass? > > > > Cheers, > > Tom > > > > > > > > On 9 September 2015 at 23:12, Eric Firing <ef...@ha...> wrote: > >> On 2015/09/09 11:01 AM, Thomas Robitaille wrote: > >>> > >>> Hi everyone, > >>> > >>> I am interested in creating axes in an interactive figure where the > >>> distance from the spines of the axes to the figure edge are constant > >>> in absolute terms. > >>> > >>> To clarify what I mean, when using add_axes([0.1, 0.1, 0.8, 0.8]), the > >>> spines of the axes are always located a distance from the edge of the > >>> figure that is 10% of the size of the figure. However, in my case, > >>> since the font size is constant, I want to be able to say that the > >>> spines should always be e.g. 0.5" from the edge of the figure, which > >>> would avoid wasting space when making the figure larger. > >>> > >>> Is there a way to do this currently? > >> > >> > >> This is what I use for positioning in inches: > >> > >> def axes_inches(fig, rect, **kw): > >> """ > >> Wrapper for Figure.add_axes in which *rect* is given in inches. > >> The translation to normalized coordinates is done immediately > >> based on the present figsize. > >> > >> *rect* is left, bottom, width, height in inches > >> *kw* are passed to Figure.add_axes > >> > >> """ > >> > >> fw = fig.get_figwidth() > >> fh = fig.get_figheight() > >> l, b, w, h = rect > >> relrect = [l / fw, b / fh, w / fw, h / fh] > >> ax = fig.add_axes(relrect, **kw) > >> return ax > >> > >> Note, however, that this works correctly only if you don't change > figsize > >> after calling it, so maybe it is not what you are looking for. > >> > >> Eric > >> > >>> > >>> (I am aware of set_tight_layout which would result in something > >>> similar, but this is not what I am after - I would like to be able to > >>> specify the exact absolute distance from the figure edge) > >>> > >>> Thanks! > >>> Tom > >>> > >>> > >>> > ------------------------------------------------------------------------------ > >>> Monitor Your Dynamic Infrastructure at Any Scale With Datadog! > >>> Get real-time metrics from all of your servers, apps and tools > >>> in one place. > >>> SourceForge users - Click here to start your Free Trial of Datadog now! > >>> http://pubads.g.doubleclick.net/gampad/clk?id=241902991&iu=/4140 > >>> _______________________________________________ > >>> Matplotlib-users mailing list > >>> Mat...@li... > >>> https://lists.sourceforge.net/lists/listinfo/matplotlib-users > >>> > >> > > > ------------------------------------------------------------------------------ > Monitor Your Dynamic Infrastructure at Any Scale With Datadog! > Get real-time metrics from all of your servers, apps and tools > in one place. > SourceForge users - Click here to start your Free Trial of Datadog now! > http://pubads.g.doubleclick.net/gampad/clk?id=241902991&iu=/4140 > _______________________________________________ > Matplotlib-users mailing list > Mat...@li... > https://lists.sourceforge.net/lists/listinfo/matplotlib-users > |
From: Thomas R. <tho...@gm...> - 2015-09-09 22:02:22
|
I managed to write an Axes sub-class to do this: https://gist.github.com/astrofrog/8d579ea83e578a9cdb99 Try running this then resize the figure and the margin between axes and figure edge will stay constant. Is this something that would be useful to have in Matplotlib itself? I could foresee something like: fig.add_axes([0.1, 0.1, 0.8, 0.8], preserve_absolute_margins=True) If this would be useful, I can open a pull request. Cheers, Tom On 9 September 2015 at 23:29, Thomas Robitaille <tho...@gm...> wrote: > Thanks Eric - unfortunately I need to be able to resize the figure > interactively and have the axes follow. > > So an alternative that would be equally useful for me would be to > specify axes using add_subplot or add_axes but then essentially have > an option to say that the distance to the edge of the figure should be > preserved when resizing. In other words, I'm not too concerned about > whether I specify the original axes position in relative units or in > inches, but the important thing is that the distance to the edge of > the figure stays constant in absolute terms. > > Is this something that would be easy to build as an Axes subclass? > > Cheers, > Tom > > > > On 9 September 2015 at 23:12, Eric Firing <ef...@ha...> wrote: >> On 2015/09/09 11:01 AM, Thomas Robitaille wrote: >>> >>> Hi everyone, >>> >>> I am interested in creating axes in an interactive figure where the >>> distance from the spines of the axes to the figure edge are constant >>> in absolute terms. >>> >>> To clarify what I mean, when using add_axes([0.1, 0.1, 0.8, 0.8]), the >>> spines of the axes are always located a distance from the edge of the >>> figure that is 10% of the size of the figure. However, in my case, >>> since the font size is constant, I want to be able to say that the >>> spines should always be e.g. 0.5" from the edge of the figure, which >>> would avoid wasting space when making the figure larger. >>> >>> Is there a way to do this currently? >> >> >> This is what I use for positioning in inches: >> >> def axes_inches(fig, rect, **kw): >> """ >> Wrapper for Figure.add_axes in which *rect* is given in inches. >> The translation to normalized coordinates is done immediately >> based on the present figsize. >> >> *rect* is left, bottom, width, height in inches >> *kw* are passed to Figure.add_axes >> >> """ >> >> fw = fig.get_figwidth() >> fh = fig.get_figheight() >> l, b, w, h = rect >> relrect = [l / fw, b / fh, w / fw, h / fh] >> ax = fig.add_axes(relrect, **kw) >> return ax >> >> Note, however, that this works correctly only if you don't change figsize >> after calling it, so maybe it is not what you are looking for. >> >> Eric >> >>> >>> (I am aware of set_tight_layout which would result in something >>> similar, but this is not what I am after - I would like to be able to >>> specify the exact absolute distance from the figure edge) >>> >>> Thanks! >>> Tom >>> >>> >>> ------------------------------------------------------------------------------ >>> Monitor Your Dynamic Infrastructure at Any Scale With Datadog! >>> Get real-time metrics from all of your servers, apps and tools >>> in one place. >>> SourceForge users - Click here to start your Free Trial of Datadog now! >>> http://pubads.g.doubleclick.net/gampad/clk?id=241902991&iu=/4140 >>> _______________________________________________ >>> Matplotlib-users mailing list >>> Mat...@li... >>> https://lists.sourceforge.net/lists/listinfo/matplotlib-users >>> >> |
From: Thomas R. <tho...@gm...> - 2015-09-09 21:29:29
|
Thanks Eric - unfortunately I need to be able to resize the figure interactively and have the axes follow. So an alternative that would be equally useful for me would be to specify axes using add_subplot or add_axes but then essentially have an option to say that the distance to the edge of the figure should be preserved when resizing. In other words, I'm not too concerned about whether I specify the original axes position in relative units or in inches, but the important thing is that the distance to the edge of the figure stays constant in absolute terms. Is this something that would be easy to build as an Axes subclass? Cheers, Tom On 9 September 2015 at 23:12, Eric Firing <ef...@ha...> wrote: > On 2015/09/09 11:01 AM, Thomas Robitaille wrote: >> >> Hi everyone, >> >> I am interested in creating axes in an interactive figure where the >> distance from the spines of the axes to the figure edge are constant >> in absolute terms. >> >> To clarify what I mean, when using add_axes([0.1, 0.1, 0.8, 0.8]), the >> spines of the axes are always located a distance from the edge of the >> figure that is 10% of the size of the figure. However, in my case, >> since the font size is constant, I want to be able to say that the >> spines should always be e.g. 0.5" from the edge of the figure, which >> would avoid wasting space when making the figure larger. >> >> Is there a way to do this currently? > > > This is what I use for positioning in inches: > > def axes_inches(fig, rect, **kw): > """ > Wrapper for Figure.add_axes in which *rect* is given in inches. > The translation to normalized coordinates is done immediately > based on the present figsize. > > *rect* is left, bottom, width, height in inches > *kw* are passed to Figure.add_axes > > """ > > fw = fig.get_figwidth() > fh = fig.get_figheight() > l, b, w, h = rect > relrect = [l / fw, b / fh, w / fw, h / fh] > ax = fig.add_axes(relrect, **kw) > return ax > > Note, however, that this works correctly only if you don't change figsize > after calling it, so maybe it is not what you are looking for. > > Eric > >> >> (I am aware of set_tight_layout which would result in something >> similar, but this is not what I am after - I would like to be able to >> specify the exact absolute distance from the figure edge) >> >> Thanks! >> Tom >> >> >> ------------------------------------------------------------------------------ >> Monitor Your Dynamic Infrastructure at Any Scale With Datadog! >> Get real-time metrics from all of your servers, apps and tools >> in one place. >> SourceForge users - Click here to start your Free Trial of Datadog now! >> http://pubads.g.doubleclick.net/gampad/clk?id=241902991&iu=/4140 >> _______________________________________________ >> Matplotlib-users mailing list >> Mat...@li... >> https://lists.sourceforge.net/lists/listinfo/matplotlib-users >> > |
From: Thomas R. <tho...@gm...> - 2015-09-09 21:01:50
|
Hi everyone, I am interested in creating axes in an interactive figure where the distance from the spines of the axes to the figure edge are constant in absolute terms. To clarify what I mean, when using add_axes([0.1, 0.1, 0.8, 0.8]), the spines of the axes are always located a distance from the edge of the figure that is 10% of the size of the figure. However, in my case, since the font size is constant, I want to be able to say that the spines should always be e.g. 0.5" from the edge of the figure, which would avoid wasting space when making the figure larger. Is there a way to do this currently? (I am aware of set_tight_layout which would result in something similar, but this is not what I am after - I would like to be able to specify the exact absolute distance from the figure edge) Thanks! Tom |
From: Benjamin R. <ben...@gm...> - 2015-09-09 17:56:59
|
Thales, Sorry for the delay in responding. This mailing list has actually moved to https://mail.python.org/mailman/listinfo/matplotlib-users Let's start up a new thread there with this information, plus also which version of matplotlib you are using and which backend. Cheers! Ben Root On Wed, Aug 26, 2015 at 6:12 PM, Thales Maia <tha...@gm...> wrote: > Hello, > > I am migrating from octave to python and found matplotlib as an useful and > powerful resource. > I played with many animations examples and tried to build my own. > > The objective is to build a live plot from data coming from an arduino. > The serial is working perfect (I can receive and plot data without > problem). > > Unfortunately, when I resize my animation windows, I get curves > overlapped. > > I must use blit because I have 6 subplots. > > Please, check the attached files: > Python: > -> animationR00.py (main) > -> lib/ > -> AnalogPlot.py > -> RingBuffer.py > -> crc8.py > > Arduino: > Teste.cpp (main) > Teste.h > ComSerial.cpp > ComSerial.h > OneWire.cpp > OneWire.h > I appreciate any help. > - > Thales Alexandre Carvalho Maia > > > > ------------------------------------------------------------------------------ > > _______________________________________________ > Matplotlib-users mailing list > Mat...@li... > https://lists.sourceforge.net/lists/listinfo/matplotlib-users > > |
From: Mark V. <mar...@uc...> - 2015-09-03 21:04:09
|
This appears to be DPI dependent. Changing the last line of Richard's example to plt.savefig("grap.png") gives a PNG with a shadow similar to that generated by TkAgg. --Mark On 09/03/2015 01:17 PM, Sterling Smith wrote: > For those who wonder what he means: > on the left is TkAgg; on the right is png. > > -Sterling > > On Sep 3, 2015, at 1:13PM, Richard Stanton <st...@ha... > <mailto:st...@ha...>> wrote: > >> A quick follow-up: if I export to a jpg file, I get the same huge shadow. If I >> export to a PDF file, the shadow looks much more like it does on the screen. >> >> >>> On Sep 3, 2015, at 1:07 PM, Richard Stanton <st...@ha... >>> <mailto:st...@ha...>> wrote: >>> >>> I’m trying to create a pie chart for a presentation. If I turn on shadows, >>> they look fine on the screen (in an IPython notebook), but when I export the >>> file to a PNG file, the shadow is way larger, and looks pretty ugly. Is this >>> a bug? And is there a way to shrink the size of the shadow? >>> >>> Here’s some sample code that shows the problem: >>> >>> import matplotlib.pyplot as plt >>> numbers = [4380.0, 2474.0, 158] >>> explode=(0, 0, 0.5) >>> plt.pie(numbers, explode=explode,shadow=True) >>> plt.axis('equal') >>> plt.savefig(‘grap.png’, dpi=400) >>> >>> Thanks for any suggestions. >>> >>> By the way, I’m using Matplotlib version 1.4.3 with the Anaconda distribution >>> under OS X. >>> >>> Richard Stanton >> >> >> ------------------------------------------------------------------------------ >> Monitor Your Dynamic Infrastructure at Any Scale With Datadog! >> Get real-time metrics from all of your servers, apps and tools >> in one place. >> SourceForge users - Click here to start your Free Trial of Datadog now! >> http://pubads.g.doubleclick.net/gampad/clk?id=241902991&iu=/4140 >> _______________________________________________ >> Matplotlib-users mailing list >> Mat...@li... >> https://lists.sourceforge.net/lists/listinfo/matplotlib-users > > > > ------------------------------------------------------------------------------ > Monitor Your Dynamic Infrastructure at Any Scale With Datadog! > Get real-time metrics from all of your servers, apps and tools > in one place. > SourceForge users - Click here to start your Free Trial of Datadog now! > http://pubads.g.doubleclick.net/gampad/clk?id=241902991&iu=/4140 > > > > _______________________________________________ > Matplotlib-users mailing list > Mat...@li... > https://lists.sourceforge.net/lists/listinfo/matplotlib-users > |
From: Sterling S. <sm...@fu...> - 2015-09-03 20:50:40
|
For those who wonder what he means: on the left is TkAgg; on the right is png. -Sterling On Sep 3, 2015, at 1:13PM, Richard Stanton <st...@ha...> wrote: > A quick follow-up: if I export to a jpg file, I get the same huge shadow. If I export to a PDF file, the shadow looks much more like it does on the screen. > > >> On Sep 3, 2015, at 1:07 PM, Richard Stanton <st...@ha...> wrote: >> >> I’m trying to create a pie chart for a presentation. If I turn on shadows, they look fine on the screen (in an IPython notebook), but when I export the file to a PNG file, the shadow is way larger, and looks pretty ugly. Is this a bug? And is there a way to shrink the size of the shadow? >> >> Here’s some sample code that shows the problem: >> >> import matplotlib.pyplot as plt >> numbers = [4380.0, 2474.0, 158] >> explode=(0, 0, 0.5) >> plt.pie(numbers, explode=explode,shadow=True) >> plt.axis('equal') >> plt.savefig(‘grap.png’, dpi=400) >> >> Thanks for any suggestions. >> >> By the way, I’m using Matplotlib version 1.4.3 with the Anaconda distribution under OS X. >> >> Richard Stanton > > > ------------------------------------------------------------------------------ > Monitor Your Dynamic Infrastructure at Any Scale With Datadog! > Get real-time metrics from all of your servers, apps and tools > in one place. > SourceForge users - Click here to start your Free Trial of Datadog now! > http://pubads.g.doubleclick.net/gampad/clk?id=241902991&iu=/4140 > _______________________________________________ > Matplotlib-users mailing list > Mat...@li... > https://lists.sourceforge.net/lists/listinfo/matplotlib-users |
From: Richard S. <st...@ha...> - 2015-09-03 20:13:41
|
A quick follow-up: if I export to a jpg file, I get the same huge shadow. If I export to a PDF file, the shadow looks much more like it does on the screen. > On Sep 3, 2015, at 1:07 PM, Richard Stanton <st...@ha...> wrote: > > I’m trying to create a pie chart for a presentation. If I turn on shadows, they look fine on the screen (in an IPython notebook), but when I export the file to a PNG file, the shadow is way larger, and looks pretty ugly. Is this a bug? And is there a way to shrink the size of the shadow? > > Here’s some sample code that shows the problem: > > import matplotlib.pyplot as plt > numbers = [4380.0, 2474.0, 158] > explode=(0, 0, 0.5) > plt.pie(numbers, explode=explode,shadow=True) > plt.axis('equal') > plt.savefig(‘grap.png’, dpi=400) > > Thanks for any suggestions. > > By the way, I’m using Matplotlib version 1.4.3 with the Anaconda distribution under OS X. > > Richard Stanton |
From: Richard S. <st...@ha...> - 2015-09-03 20:07:42
|
I’m trying to create a pie chart for a presentation. If I turn on shadows, they look fine on the screen (in an IPython notebook), but when I export the file to a PNG file, the shadow is way larger, and looks pretty ugly. Is this a bug? And is there a way to shrink the size of the shadow? Here’s some sample code that shows the problem: import matplotlib.pyplot as plt numbers = [4380.0, 2474.0, 158] explode=(0, 0, 0.5) plt.pie(numbers, explode=explode,shadow=True) plt.axis('equal') plt.savefig(‘grap.png’, dpi=400) Thanks for any suggestions. By the way, I’m using Matplotlib version 1.4.3 with the Anaconda distribution under OS X. Richard Stanton |