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
(2) |
2
(4) |
3
(16) |
4
(4) |
5
(15) |
6
(16) |
7
(6) |
8
(4) |
9
(9) |
10
(5) |
11
(8) |
12
(14) |
13
(19) |
14
(21) |
15
(8) |
16
(6) |
17
(10) |
18
(22) |
19
(15) |
20
(7) |
21
(21) |
22
(1) |
23
(6) |
24
(16) |
25
(12) |
26
(11) |
27
(27) |
28
(7) |
29
|
30
(4) |
31
(5) |
|
|
|
|
|
Ah, thank you very much, that helped! It works nicely! Best regards, Daniel
On 01/22/2011 05:16 PM, Paul Ivanov wrote: > Paul Ivanov, on 2011年01月22日 18:28, wrote: >> Ilya Shlyakhter, on 2011年01月22日 19:06, wrote: >>> Is it possible to create a "break" in the y-axis so that it has ticks >>> for value 0-.2, then ticks for values .8-1.0, but devotes only a token >>> amount of space to the area 0.2-0.8? >>> I have a dataset with most datapoints in 0-.2 and a couple in .8-1.0, >>> and none in .2-.8 . The default scaling wastes a lot of space and >>> compresses the data in the 0-.2 range >>> such that it is hard to distinguish. >> >> Hi Ilya, >> >> this... Paul, Your example below is nice, and this question comes up quite often. If we don't already have a gallery example of this, you might want to add one. (Probably better to use deterministic fake data rather than random.) Eric >> >>> p.s. I know I could use two y-axes with different scales; but this >>> would require splitting the data into two different datasets as well, >>> and would not allow connecting all points >>> with one line. >> >> ... is the way I'd proceed, because it's clean, and requires the >> least amount of work. Connecting your lines across such breaks >> is misleading - since the magnitude of the slope of the >> connecting line segment arbitrary relative to all other line >> segments. You don't actually have to divide your data, you can >> just replot *all* data on the secondary plot, and then set the x >> and y lims to break up your views on the data. I'm attaching a >> quick sketch of what that would look like. (Note how different >> the outlier line segments would look if we connected them in the >> same manner that all other points are connected). >> >> import numpy as np >> import matplotlib.pylab as plt >> pts = np.random.rand(30)*.2 >> pts[[7,11]] += .8 >> f,(ax,ax2) = plt.subplots(2,1,sharex=True) >> >> ax.plot(pts) >> ax2.plot(pts) >> ax.set_ylim(.78,1.) >> ax2.set_ylim(0,.22) >> >> ax.xaxis.tick_top() >> ax.spines['bottom'].set_visible(False) >> ax.tick_params(labeltop='off') >> ax2.xaxis.tick_bottom() >> ax2.spines['top'].set_visible(False) >> >> If this is something you really want, though, you can achieve it >> by making your own projection/scale: >> http://matplotlib.sourceforge.net/devel/add_new_projection.html >> >> Yet another way would be to re-label the tick lines (e.g. make .6 >> label be 1.0 and subtract that offset from your two outliers. > > forgot the attachment, here it is. > > > > > ------------------------------------------------------------------------------ > Special Offer-- Download ArcSight Logger for FREE (a 49ドル USD value)! > Finally, a world-class log management solution at an even better price-free! > Download using promo code Free_Logger_4_Dev2Dev. Offer expires > February 28th, so secure your free ArcSight Logger TODAY! > http://p.sf.net/sfu/arcsight-sfd2d > > > > _______________________________________________ > Matplotlib-users mailing list > Mat...@li... > https://lists.sourceforge.net/lists/listinfo/matplotlib-users
Paul Ivanov, on 2011年01月22日 18:28, wrote: > Ilya Shlyakhter, on 2011年01月22日 19:06, wrote: > > Is it possible to create a "break" in the y-axis so that it has ticks > > for value 0-.2, then ticks for values .8-1.0, but devotes only a token > > amount of space to the area 0.2-0.8? > > I have a dataset with most datapoints in 0-.2 and a couple in .8-1.0, > > and none in .2-.8 . The default scaling wastes a lot of space and > > compresses the data in the 0-.2 range > > such that it is hard to distinguish. > > Hi Ilya, > > this... > > > p.s. I know I could use two y-axes with different scales; but this > > would require splitting the data into two different datasets as well, > > and would not allow connecting all points > > with one line. > > ... is the way I'd proceed, because it's clean, and requires the > least amount of work. Connecting your lines across such breaks > is misleading - since the magnitude of the slope of the > connecting line segment arbitrary relative to all other line > segments. You don't actually have to divide your data, you can > just replot *all* data on the secondary plot, and then set the x > and y lims to break up your views on the data. I'm attaching a > quick sketch of what that would look like. (Note how different > the outlier line segments would look if we connected them in the > same manner that all other points are connected). > > import numpy as np > import matplotlib.pylab as plt > pts = np.random.rand(30)*.2 > pts[[7,11]] += .8 > f,(ax,ax2) = plt.subplots(2,1,sharex=True) > > ax.plot(pts) > ax2.plot(pts) > ax.set_ylim(.78,1.) > ax2.set_ylim(0,.22) > > ax.xaxis.tick_top() > ax.spines['bottom'].set_visible(False) > ax.tick_params(labeltop='off') > ax2.xaxis.tick_bottom() > ax2.spines['top'].set_visible(False) > > If this is something you really want, though, you can achieve it > by making your own projection/scale: > http://matplotlib.sourceforge.net/devel/add_new_projection.html > > Yet another way would be to re-label the tick lines (e.g. make .6 > label be 1.0 and subtract that offset from your two outliers. forgot the attachment, here it is. -- Paul Ivanov 314 address only used for lists, off-list direct email at: http://pirsquared.org | GPG/PGP key id: 0x0F3E28F7
Glen Shennan, on 2011年01月21日 15:41, wrote: > Hi, > > I'm trying to install matplotlib from the svn source. I can compile > the code and install it to my desired location but I cannot import it > into python. > > I did: > > svn co https://matplotlib.svn.sourceforge.net/svnroot/matplotlib/trunk/matplotlib > matplotlib > cd matplotlib > python setup.py install --prefix=/home/glen/local > > I have numpy and scipy installed and working correctly using the above > prefix and matplotlib compiles and installs the same way but when I > issue "import matplotlib as mpl" nothing results. There is no error > but also no library. > > >>> dir(mpl) > ['__builtins__', '__doc__', '__file__', '__name__', '__package__', '__path__'] > > >>> mpl.__path__ > ['matplotlib'] > > >>> mpl.__file__ > 'matplotlib/__init__.pyc' Hi Glen, what directory are you in when you're doing this? > >>> mpl.__path__ > ['matplotlib'] suggests that you're importing from some local directory. If everything worked right, the path should be something like >>> mpl.__path__ ['/home/glen/local/lib/python2.x/site-packages/matplotlib'] best, -- Paul Ivanov 314 address only used for lists, off-list direct email at: http://pirsquared.org | GPG/PGP key id: 0x0F3E28F7
Ilya Shlyakhter, on 2011年01月22日 19:06, wrote: > Is it possible to create a "break" in the y-axis so that it has ticks > for value 0-.2, then ticks for values .8-1.0, but devotes only a token > amount of space to the area 0.2-0.8? > I have a dataset with most datapoints in 0-.2 and a couple in .8-1.0, > and none in .2-.8 . The default scaling wastes a lot of space and > compresses the data in the 0-.2 range > such that it is hard to distinguish. Hi Ilya, this... > p.s. I know I could use two y-axes with different scales; but this > would require splitting the data into two different datasets as well, > and would not allow connecting all points > with one line. ... is the way I'd proceed, because it's clean, and requires the least amount of work. Connecting your lines across such breaks is misleading - since the magnitude of the slope of the connecting line segment arbitrary relative to all other line segments. You don't actually have to divide your data, you can just replot *all* data on the secondary plot, and then set the x and y lims to break up your views on the data. I'm attaching a quick sketch of what that would look like. (Note how different the outlier line segments would look if we connected them in the same manner that all other points are connected). import numpy as np import matplotlib.pylab as plt pts = np.random.rand(30)*.2 pts[[7,11]] += .8 f,(ax,ax2) = plt.subplots(2,1,sharex=True) ax.plot(pts) ax2.plot(pts) ax.set_ylim(.78,1.) ax2.set_ylim(0,.22) ax.xaxis.tick_top() ax.spines['bottom'].set_visible(False) ax.tick_params(labeltop='off') ax2.xaxis.tick_bottom() ax2.spines['top'].set_visible(False) If this is something you really want, though, you can achieve it by making your own projection/scale: http://matplotlib.sourceforge.net/devel/add_new_projection.html Yet another way would be to re-label the tick lines (e.g. make .6 label be 1.0 and subtract that offset from your two outliers. best, -- Paul Ivanov 314 address only used for lists, off-list direct email at: http://pirsquared.org | GPG/PGP key id: 0x0F3E28F7
Is it possible to create a "break" in the y-axis so that it has ticks for value 0-.2, then ticks for values .8-1.0, but devotes only a token amount of space to the area 0.2-0.8? I have a dataset with most datapoints in 0-.2 and a couple in .8-1.0, and none in .2-.8 . The default scaling wastes a lot of space and compresses the data in the 0-.2 range such that it is hard to distinguish. Thanks for any help! Ilya p.s. I know I could use two y-axes with different scales; but this would require splitting the data into two different datasets as well, and would not allow connecting all points with one line.