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
(12) |
2
(13) |
3
(14) |
4
(9) |
5
(9) |
6
(22) |
7
(17) |
8
(16) |
9
(19) |
10
(17) |
11
(6) |
12
|
13
(20) |
14
(21) |
15
(20) |
16
(10) |
17
(14) |
18
(3) |
19
(3) |
20
(12) |
21
(22) |
22
(26) |
23
(31) |
24
(26) |
25
(9) |
26
(4) |
27
(33) |
28
(15) |
29
(37) |
30
(26) |
|
|
From: Ng, E. <enr...@lm...> - 2009-04-16 19:48:03
|
I've been trying to figure out how to do this for a while. I need to make polar plots which go around clockwise and have 0deg on top (north) instead of on the side (east). How can this be done? |
From: Josh L. <jos...@gm...> - 2009-04-16 19:28:46
|
Jeff, Thanks for the speedy reply. Should a warning be raised then that my data (though in 2D form) is not 2D and therefore is invalid input? Cheers, Josh Lawrence Ph.D. Student Clemson University On Apr 16, 2009, at 2:53 PM, Jeff Whitaker wrote: > Josh Lawrence wrote: >> Greetings all, >> >> In using the function griddata in mlab.py, I think I have found a >> bug. The following line in mlab.py errors for me. >> I supply it an xi and yi that have shape (N,1). I have surface >> data, but I only care about the variation in one direction. In >> mlab, when it gets to this line (2956 in svn revision 7040): >> >> if min(xo[1:]-xo[0:-1]) < 0 or min(yo[1:]-yo[0:-1]) < 0: >> raise ValueError, 'output grid defined by xi,yi must >> be monotone increasing' >> >> the result is an error. That is, I get the following: >> >> ValueError: min() arg is an empty sequence >> >> A couple of things. First, if I make my variation in x to be 2 >> points (x = 0 for the case I'm interested in--so I just have both >> values of x be zero), I do not get this error and I believe the >> result works. So, it seems that there should be some handling of >> the case that there are only 1 point in either x or y direction. >> >> Second, is it better to use the builtin python function min, or >> should numpy.min be used instead? >> >> Cheers, >> >> Josh Lawrence >> Ph.D. Student >> Clemson University > > Josh: griddata currently only works for 2-D output grids. It may > be possible to modify it to work with 1-D data, but that was not the > original intent of the function. > > -Jeff > > -- > Jeffrey S. Whitaker Phone : (303)497-6313 > Meteorologist FAX : (303)497-6449 > NOAA/OAR/PSD R/PSD1 Email : Jef...@no... > 325 Broadway Office : Skaggs Research Cntr 1D-113 > Boulder, CO, USA 80303-3328 Web : http://tinyurl.com/5telg > |
From: Mark L. <lar...@gm...> - 2009-04-16 19:20:29
|
> I am not sure what you are asking -- could you elaborate? Sorry. I use matplotlib to create PNGs graphics for display on a web-page. I want to make the plots zoom-able. I'll use javascript to capture the pixel positions of the user's selected zoom region on the PNG plot. I'll then translate this into the coordinate system on the plot and redraw it with a new x, y range. I'm having trouble translating the initial axises into the pixel positions (essentially where they are on the PNG image). For example, I use the following code to map point positions from the coordinate system to pixel positions. I use an img map <MAP> to provide interaction with the actual lines. [CODE] lineObj = plt.plot(Xs,Ys,marker='o')[0] path, affine = lineObj._transformed_path.get_transformed_points_and_affine() path = affine.transform_path(path) for real,pixel in zip(lineObj.get_xydata(),path.vertices): ## write <AREA> tag for each point [/CODE] I'd like to get information similar to this for the axis of the plot. Thanks. |
From: Jeff W. <js...@fa...> - 2009-04-16 18:53:44
|
Josh Lawrence wrote: > Greetings all, > > In using the function griddata in mlab.py, I think I have found a bug. > The following line in mlab.py errors for me. > I supply it an xi and yi that have shape (N,1). I have surface data, > but I only care about the variation in one direction. In mlab, when it > gets to this line (2956 in svn revision 7040): > > if min(xo[1:]-xo[0:-1]) < 0 or min(yo[1:]-yo[0:-1]) < 0: > raise ValueError, 'output grid defined by xi,yi must be > monotone increasing' > > the result is an error. That is, I get the following: > > ValueError: min() arg is an empty sequence > > A couple of things. First, if I make my variation in x to be 2 points > (x = 0 for the case I'm interested in--so I just have both values of x > be zero), I do not get this error and I believe the result works. So, > it seems that there should be some handling of the case that there are > only 1 point in either x or y direction. > > Second, is it better to use the builtin python function min, or should > numpy.min be used instead? > > Cheers, > > Josh Lawrence > Ph.D. Student > Clemson University Josh: griddata currently only works for 2-D output grids. It may be possible to modify it to work with 1-D data, but that was not the original intent of the function. -Jeff -- Jeffrey S. Whitaker Phone : (303)497-6313 Meteorologist FAX : (303)497-6449 NOAA/OAR/PSD R/PSD1 Email : Jef...@no... 325 Broadway Office : Skaggs Research Cntr 1D-113 Boulder, CO, USA 80303-3328 Web : http://tinyurl.com/5telg |
From: John H. <jd...@gm...> - 2009-04-16 18:21:56
|
On Thu, Apr 16, 2009 at 1:10 PM, Mark Larsen <lar...@gm...> wrote: > MPL Users, > > How can I get the matched max and min pixel/coordinate positions of my > x and y axises? I am not sure what you are asking -- could you elaborate? JDH |
From: Josh L. <jos...@gm...> - 2009-04-16 18:15:29
|
Greetings all, In using the function griddata in mlab.py, I think I have found a bug. The following line in mlab.py errors for me. I supply it an xi and yi that have shape (N,1). I have surface data, but I only care about the variation in one direction. In mlab, when it gets to this line (2956 in svn revision 7040): if min(xo[1:]-xo[0:-1]) < 0 or min(yo[1:]-yo[0:-1]) < 0: raise ValueError, 'output grid defined by xi,yi must be monotone increasing' the result is an error. That is, I get the following: ValueError: min() arg is an empty sequence A couple of things. First, if I make my variation in x to be 2 points (x = 0 for the case I'm interested in--so I just have both values of x be zero), I do not get this error and I believe the result works. So, it seems that there should be some handling of the case that there are only 1 point in either x or y direction. Second, is it better to use the builtin python function min, or should numpy.min be used instead? Cheers, Josh Lawrence Ph.D. Student Clemson University |
From: Mark L. <lar...@gm...> - 2009-04-16 18:10:54
|
MPL Users, How can I get the matched max and min pixel/coordinate positions of my x and y axises? Thanks, LarsenMTL |
From: Pim S. <P.S...@st...> - 2009-04-16 10:00:29
|
Dear matplotlib users/developers, I recently noticed that the errorbar funciton in the pyplot module changed it's default setting to fmt="-". This is a bit strange since this function is primarily used to display individual data points with measurement errors, drawing a line connecting the datapoints is not a common procedure and normally only done with a fit to the data. I think it makes much more sense if the default behaviour was fmt="+". Kind regards, Pim Schellart |
From: Andres L. <and...@ut...> - 2009-04-16 09:30:28
|
Images, one is directly png and other converted from eps. Andres Andres Luhamaa wrote: > Hello! > Following example will give strange result in postscript output. It does > not happen, if I use imshow or contourf instead of pcolormesh and it > seems to happen only with log scale. > > Best regards, > Andres > > import numpy as np > import matplotlib > matplotlib.use( 'PS' ) > from mpl_toolkits.basemap import Basemap > import os > import pylab as plt > import matplotlib.colors as colors > m=Basemap(width=1500000,height=1000000,resolution='c',projection='stere',lon_0=\ > 17,lat_0=58) > # geogr coords for > points > rx=np.arange(18,22,0.1) > ry=np.arange(56,60,0.1) > RX,RY=np.meshgrid(rx,ry) > x,y=m(RX,RY) > # create data for > points > data=np.zeros([rx.size,ry.size]) > data[:10,:10]=1e3 > m.pcolormesh(x,y,data > ,norm=colors.LogNorm(vmin=50,vmax=17000.0) > ) > m.drawcoastlines() > m.drawcountries() > m.drawmapboundary() > plt.colorbar() > plt.savefig('mapproblem.eps') > > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by: > High Quality Requirements in a Collaborative Environment. > Download a free trial of Rational Requirements Composer Now! > http://p.sf.net/sfu/www-ibm-com > _______________________________________________ > Matplotlib-users mailing list > Mat...@li... > https://lists.sourceforge.net/lists/listinfo/matplotlib-users > > |
From: Evan M. <eva...@gm...> - 2009-04-16 00:01:01
|
Hi, I want to put arrows onto the contours of a contour plot, the direction will depend on whether the contour is positive/negative. Before I try to do it myself, has anybody written something to do that? Thanks, Evan |