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
(7) |
2
(8) |
|
3
(3) |
4
(5) |
5
(2) |
6
(3) |
7
(4) |
8
(11) |
9
(4) |
|
10
|
11
(8) |
12
(10) |
13
(16) |
14
(14) |
15
(13) |
16
(1) |
|
17
|
18
(8) |
19
(6) |
20
(13) |
21
(15) |
22
(5) |
23
(13) |
|
24
(2) |
25
(4) |
26
(1) |
27
(4) |
28
(8) |
29
(11) |
30
(5) |
|
31
(3) |
|
|
|
|
|
|
|
From: Benjamin R. <ben...@ou...> - 2011-07-19 16:31:21
|
On Tue, Jul 19, 2011 at 9:14 AM, Jakub Nowacki <j.s...@gm...>wrote: > Thanks for the answers. > > >> Jakub, if possible, could you test out the latest matplotlib in >> development on github? I have been working hard in this. If not, you >> could also always operate directly through the axis objects >> themselves, such as: ax.zaxis (although, you might have to do >> ax.w_zaxis). >> > > OK, I can use axis through w_*axis to control them. The function set_ticks > works(ish) in that case but the axes is for some reason flushed to the left > (it filled the image before) as can be seen in the enclosed image. This > behaviour has nothing to do with the ticks values nor the axis (brakes the > same for x, y and z axis). The selected ticks are updated though, just the > whole projection (?) brakes. > > Curious, I haven't encountered that before. Is it possible to include a code sample that reproduces the problem for you? > The below suggestion by José works correctly without the effect shown in > the image. > > > a1.w_yaxis.set_major_locator(**LinearLocator(5)) > a1.w_zaxis.set_major_locator(**LinearLocator(5)) > > As for the github version, I can try it out in some future but currently I > don't have time. Also installing new stuff into EPD is not necessary too > trivial. > > Fair enough. I am glad you found a solution that works for you. Ben Root |
|
From: Jakub N. <j.s...@gm...> - 2011-07-19 14:14:13
|
Thanks for the answers. > > Jakub, if possible, could you test out the latest matplotlib in > development on github? I have been working hard in this. If not, you > could also always operate directly through the axis objects > themselves, such as: ax.zaxis (although, you might have to do > ax.w_zaxis). OK, I can use axis through w_*axis to control them. The function set_ticks works(ish) in that case but the axes is for some reason flushed to the left (it filled the image before) as can be seen in the enclosed image. This behaviour has nothing to do with the ticks values nor the axis (brakes the same for x, y and z axis). The selected ticks are updated though, just the whole projection (?) brakes. The below suggestion by José works correctly without the effect shown in the image. a1.w_yaxis.set_major_locator(LinearLocator(5)) a1.w_zaxis.set_major_locator(LinearLocator(5)) As for the github version, I can try it out in some future but currently I don't have time. Also installing new stuff into EPD is not necessary too trivial. Thanks for the suggestions. Cheers, Jakub |
|
From: Benjamin R. <ben...@ou...> - 2011-07-19 14:13:22
|
On Tuesday, July 19, 2011, José Alexandre Nalon <na...@te...> wrote: > Hello, > > Em 19/07/2011, às 08:09, Jakub Nowacki escreveu: > >> But I've found that _nbins doesn't do >> anything (also, there is no zaxis object), set_zticks return an error >> 'AttributeError: 'Axes3DSubplot' object has no attribute 'set_zticks'' >> and set_x(y)ticks changes ticks of not 3d axis but 2d one. Is there any >> (other) way to influence the number of ticks? > > I don't know if that will help you, but I used the command below: > > a1.w_yaxis.set_major_locator(LinearLocator(5)) > a1.w_zaxis.set_major_locator(LinearLocator(5)) > > Notice that you are not using xaxis, yaxis or zaxis, these properties > do not exist and give you the attribute error you are getting. But, > adding w_ in front of the name of the axis it works perfectly. You > can use locators and formatters in this way. > > Also, notice that if you want to control axis limits, you should use > set_xlim3d, set_ylim3d and set_zlim3d. While these commands are a > little more cumbersome to use, I could get a lot of control over 3d > plots using them. > > Hope this helps! > Just a heads-up, this will no longer be necessary in the upcoming v1.1.0 release. They will still be valid, but not required. Ben Root |
|
From: José A. N. <na...@te...> - 2011-07-19 13:58:19
|
Hello, Em 19/07/2011, às 08:09, Jakub Nowacki escreveu: > But I've found that _nbins doesn't do > anything (also, there is no zaxis object), set_zticks return an error > 'AttributeError: 'Axes3DSubplot' object has no attribute 'set_zticks'' > and set_x(y)ticks changes ticks of not 3d axis but 2d one. Is there any > (other) way to influence the number of ticks? I don't know if that will help you, but I used the command below: a1.w_yaxis.set_major_locator(LinearLocator(5)) a1.w_zaxis.set_major_locator(LinearLocator(5)) Notice that you are not using xaxis, yaxis or zaxis, these properties do not exist and give you the attribute error you are getting. But, adding w_ in front of the name of the axis it works perfectly. You can use locators and formatters in this way. Also, notice that if you want to control axis limits, you should use set_xlim3d, set_ylim3d and set_zlim3d. While these commands are a little more cumbersome to use, I could get a lot of control over 3d plots using them. Hope this helps! --- José Alexandre Nalon na...@te... |
|
From: Benjamin R. <ben...@ou...> - 2011-07-19 13:27:33
|
On Tuesday, July 19, 2011, Jakub Nowacki <j.s...@gm...> wrote: > Dear All, > > I've found it impossible to get some control over ticks in a 3D plot > (Axes3D, using with projection='3d' option) in Matplotlib 1.0.1 (EPD > 7.1-1 linux 64-bit). Namely, I have one out of four subplots, that is 3D > and it has much to many ticks (tick labels to be exact), which makes > them unreadable (most of them overlay on one another, not mentioning > axis labels are covered as well). Usually in such situations I used > set_x(y)ticks with some values or ax.x(y)axis.get_major_locator()._nbins > if I just wanted a certain number. But I've found that _nbins doesn't do > anything (also, there is no zaxis object), set_zticks return an error > 'AttributeError: 'Axes3DSubplot' object has no attribute 'set_zticks'' > and set_x(y)ticks changes ticks of not 3d axis but 2d one. Is there any > (other) way to influence the number of ticks? > > Thanks for the help in advance. > > Best wishes, > > Jakub > Jakub, if possible, could you test out the latest matplotlib in development on github? I have been working hard in this. If not, you could also always operate directly through the axis objects themselves, such as: ax.zaxis (although, you might have to do ax.w_zaxis). Ben Root |
|
From: Jakub N. <j.s...@gm...> - 2011-07-19 11:09:29
|
Dear All, I've found it impossible to get some control over ticks in a 3D plot (Axes3D, using with projection='3d' option) in Matplotlib 1.0.1 (EPD 7.1-1 linux 64-bit). Namely, I have one out of four subplots, that is 3D and it has much to many ticks (tick labels to be exact), which makes them unreadable (most of them overlay on one another, not mentioning axis labels are covered as well). Usually in such situations I used set_x(y)ticks with some values or ax.x(y)axis.get_major_locator()._nbins if I just wanted a certain number. But I've found that _nbins doesn't do anything (also, there is no zaxis object), set_zticks return an error 'AttributeError: 'Axes3DSubplot' object has no attribute 'set_zticks'' and set_x(y)ticks changes ticks of not 3d axis but 2d one. Is there any (other) way to influence the number of ticks? Thanks for the help in advance. Best wishes, Jakub |