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: Michael D. <md...@st...> - 2010-08-24 12:43:36
|
You have plotted three lines, but only provided legend labels for two of
them. Try:
plt.legend(('Model length', 'Data length', 'Something else'),
'best', shadow=True, fancybox=True)
Mike
On 08/24/2010 06:33 AM, xyz wrote:
> Hello,
> the following script creates a legend for only two instead of three
> datasets.
> -----------
> from pylab import *
> import matplotlib.pyplot as plt
>
> fig = plt.figure()
> ax = fig.add_subplot(111)
>
> for i in [[2,2], [2,3], [4.2,3.5]]:
> print i[0],i[1]
> plt.plot(i[0],i[1],'o')
>
> ax.grid(True)
> plt.legend(('Model length', 'Data length'),
> 'best', shadow=True, fancybox=True)
>
> plt.show()
> -----------------
>
> What did I wrong.
>
> Thank you in advance.
>
> ------------------------------------------------------------------------------
> 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
>
--
Michael Droettboom
Science Software Branch
Space Telescope Science Institute
Baltimore, Maryland, USA
|
|
From: xyz <mi...@op...> - 2010-08-24 10:34:04
|
Hello,
the following script creates a legend for only two instead of three
datasets.
-----------
from pylab import *
import matplotlib.pyplot as plt
fig = plt.figure()
ax = fig.add_subplot(111)
for i in [[2,2], [2,3], [4.2,3.5]]:
print i[0],i[1]
plt.plot(i[0],i[1],'o')
ax.grid(True)
plt.legend(('Model length', 'Data length'),
'best', shadow=True, fancybox=True)
plt.show()
-----------------
What did I wrong.
Thank you in advance.
|
|
From: xiaoni <wa...@ya...> - 2010-08-24 10:13:08
|
Hello, Benjamin,
Thanks for your quick response ! I found that I only need use clf(), and
then everything is fine ! The code can be run quickly and I can exit ipython
gracefully afterwards. So it is not a problem of backend, just of clearing the
existing figures properly ! (close() is not good because the figures are not
displayed.)
cheers,
xiaoni
________________________________
From: Benjamin Root <ben...@ou...>
To: xiaoni <wa...@ya...>
Cc: mat...@li...
Sent: Tue, August 24, 2010 2:29:32 AM
Subject: Re: [Matplotlib-users] a question about backend, matplotlib and ipython
On Mon, Aug 23, 2010 at 1:53 PM, xiaoni <wa...@ya...> wrote:
Hello,
> I got a problem with backend in matplotlib.
> I used ipython for launching the codes and the backend of
>matplotlib is GTKAgg. I have a code.py with a for loop for processing data,
>and in each iteration I read and plot and save the figures. Because
>there are so many figures, I set the non-interative mode and not using
>"show()" in the code. Then the memory is used more and more as the
>iteration number increases, and the most memory is due to write_png
>function. I guess that the figures (though not shown on the screen)
>from each iteration take the memory, and try to close the figures produced at
>each iteration.
>what I did:
>modify the backend to Agg in the code
>add "close('all')" before each iteration finish.
>
> This works for removing the memory problem. But a new issue arrive.
>After the run is finished, the ipython command window has no response
>to any keyboard input for a few seconds, then a warning message appear:
> "Warning: Timeout for mainloop thread exceeded switching to
>nonthreaded mode (until mainloop wakes up again)",
>and when I tried to quit ipython afterwards, it is stuck there and the
>ipython is crashed.
> But if I tried using "python code.py" , then it works well : no warnings.
> Does it mean that we can not use ipython and a backend non-GUI at the same
>time ?
>
> Any one would like to explain a bit ? Thanks in advance !!
>
>
>xiaoni
>
>
xiaoni,
For the way that you appear to be using ipython, it might be better to just use
regular python instead. ipython is very useful for interactive systems and
other advanced topics, but for a simple, loop-driven image generator, python
will work just fine.
As for your memory usage, doing a clf() should be helpful to keep it under
control. I should also note that ipython have been known to cause memory use to
grow due to the extra references it holds to the figure data, although I don't
know if this is still true in the latest version that is currently being worked
on.
I hope this helps,
Ben Root
|
|
From: Chloe L. <ch...@be...> - 2010-08-24 06:24:36
|
And if you have mutually prime numbers of colors,
linestyles, widths, you can automatically generate
more distinct lines than I can distinguish... If there's any
wxcuse for treating them as a series, I replot
when I know how many I have, and space the
colors through a colorbar.
&C
Away from home, checking mail rarely.
On Aug 23, 2010, at 2:11 PM, John Salvatier
<jsalvati@u.washington.edu> wrote:
> By the way, I found that the following generator expression made
> things easy:
>
> def styles():
> return ( {'c' : color, 'ls' : style, 'lw' : width} for color,
> style, width in itertools.product(colors, linestyles, linewidths))
>
> then you can do something like
>
> for result, style in zip(results, styles()):
> pylab.plot(result[i], **style)
>
> On Mon, Aug 23, 2010 at 1:22 PM, John Salvatier <jsalvati@u.washington.edu
> > wrote:
> Thanks!
>
>
> On Mon, Aug 23, 2010 at 12:38 PM, Aman Thakral
> <ama...@gm...> wrote:
> Hi John,
>
> Here is a simple way to do it.
>
> import matplotlib.pyplot as plt
> import numpy as np
> fig = plt.figure()
> ax = fig.add_subplot(111)
>
> colors = ('red','green','blue','yellow','orange')
> linestyles = ('-','--',':')
> linewidths = (0.5,2)
>
> y = np.random.randn(100,30)
> x = range(y.shape[0])
> i = 0
>
> for c in colors:
> for ls in linestyles:
> for lw in linewidths:
> ax.plot(x,y[:,i],c=c,ls=ls,lw=lw)
> i+=1
> plt.show()
>
>
>
> On 10-08-23 03:06 PM, John Salvatier wrote:
>> Hello,
>>
>> I have a plot with lots of curves on it (say 30), and I would like
>> to have some way of distinguishing the curves from each other. Just
>> plotting them works well for a few curves because they come out as
>> different colors unless you specify otherwise, but if you do too
>> many you start getting repeats is there a way to have matplotlib
>> also vary the line style that it automatically assigns? Or perhaps
>> someone has another way of distinguishing lots of curves?
>>
>> Best Regards,
>> John
>>
>>
>> ---
>> ---
>> ---
>> ---------------------------------------------------------------------
>> 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
>>
>
>
>
> ---
> ---
> ---
> ---------------------------------------------------------------------
> 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
|
|
From: Benjamin R. <ben...@ou...> - 2010-08-24 00:29:58
|
On Mon, Aug 23, 2010 at 1:53 PM, xiaoni <wa...@ya...> wrote:
> Hello,
> I got a problem with backend in matplotlib.
> I used ipython for launching the codes and the backend of matplotlib
> is GTKAgg. I have a code.py with a for loop for processing data, and in
> each iteration I read and plot and save the figures. Because there are so
> many figures, I set the non-interative mode and not using "show()" in the
> code. Then the memory is used more and more as the iteration number
> increases, and the most memory is due to write_png function. I guess that
> the figures (though not shown on the screen) from each iteration take the
> memory, and try to close the figures produced at each iteration.
> what I did:
> modify the backend to Agg in the code
> add "close('all')" before each iteration finish.
>
> This works for removing the memory problem. But a new issue arrive.
> After the run is finished, the ipython command window has no response to any
> keyboard input for a few seconds, then a warning message appear:
> "Warning: Timeout for mainloop thread exceeded switching to nonthreaded
> mode (until mainloop wakes up again)",
> and when I tried to quit ipython afterwards, it is stuck there and the
> ipython is crashed.
> But if I tried using "python code.py" , then it works well : no
> warnings.
> Does it mean that we can not use ipython and a backend non-GUI at the
> same time ?
>
> Any one would like to explain a bit ? Thanks in advance !!
>
>
> xiaoni
>
>
>
xiaoni,
For the way that you appear to be using ipython, it might be better to just
use regular python instead. ipython is very useful for interactive systems
and other advanced topics, but for a simple, loop-driven image generator,
python will work just fine.
As for your memory usage, doing a clf() should be helpful to keep it under
control. I should also note that ipython have been known to cause memory
use to grow due to the extra references it holds to the figure data,
although I don't know if this is still true in the latest version that is
currently being worked on.
I hope this helps,
Ben Root
|