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
(12) |
3
(7) |
4
(23) |
5
(5) |
6
(7) |
7
(4) |
|
8
(7) |
9
(25) |
10
(17) |
11
(25) |
12
(11) |
13
(8) |
14
(6) |
|
15
(1) |
16
(22) |
17
(11) |
18
(12) |
19
(22) |
20
(32) |
21
(9) |
|
22
(4) |
23
(16) |
24
(5) |
25
(9) |
26
(26) |
27
(21) |
28
(14) |
|
29
(6) |
30
(8) |
31
(4) |
|
|
|
|
|
From: Benjamin R. <ben...@ou...> - 2010-08-29 18:04:02
|
On Sun, Aug 29, 2010 at 6:29 AM, xyz <mi...@op...> wrote: > On 29/08/10 17:28, Eric Firing wrote: > > On 08/28/2010 06:40 PM, xyz wrote: > >> Hello, > >> If I use autoscale_view than: > >> * plt.text appears outside x and y coordinates > >> * and the coordinates starts do not from 0 whereas I use ax.set_xlim(0) > >> and ax.set_ylim(0) > >> > >> What did I wrong? > > The call to autoscale_view overrides the earlier calls to set_xlim and > > set_ylim. There is no built-in mechanism for autoscaling only the upper > > limit, and holding the lower limit fixed. You could make such a > > mechanism by writing a custom Locator, but it may make more sense to > > calculate the upper limit directly in your code based on your data, and > > then use set_xlim and set_ylim to set both ends of each axis. > > > > Eric > > > > Thank you for your answer. However, I do not how to calculate the upper > limit directly from my code based on my data, and then use set_xlim and > set_ylim to set both ends of each axis. Could you show me please how to > do it? > > Thank you in advance. > > You could try: maxy = max(max(y1), max(y2)) maxx = max(x) ax.set_xlim((0.0, maxx)) ax.set_ylim((0.0, maxy)) I hope that helps, Ben Root |
|
From: xyz <mi...@op...> - 2010-08-29 11:29:51
|
On 29/08/10 17:28, Eric Firing wrote:
> On 08/28/2010 06:40 PM, xyz wrote:
>> Hello,
>> If I use autoscale_view than:
>> * plt.text appears outside x and y coordinates
>> * and the coordinates starts do not from 0 whereas I use ax.set_xlim(0)
>> and ax.set_ylim(0)
>>
>> What did I wrong?
> The call to autoscale_view overrides the earlier calls to set_xlim and
> set_ylim. There is no built-in mechanism for autoscaling only the upper
> limit, and holding the lower limit fixed. You could make such a
> mechanism by writing a custom Locator, but it may make more sense to
> calculate the upper limit directly in your code based on your data, and
> then use set_xlim and set_ylim to set both ends of each axis.
>
> Eric
>
Thank you for your answer. However, I do not how to calculate the upper
limit directly from my code based on my data, and then use set_xlim and
set_ylim to set both ends of each axis. Could you show me please how to
do it?
Thank you in advance.
from pylab import *
import matplotlib.pyplot as plt
x = [1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19,
20, 21, 22, 23, 24, 25, 26, 27, 28, 29]
y1 = [20, 24, 8, 4, 12, 22, 31, 25, 15, 28, 12, 27, 22, 22, 27, 14, 32,
28, 8, 17, 2, 8, 29, 13, 14, 20, 11, 28, 8]
y2= [2, 32, 28, 1, 22, 11, 14, 27, 3, 31, 12, 20, 32, 24, 24, 16, 7, 10,
12, 11, 3, 32, 10, 20, 14, 14, 3, 25, 14]
point_labels1 = ['A=1', 'A=1', 'A=1', 'A=1', 'A=1', 'A=1', 'A=1', 'A=1',
'A=1', 'A=1', 'A=1', 'A=1', 'A=1', 'A=1', 'A=1', 'A=1', 'A=1', 'A=1',
'A=1', 'A=1', 'A=1', 'A=1', 'A=1', 'A=1', 'A=1', 'A=1', 'A=1', 'A=1',
'A=1']
point_labels2 = ['B=1', 'B=1', 'B=1', 'B=1', 'B=1', 'B=1', 'B=1', 'B=1',
'B=1', 'B=1', 'B=1', 'B=1', 'B=1', 'B=1', 'B=1', 'B=1', 'B=1', 'B=1',
'B=1', 'B=1', 'B=1', 'B=1', 'B=1', 'B=1', 'B=1', 'B=1', 'B=1', 'B=1',
'B=1']
fig = plt.figure()
ax = fig.add_subplot(111)
ax.set_title('The red point should be on the path')
plt.plot(x, y1, 'bo', x, y2, 'go')
ax.grid(True)
ax.set_xlim(0.0)
ax.set_ylim(0.0)
fig.autofmt_xdate()
plt.xticks(range(0, 40, 1))
plt.yticks(range(0, 40, 1))
plt.xlabel('Longitude')
plt.ylabel('Latitude')
plt.legend(('Model length', 'Data length'),
'best', shadow=True, fancybox=True)
for i, label in enumerate(y1):
plt.text (x[i], y1[i]+0.2, label,
horizontalalignment='center' )
for i, label in enumerate(y2):
plt.text (x[i], y2[i]+0.2, label,
horizontalalignment='center' )
ax.autoscale_view()
plt.savefig('test.png')
plt.show()
|
|
From: xyz <mi...@op...> - 2010-08-29 11:22:16
|
On 29/08/10 17:28, Eric Firing wrote:
> On 08/28/2010 06:40 PM, xyz wrote:
>
>> Hello,
>> If I use autoscale_view than:
>> * plt.text appears outside x and y coordinates
>> * and the coordinates starts do not from 0 whereas I use ax.set_xlim(0)
>> and ax.set_ylim(0)
>>
>> What did I wrong?
>>
> The call to autoscale_view overrides the earlier calls to set_xlim and
> set_ylim. There is no built-in mechanism for autoscaling only the upper
> limit, and holding the lower limit fixed. You could make such a
> mechanism by writing a custom Locator, but it may make more sense to
> calculate the upper limit directly in your code based on your data, and
> then use set_xlim and set_ylim to set both ends of each axis.
>
> Eric
>
>
Thank you for your answer. However, I do not how to calculate the upper
limit directly from my code based on my data, and then use set_xlim and
set_ylim to set both ends of each axis. Could you show me please how to
do it?
Thank you in advance.
from pylab import *
import matplotlib.pyplot as plt
x = [1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19,
20, 21, 22, 23, 24, 25, 26, 27, 28, 29]
y1 = [20, 24, 8, 4, 12, 22, 31, 25, 15, 28, 12, 27, 22, 22, 27, 14, 32,
28, 8, 17, 2, 8, 29, 13, 14, 20, 11, 28, 8]
y2= [2, 32, 28, 1, 22, 11, 14, 27, 3, 31, 12, 20, 32, 24, 24, 16, 7, 10,
12, 11, 3, 32, 10, 20, 14, 14, 3, 25, 14]
point_labels1 = ['A=1', 'A=1', 'A=1', 'A=1', 'A=1', 'A=1', 'A=1', 'A=1',
'A=1', 'A=1', 'A=1', 'A=1', 'A=1', 'A=1', 'A=1', 'A=1', 'A=1', 'A=1',
'A=1', 'A=1', 'A=1', 'A=1', 'A=1', 'A=1', 'A=1', 'A=1', 'A=1', 'A=1', 'A=1']
point_labels2 = ['B=1', 'B=1', 'B=1', 'B=1', 'B=1', 'B=1', 'B=1', 'B=1',
'B=1', 'B=1', 'B=1', 'B=1', 'B=1', 'B=1', 'B=1', 'B=1', 'B=1', 'B=1',
'B=1', 'B=1', 'B=1', 'B=1', 'B=1', 'B=1', 'B=1', 'B=1', 'B=1', 'B=1', 'B=1']
fig = plt.figure()
ax = fig.add_subplot(111)
ax.set_title('The red point should be on the path')
plt.plot(x, y1, 'bo', x, y2, 'go')
ax.grid(True)
ax.set_xlim(0.0)
ax.set_ylim(0.0)
fig.autofmt_xdate()
plt.xticks(range(0, 40, 1))
plt.yticks(range(0, 40, 1))
plt.xlabel('Longitude')
plt.ylabel('Latitude')
plt.legend(('Model length', 'Data length'),
'best', shadow=True, fancybox=True)
for i, label in enumerate(y1):
plt.text (x[i], y1[i]+0.2, label,
horizontalalignment='center' )
for i, label in enumerate(y2):
plt.text (x[i], y2[i]+0.2, label,
horizontalalignment='center' )
ax.autoscale_view()
plt.savefig('test.png')
plt.show()
|
|
From: Eric F. <ef...@ha...> - 2010-08-29 07:29:01
|
On 08/28/2010 06:40 PM, xyz wrote:
> Hello,
> If I use autoscale_view than:
> * plt.text appears outside x and y coordinates
> * and the coordinates starts do not from 0 whereas I use ax.set_xlim(0)
> and ax.set_ylim(0)
>
> What did I wrong?
The call to autoscale_view overrides the earlier calls to set_xlim and
set_ylim. There is no built-in mechanism for autoscaling only the upper
limit, and holding the lower limit fixed. You could make such a
mechanism by writing a custom Locator, but it may make more sense to
calculate the upper limit directly in your code based on your data, and
then use set_xlim and set_ylim to set both ends of each axis.
Eric
>
> from pylab import *
> import matplotlib.pyplot as plt
>
> x = [1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19,
> 20, 21, 22, 23, 24, 25, 26, 27, 28, 29]
> y1 = [20, 24, 8, 4, 12, 22, 31, 25, 15, 28, 12, 27, 22, 22, 27, 14, 32,
> 28, 8, 17, 2, 8, 29, 13, 14, 20, 11, 28, 8]
> y2= [2, 32, 28, 1, 22, 11, 14, 27, 3, 31, 12, 20, 32, 24, 24, 16, 7, 10,
> 12, 11, 3, 32, 10, 20, 14, 14, 3, 25, 14]
> point_labels1 = ['A=1', 'A=1', 'A=1', 'A=1', 'A=1', 'A=1', 'A=1', 'A=1',
> 'A=1', 'A=1', 'A=1', 'A=1', 'A=1', 'A=1', 'A=1', 'A=1', 'A=1', 'A=1',
> 'A=1', 'A=1', 'A=1', 'A=1', 'A=1', 'A=1', 'A=1', 'A=1', 'A=1', 'A=1', 'A=1']
> point_labels2 = ['B=1', 'B=1', 'B=1', 'B=1', 'B=1', 'B=1', 'B=1', 'B=1',
> 'B=1', 'B=1', 'B=1', 'B=1', 'B=1', 'B=1', 'B=1', 'B=1', 'B=1', 'B=1',
> 'B=1', 'B=1', 'B=1', 'B=1', 'B=1', 'B=1', 'B=1', 'B=1', 'B=1', 'B=1', 'B=1']
>
> fig = plt.figure()
> ax = fig.add_subplot(111)
>
> ax.set_title('The red point should be on the path')
>
> plt.plot(x, y1, 'bo', x, y2, 'go')
> ax.grid(True)
> ax.set_xlim(0.0)
> ax.set_ylim(0.0)
>
> fig.autofmt_xdate()
>
> plt.xticks(range(0, 40, 1))
>
> plt.yticks(range(0, 40, 1))
> plt.xlabel('Longitude')
> plt.ylabel('Latitude')
> plt.legend(('Model length', 'Data length'),
> 'best', shadow=True, fancybox=True)
>
> for i, label in enumerate(y1):
> plt.text (x[i], y1[i]+0.2, label,
> horizontalalignment='center' )
>
> for i, label in enumerate(y2):
> plt.text (x[i], y2[i]+0.2, label,
> horizontalalignment='center' )
>
>
> ax.autoscale_view()
> plt.savefig('test.png')
> plt.show()
|
|
From: xyz <mi...@op...> - 2010-08-29 04:41:08
|
Hello,
If I use autoscale_view than:
* plt.text appears outside x and y coordinates
* and the coordinates starts do not from 0 whereas I use ax.set_xlim(0)
and ax.set_ylim(0)
What did I wrong?
from pylab import *
import matplotlib.pyplot as plt
x = [1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19,
20, 21, 22, 23, 24, 25, 26, 27, 28, 29]
y1 = [20, 24, 8, 4, 12, 22, 31, 25, 15, 28, 12, 27, 22, 22, 27, 14, 32,
28, 8, 17, 2, 8, 29, 13, 14, 20, 11, 28, 8]
y2= [2, 32, 28, 1, 22, 11, 14, 27, 3, 31, 12, 20, 32, 24, 24, 16, 7, 10,
12, 11, 3, 32, 10, 20, 14, 14, 3, 25, 14]
point_labels1 = ['A=1', 'A=1', 'A=1', 'A=1', 'A=1', 'A=1', 'A=1', 'A=1',
'A=1', 'A=1', 'A=1', 'A=1', 'A=1', 'A=1', 'A=1', 'A=1', 'A=1', 'A=1',
'A=1', 'A=1', 'A=1', 'A=1', 'A=1', 'A=1', 'A=1', 'A=1', 'A=1', 'A=1', 'A=1']
point_labels2 = ['B=1', 'B=1', 'B=1', 'B=1', 'B=1', 'B=1', 'B=1', 'B=1',
'B=1', 'B=1', 'B=1', 'B=1', 'B=1', 'B=1', 'B=1', 'B=1', 'B=1', 'B=1',
'B=1', 'B=1', 'B=1', 'B=1', 'B=1', 'B=1', 'B=1', 'B=1', 'B=1', 'B=1', 'B=1']
fig = plt.figure()
ax = fig.add_subplot(111)
ax.set_title('The red point should be on the path')
plt.plot(x, y1, 'bo', x, y2, 'go')
ax.grid(True)
ax.set_xlim(0.0)
ax.set_ylim(0.0)
fig.autofmt_xdate()
plt.xticks(range(0, 40, 1))
plt.yticks(range(0, 40, 1))
plt.xlabel('Longitude')
plt.ylabel('Latitude')
plt.legend(('Model length', 'Data length'),
'best', shadow=True, fancybox=True)
for i, label in enumerate(y1):
plt.text (x[i], y1[i]+0.2, label,
horizontalalignment='center' )
for i, label in enumerate(y2):
plt.text (x[i], y2[i]+0.2, label,
horizontalalignment='center' )
ax.autoscale_view()
plt.savefig('test.png')
plt.show()
|
|
From: Jae-Joon L. <lee...@gm...> - 2010-08-29 00:29:28
|
I just remembered that there has been a bug in old version of matplotlib that annotation_clip parameter is not correctly set when given as a keyword parameter of "annotate" function. The bug has been fixed. http://www.mail-archive.com/mat...@li.../msg15068.html As a workaround, use ann = pylab.annotate('',(-1,3.1),(0,3.1),va='center',ha='center', arrowprops=dict(arrowstyle='<->')) ann.set_annotation_clip(False) Regards, -JJ On Sun, Aug 29, 2010 at 5:59 AM, Stan Schymanski <ss...@bg...> wrote: > Hi JJ, > > Thanks for the advice. However, the annotation_clip=False addition does not > make a difference to me. I am using Matplotlib from within Sage, though; not > sure if this makes it behave differently. > > Cheers > Stan > > On 8/28/10 5:09 PM, Jae-Joon Lee wrote: >> >> I think this change has been there for a while. >> For recent versions of matplotlib, the default behavior of annotate is >> that, when xycoords=="data", the arrow is drawn only when the >> annotated point is inside the axes. >> To override this behavior, use annotation_clip keyword parameter. >> >> >> pylab.annotate('',(-1,3.1),(0,3.1),va='center',ha='center', >> arrowprops=dict(arrowstyle='<->'), annotation_clip=False) >> >> Regards, >> >> -JJ >> >> >> On Fri, Aug 27, 2010 at 9:21 PM, Stan Schymanski<ss...@bg...> >> wrote: >> >>> >>> Dear all, >>> >>> I don't know which update it was that broke it, but this used to work: >>> >>> import numpy >>> import pylab >>> pylab.clf() >>> fig = pylab.figure(1,figsize=(8,5)) >>> ax = fig.add_subplot(111, autoscale_on=False, xlim=(-1,5), >>> ylim=(-4,3)) >>> >>> t = numpy.arange(0.0, 5.0, 0.01) >>> s = numpy.cos(2*numpy.pi*t) >>> line, = ax.plot(t, s, lw=3, color='purple') >>> pylab.text(-0.5,3.2,'no data',ha='center') >>> >>> pylab.annotate('',(-1,3.1),(0,3.1),va='center',ha='center',arrowprops=dict(arrowstyle='<->')) >>> pylab.savefig('blah.png') >>> >>> This used to plot an arrow under the text 'no data' but above the main >>> plot. Now this arrow does not appear unless at least part of it is within >>> the plotting area. Change one of the '3.1' in the code above to, say, 3.0 >>> and the whole arrow is displayed. Is this a bug or is there a new way of >>> achieving what I want? >>> >>> Thanks for your help already! >>> >>> Cheers >>> Stan >>> >>> >>> >>> ------------------------------------------------------------------------------ >>> Sell apps to millions through the Intel(R) Atom(Tm) Developer Program >>> Be part of this innovative community and reach millions of netbook users >>> worldwide. Take advantage of special opportunities to increase revenue >>> and >>> speed time-to-market. Join now, and jumpstart your future. >>> http://p.sf.net/sfu/intel-atom-d2d >>> _______________________________________________ >>> Matplotlib-users mailing list >>> Mat...@li... >>> https://lists.sourceforge.net/lists/listinfo/matplotlib-users >>> >>> > > -- > ________________________________________ > > Stan Schymanski > Scientist > Max Planck Institute for Biogeochemistry > PO Box 10 01 64 > D-07701 Jena, Germany > > Phone: +49.3641.576264 > Fax: +49.3641.577274 > WWW: http://www.bgc-jena.mpg.de/~sschym > > Biospheric Theory and Modelling Group > http://www.bgc-jena.mpg.de/bgc-theory/ > _________________________________________ > > |