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
(9) |
2
(1) |
3
(4) |
4
(4) |
5
(9) |
6
(5) |
7
(12) |
8
(5) |
9
(27) |
10
(10) |
11
(4) |
12
|
13
(6) |
14
(12) |
15
(16) |
16
(13) |
17
(9) |
18
(1) |
19
(2) |
20
(4) |
21
(9) |
22
(5) |
23
(2) |
24
(6) |
25
|
26
(1) |
27
(9) |
28
(7) |
29
(2) |
30
(9) |
|
|
On 06/08/2011 01:28 AM, Daniel Mader wrote: > Dear Eric, > > thanks again for your comment, I am aware that the script contained > both the individual colorbars and the common one. My comment in the > code was because the placement on the figure is somewhat cramped: That's what I suspected, so the main point of the modified version was using subplots_adjust to give more room at the bottom, and then shifting the bottom colorbar so that it was less cramped. Granted, this approach takes some fiddling; but if you are using subplots and care about appearance, then sooner or later you will probably benefit from subplots_adjust, a function/method which is probably not as well-known as it deserves to be. Eric > > ## doesn't really work :/ ## in what way? > cax = fig.add_axes([0.25, 0.06, 0.5, 0.02]) > fig.colorbar(im2, cax, orientation='horizontal') > > Ideally, I'd need to create a new subfig 313 with a much reduced height. > > Either way, you helped me a lot! > > > 2011年6月7日 Eric Firing<ef...@ha...>: >> On 06/07/2011 01:37 AM, Daniel Mader wrote: >>> >>> Hi Eric, >>> >>> >>> 2011年6月6日 Eric Firing<ef...@ha...>: >>>> >>>> It's not quite clear to me yet, but I assume you want to use a call to >>>> imshow with a different data set in the second subplot, but have the >>>> color scale and colorbar be identical to those in the first subplot. Is >>>> that correct? If so, all you need to do is use the same norm for both >>>> calls to imshow--that is, define a norm, set the limits you want on it, >>>> and supply it as a kwarg. >>> >>> thanks a lot, you helped me to work around my problem, see code below :) >>> >>>> Also, for this sort of comparison, sometimes it is more efficient to use >>>> a single colorbar for multiple panels, as in this example: >>>> >>>> >>>> http://matplotlib.sourceforge.net/examples/pylab_examples/multi_image.html >>> >>> Very nice example! It's a little too complex for me, though, with all >>> the calculations for the axes layout -- I prefer subplots :) However, >>> I think I have found a nice compromise: >> >> Attached is a slight modification, much simpler than the example above, but >> retaining the single colorbar. Alternatively, if you stick with the >> colorbar for each panel (which is sometimes clearer), it illustrates a >> slightly clearer way of handling the cmap and norm, explicitly using the >> same instance of each for both images. >> >> Eric >> >>> >>> import pylab >>> import matplotlib as mpl >>> >>> pylab.close('all') >>> >>> dat = pylab.array([[1,2,3,4],[5,6,7,8]]) >>> datT = dat/2 >>> >>> fig = pylab.figure() >>> >>> ax1 = fig.add_subplot(211) >>> ax1.set_title('raw data') >>> im1 = ax1.imshow(dat, interpolation='nearest', >>> cmap=mpl.cm.get_cmap('rainbow', 20)) >>> fig.colorbar(im1) >>> >>> ax2 = fig.add_subplot(212) >>> ax2.set_title('leveled') >>> im2 = ax2.imshow(datT, interpolation='nearest', >>> cmap=mpl.cm.get_cmap('rainbow', 20)) >>> ## apply norm: >>> norm = mpl.colors.Normalize(vmin=dat.min(), vmax=dat.max()) >>> im2.set_norm(norm) >>> fig.colorbar(im2) >>> >>> ## doesn't really work :/ >>> cax = fig.add_axes([0.25, 0.04, 0.5, 0.02]) >>> fig.colorbar(im2, cax, orientation='horizontal') >>> >>> pylab.show() >>> >>> Thanks a lot, >>> best regards, >>> >>> Daniel > > ------------------------------------------------------------------------------ > EditLive Enterprise is the world's most technically advanced content > authoring tool. Experience the power of Track Changes, Inline Image > Editing and ensure content is compliant with Accessibility Checking. > http://p.sf.net/sfu/ephox-dev2dev > _______________________________________________ > Matplotlib-users mailing list > Mat...@li... > https://lists.sourceforge.net/lists/listinfo/matplotlib-users
On Tue, Jun 7, 2011 at 5:16 PM, Shankararaman Ramakrishnan < Sha...@tr...> wrote: > Hi, > > > > I use matplotlib as my python graphics library. I happen to see the > following problems with the plot() function and would appreciate any help to > resolve these problems! > > > > 1. Using the default line style under plot() results in the function > dropping data points from the plot. Plotting the same data with a ‘dot’ > linestyle shows the missing data points. > > 2. Any large outliers in a data set are generally excluded from the > resulting plot. > > > > The original plot generated using the default linestyle does not show the > large outliers in the dataset. Further comparing against the second plot > shows missing data points which were not connected by the default linestyle. > Several missing data points are not necessarily large outliers. My initial > guess for missing large outliers was that the function was aliasing down > large values. > > > > Missing nominal data points makes me wonder if the plot function internally > generates a "best-fit" or least squares plot of the data points? This > inconsistent plot occurs only with large data sets. The two plots were > generated with over 100000 (hundred thousand) data points. > > > > Would be happy to send you the original data if that may help troubleshoot > this problem. > In all liklihood, you are using an older version of matplotlib which had a bug in the path.simplify logic that caused some points to be dropped. The solution is to either upgrade to the latest matplotlib (1.0.1) or turn off path simplification by setting 'path.simplify : False' in your matplotlibrc http://matplotlib.sourceforge.net/users/customizing.html You can find out what version of matplotlib you are running by doing In [127]: import matplotlib In [128]: matplotlib.__version__ Out[128]: '1.0.1' JDH
Dear Eric, thanks again for your comment, I am aware that the script contained both the individual colorbars and the common one. My comment in the code was because the placement on the figure is somewhat cramped: ## doesn't really work :/ ## in what way? cax = fig.add_axes([0.25, 0.06, 0.5, 0.02]) fig.colorbar(im2, cax, orientation='horizontal') Ideally, I'd need to create a new subfig 313 with a much reduced height. Either way, you helped me a lot! 2011年6月7日 Eric Firing <ef...@ha...>: > On 06/07/2011 01:37 AM, Daniel Mader wrote: >> >> Hi Eric, >> >> >> 2011年6月6日 Eric Firing<ef...@ha...>: >>> >>> It's not quite clear to me yet, but I assume you want to use a call to >>> imshow with a different data set in the second subplot, but have the >>> color scale and colorbar be identical to those in the first subplot. Is >>> that correct? If so, all you need to do is use the same norm for both >>> calls to imshow--that is, define a norm, set the limits you want on it, >>> and supply it as a kwarg. >> >> thanks a lot, you helped me to work around my problem, see code below :) >> >>> Also, for this sort of comparison, sometimes it is more efficient to use >>> a single colorbar for multiple panels, as in this example: >>> >>> >>> http://matplotlib.sourceforge.net/examples/pylab_examples/multi_image.html >> >> Very nice example! It's a little too complex for me, though, with all >> the calculations for the axes layout -- I prefer subplots :) However, >> I think I have found a nice compromise: > > Attached is a slight modification, much simpler than the example above, but > retaining the single colorbar. Alternatively, if you stick with the > colorbar for each panel (which is sometimes clearer), it illustrates a > slightly clearer way of handling the cmap and norm, explicitly using the > same instance of each for both images. > > Eric > >> >> import pylab >> import matplotlib as mpl >> >> pylab.close('all') >> >> dat = pylab.array([[1,2,3,4],[5,6,7,8]]) >> datT = dat/2 >> >> fig = pylab.figure() >> >> ax1 = fig.add_subplot(211) >> ax1.set_title('raw data') >> im1 = ax1.imshow(dat, interpolation='nearest', >> cmap=mpl.cm.get_cmap('rainbow', 20)) >> fig.colorbar(im1) >> >> ax2 = fig.add_subplot(212) >> ax2.set_title('leveled') >> im2 = ax2.imshow(datT, interpolation='nearest', >> cmap=mpl.cm.get_cmap('rainbow', 20)) >> ## apply norm: >> norm = mpl.colors.Normalize(vmin=dat.min(), vmax=dat.max()) >> im2.set_norm(norm) >> fig.colorbar(im2) >> >> ## doesn't really work :/ >> cax = fig.add_axes([0.25, 0.04, 0.5, 0.02]) >> fig.colorbar(im2, cax, orientation='horizontal') >> >> pylab.show() >> >> Thanks a lot, >> best regards, >> >> Daniel
Hello, I've got following function describing any kind of animal dispersal kernel: def pdf(x,s1,s2): return (p/(math.sqrt(2*math.pi*s1**2))*numpy.exp(-((x-0)**(2)/(2*s1**(2)))))+((1-p)/(s2*math.sqrt(2*math.pi))*numpy.exp(-((x-0)**(2)/(2*s2**(2))))) On the other hand I've got data from literature with which I want to fit the function so that I get s1, s2 and x. Ususally the data in the literature are as follows: Example 1: 50% of the animals are between -270m and +270m and 90% are between -500m and + 500m Example 2: 84% is between - 5000 m and +5000m, and 73% are between -1000m and +1000m So far as I understand an integration of the function is needed to solve for s1 and s2 as all the literature data give percentage (area under the curve) Can that be used to fit the curve or can that create ranges for s1 and s2. /Johannes -- NEU: FreePhone - kostenlos mobil telefonieren! Jetzt informieren: http://www.gmx.net/de/go/freephone
efiring wrote: > > My github branch now includes a changeset with augmented docstrings for > show and draw. > Your new docstrings are a great improvement. They answer many of the questions I have been having for years. As for where the interactive mode/non-interactive mode discussion should be, I think that while the mere existence of this discussion is an improvement. I vote for moving it to a more prominent place than the FAQ, as it is about an important, practical subject that users should be aware of quite early when they learn Matplotlib. Anyway, many thanks to you and Ben for devoting time to this. :-) -- View this message in context: http://old.nabble.com/Exact-semantics-of-ion%28%29---tp31728909p31798588.html Sent from the matplotlib - users mailing list archive at Nabble.com.