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
(5) |
2
(24) |
3
(2) |
4
|
5
(4) |
6
(1) |
7
(22) |
8
(9) |
9
(23) |
10
(6) |
11
|
12
(7) |
13
(17) |
14
(12) |
15
(10) |
16
(22) |
17
(11) |
18
(6) |
19
(11) |
20
(13) |
21
(10) |
22
(7) |
23
(7) |
24
(5) |
25
(3) |
26
(20) |
27
(17) |
28
(25) |
29
(16) |
30
(17) |
31
(8) |
Maybe I have reinvented the wheel, but I find the attached code snippet very useful. I have modified a bit the recipe at http://aspn.activestate.com/ASPN/Cookbook/Python/Recipe/65222 to be used in the following situation: You plot (interactively) something in a main program, which than works heavily. Normally, when the figure window gets obscured, it will not redraw. The attached code shows how to make a thread that periodically redraws the figure. r.
Hello, I am using the OO interface to plot some data in logarithmic y-scale. The data displayed are almost constant but not entirely, see the attached image. In order to see the details, I would like to do something like 'axis( 'image' )' for the yaxis. I have tried to play with axes.set_ylim(), axes.yaxis.set_ticks() but failed utterly. Can anyone help me? For linear scaling, there is no problem - the axes limits are well adjusted without any intervention. thanks, r.
This will give you a smooth line for your cumulative distribution function: x = randn(10000) y = sort(x) plot(y,linspace(0,1,10000)) Mark
I have two plots. first one is velocity data from servo controller (freq) - plant reciprocates back and forth so we got turn data in there as well second one is psd (power spectral density) so we can see where we got resonances etc. When we zoom in on on section of first plot (say the forward movement), I'd like to recalc the psd with only the data that's been zoomed in on. Everything kind of works except for somewhere to trigger from. I had thought of trying resize_event - however I cannot get this working- see other post. I played with button_release_event to get the code basically working, however that event occurs before the first graph gets resized, so the region I am calculating the psd on is wrong, maybe because I am using xlim = myAxis.get_xlim() to find the limits of the first graph (which hasn't been re-drawn yet) Is there some way I can hook the re-calc/draw of psd to the zooming of first graph? Previously with 2 plot commands, I have used subplot(212, sharex=p1), to hook the two graphs together on the xaxis however as the second graph is a psd I don't know how to hook the psd input data to the xaxis of the first graph. Thanks Steve
Richard Brown wrote: > Hi there, > > I'm pretty new to python; I'm in the process of switching from Matlab. > I do quite a bit of image processing in my research, and while > pylab/matplotlib seems to be a great plotting library, some of the > quirks seem just a little bit frustrating - I'm hoping for some > enlightenment :) > > When I use imshow or matshow to display an array, the points with > index (m, n) are displayed with the pixels centred at (0.5 + m, 0.5 + > n). Is there a setting somewhere to make it so that the centres of the > pixels are at the index values rather than their bottom left corners? > Or must I be always adding 0.5 to things to make them appear in the > right places? Coincidentally, a few days ago I made this change for matshow; I had made it in spy some time ago. I have so far left imshow alone; isn't its present behavior consistent with Matlab? That is not necessarily a good reason for leaving it the way it is, but it is reason for some caution. I suspect quite a few people may prefer it the way it is; let's see who responds, and what opinions are voiced. One way of maintaining compatibility (if it is indeed compatible now, and if this is judged desirable) would be to add a kwarg and/or rc option. But if there is a consensus that imshow should by default put index ticks at cell centers, then I will be happy to make that change. Eric > > Thanks, I appreciate any help > > Richard
Hi there, I'm pretty new to python; I'm in the process of switching from Matlab. I do quite a bit of image processing in my research, and while pylab/matplotlib seems to be a great plotting library, some of the quirks seem just a little bit frustrating - I'm hoping for some enlightenment :) When I use imshow or matshow to display an array, the points with index (m, n) are displayed with the pixels centred at (0.5 + m, 0.5 + n). Is there a setting somewhere to make it so that the centres of the pixels are at the index values rather than their bottom left corners? Or must I be always adding 0.5 to things to make them appear in the right places? Thanks, I appreciate any help Richard -- Richard Brown Ph.D. Candidate Dept. of Mechanical Engineering University of Canterbury, NZ
Trying to get resize event to work, but either I don't understand the definition of when resize_event should work, or it's broken. for example ======================= from matplotlib import pylab , numerix def GotResizeEvent( event ): print 'Resize event detected' def GotDrawEvent( event ): print 'Draw event detected' X = range(0, 200) Y = pylab.sin(X) r = pylab.plot(X,Y) pylab.connect( 'resize_event', GotResizeEvent) pylab.connect( 'draw_event', GotDrawEvent) pylab.show() ========================= Will only get draw_events as I zoom in on the data, never a resize event? I also get draw_events as I resize the window itself, but never a resize_event. So my question, .. what user activity triggers a resize event? Numerix Version: numpy 1.0 MatPlotLib Version: 0.87.7 Steve