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
|
3
(3) |
4
(16) |
5
(8) |
6
(22) |
7
(10) |
8
(18) |
|
9
(11) |
10
(7) |
11
(16) |
12
(1) |
13
(10) |
14
(14) |
15
(2) |
|
16
(3) |
17
(19) |
18
(24) |
19
(35) |
20
(38) |
21
(27) |
22
(1) |
|
23
(9) |
24
(6) |
25
(24) |
26
(9) |
27
(7) |
28
(5) |
29
(9) |
|
30
(4) |
|
|
|
|
|
|
|
From: Jae-Joon L. <lee...@gm...> - 2008-11-14 23:33:27
|
On Fri, Nov 14, 2008 at 5:20 PM, Gael Varoquaux
<gae...@no...> wrote:
> On Fri, Nov 14, 2008 at 11:12:14AM -0800, Benjamin J. Racine wrote:
>> I use pause in matlab to cycle through an interactive do-loop and view a
>> bunch of plots in interactively...
>
>> Don't bother reproducing it here, but I am just wondering if this is
>> possible in ipython/matplotlib
>
> pylab.waitforbuttonpress will do what you want.
>
> Gaël
>
waitforbuttonpress immediately returns for any keyboard or mouse event
(from the gui canvas).
If you want to examine the plot (pan, zoom, etc) with mouse, a quick
solution would be to use a loop
while not waitforbuttonpress():
pass
The loop stops only for a key press.
Also, take a look at ginput().
-JJ
|
|
From: Gael V. <gae...@no...> - 2008-11-14 23:18:20
|
On Fri, Nov 14, 2008 at 11:12:14AM -0800, Benjamin J. Racine wrote: > I use pause in matlab to cycle through an interactive do-loop and view a > bunch of plots in interactively... > Don't bother reproducing it here, but I am just wondering if this is > possible in ipython/matplotlib pylab.waitforbuttonpress will do what you want. Gaël |
|
From: Tom D. <tom...@al...> - 2008-11-14 22:18:17
|
I've had the same problem. You can write a pause function using the python input() function but it hangs the GIL and as a result your window becomes unresponsive. If anyone knows a GIL friendly way to pause i would also be very interested. On Fri, Nov 14, 2008 at 1:12 PM, Benjamin J. Racine <bjr...@gl...> wrote: > I use pause in matlab to cycle through an interactive do-loop and view a > bunch of plots in interactively... > > Don't bother reproducing it here, but I am just wondering if this is > possible in ipython/matplotlib > > Many thanks, > > Ben Racine > _______________________________________________ > IPython-user mailing list > IPy...@sc... > http://lists.ipython.scipy.org/mailman/listinfo/ipython-user > > |
|
From: Michael D. <md...@st...> - 2008-11-14 21:02:02
|
I'm not at the bottom of this yet, but thought I'd share my progress so far --> It is leaking actual Python references (meaning len(gc.get_objects()) is increasing). So it's not a malloc/free pair. Seems to be Gtk-specific. (Both GtkAgg and Gtk). Other backends are unaffected (Qt4 has some sort of leak of a much smaller magnitude). The proper way to destroy pygtk objects appears to be a little bit of a black art. What's there now was pretty much arrived at by experimentation and seems very brittle. I know at one point it was working better than it is now. My next step will be to try to revert to a state where the leak wasn't so bad. Given the architecture of pygtk, I'm not sure it's possible to not leak at all when creating/destroying windows like this, but we should at least be able to reduce the leakage. If your use case is just generating a bunch of images in batch, I'd recommend using the Agg backend, rather than Gtk. That doesn't leak for me. If you really need to be opening and closing this many windows in succession, then we still don't have a good solution. Mike Michael Droettboom wrote: > Ok. Thanks, I'll look into it. Just wanted to rule out that this > wasn't the known Gtk memory leak with old versions of Gtk before > devoting time to it. > > Cheers, > Mike > > Eric Firing wrote: > >> Michael Droettboom wrote: >> >>> Can you provide more information about the platform and backend that >>> you are using? >>> >> Mike, >> >> I was able to reproduce this with my ubuntu 8.10, gtkagg backend. I >> ran the code via cut and paste with the stock python interpreter, not >> ipython. I did not measure the memory use carefully, but used the >> system monitor to observe memory for that process climbing, maybe 500k >> per cycle. >> >> Our usual memleak tester shows no problem, however. >> >> Eric >> >> >>> D2Hitman wrote: >>> >>>> I am getting a memory leak when i am using the pylab.close() >>>> function. I am >>>> running matplotlib-0.98.3. It happens in a very simple script such as: >>>> >>>> #!/usr/bin/python >>>> import time >>>> import pylab >>>> >>>> while True: >>>> time.sleep(1) >>>> print 'calling pylab' >>>> pylab.box() >>>> pylab.close() >>>> >>>> Every close seems to store megabytes in physical memory. Any idea >>>> why this >>>> happens? >>>> >>>> Cheers. >>>> >>>> >>>> >>>> > > -- Michael Droettboom Science Software Branch Operations and Engineering Division Space Telescope Science Institute Operated by AURA for NASA |
|
From: Benjamin J. R. <bjr...@gl...> - 2008-11-14 19:13:13
|
I use pause in matlab to cycle through an interactive do-loop and view a bunch of plots in interactively... Don't bother reproducing it here, but I am just wondering if this is possible in ipython/matplotlib Many thanks, Ben Racine |
|
From: D2Hitman <j.m...@wa...> - 2008-11-14 17:48:11
|
openSUSE 11.0 (x86_64) KDE 3.5.9 "release 49.1" with GTKAgg backend Michael Droettboom-3 wrote: > > Can you provide more information about the platform and backend that you > are using? > > D2Hitman wrote: >> I am getting a memory leak when i am using the pylab.close() function. I >> am >> running matplotlib-0.98.3. It happens in a very simple script such as: >> >> #!/usr/bin/python >> import time >> import pylab >> >> while True: >> time.sleep(1) >> print 'calling pylab' >> pylab.box() >> pylab.close() >> >> Every close seems to store megabytes in physical memory. Any idea why >> this >> happens? >> >> Cheers. >> >> >> > > -- > Michael Droettboom > Science Software Branch > Operations and Engineering Division > Space Telescope Science Institute > Operated by AURA for NASA > > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's > challenge > Build the coolest Linux based applications with Moblin SDK & win great > prizes > Grand prize is a trip for two to an Open Source event anywhere in the > world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > Matplotlib-users mailing list > Mat...@li... > https://lists.sourceforge.net/lists/listinfo/matplotlib-users > > -- View this message in context: http://www.nabble.com/pylab.close%28%29-tp20486589p20505291.html Sent from the matplotlib - users mailing list archive at Nabble.com. |
|
From: Michael D. <md...@st...> - 2008-11-14 17:47:01
|
Ok. Thanks, I'll look into it. Just wanted to rule out that this wasn't the known Gtk memory leak with old versions of Gtk before devoting time to it. Cheers, Mike Eric Firing wrote: > Michael Droettboom wrote: >> Can you provide more information about the platform and backend that >> you are using? > > Mike, > > I was able to reproduce this with my ubuntu 8.10, gtkagg backend. I > ran the code via cut and paste with the stock python interpreter, not > ipython. I did not measure the memory use carefully, but used the > system monitor to observe memory for that process climbing, maybe 500k > per cycle. > > Our usual memleak tester shows no problem, however. > > Eric > >> >> D2Hitman wrote: >>> I am getting a memory leak when i am using the pylab.close() >>> function. I am >>> running matplotlib-0.98.3. It happens in a very simple script such as: >>> >>> #!/usr/bin/python >>> import time >>> import pylab >>> >>> while True: >>> time.sleep(1) >>> print 'calling pylab' >>> pylab.box() >>> pylab.close() >>> >>> Every close seems to store megabytes in physical memory. Any idea >>> why this >>> happens? >>> >>> Cheers. >>> >>> >>> >> > -- Michael Droettboom Science Software Branch Operations and Engineering Division Space Telescope Science Institute Operated by AURA for NASA |
|
From: Eric F. <ef...@ha...> - 2008-11-14 17:40:25
|
Michael Droettboom wrote: > Can you provide more information about the platform and backend that you > are using? Mike, I was able to reproduce this with my ubuntu 8.10, gtkagg backend. I ran the code via cut and paste with the stock python interpreter, not ipython. I did not measure the memory use carefully, but used the system monitor to observe memory for that process climbing, maybe 500k per cycle. Our usual memleak tester shows no problem, however. Eric > > D2Hitman wrote: >> I am getting a memory leak when i am using the pylab.close() function. I am >> running matplotlib-0.98.3. It happens in a very simple script such as: >> >> #!/usr/bin/python >> import time >> import pylab >> >> while True: >> time.sleep(1) >> print 'calling pylab' >> pylab.box() >> pylab.close() >> >> Every close seems to store megabytes in physical memory. Any idea why this >> happens? >> >> Cheers. >> >> >> > |
|
From: DAVID H. <dav...@un...> - 2008-11-14 15:58:30
|
>> Hi all,
>>
>> I'm having problems with axis labels for large integers (1471674
>> is represented as 1000 +1.479e6) .... I really need to see the
>> number as a conventional integer. I have the feeling that it
>> should be possible with ticker. FormatStrFormatter but I have not
>> been able to work out how. Any advice would be greatly appreciated.
>>
> Assuming 'ax' is your current set of axes (obtained from gca() or a
> call to subplot(), for example)...
> from matplotlib import ticker
> ...
>
> ax.xaxis.set_major_formatter(ticker.FormatStrFormatter("%d"))
> ax.yaxis.set_major_formatter(ticker.FormatStrFormatter("%d"))
>> While I'm asking stupid questions, I'd also like to know how to
>> let the absolute dimensions of a subplot (with a barh()
>> horizontal bar chart) adjust themselves according to the number
>> of bars added (keeping the height of the bars strictly constant
>> rather than the bar height adjusting according to the number of
>> data points).
>>
Fantastic .... I knew this should be easy
>>
> There's no direct way to do this, but by setting the figure size
> based on the number of bars, you should be able to fake it. You
> can set the overall figure size either when you create the figure:
>
> figure(figsize=(4,3))
>
> or after the fact (which doesn't really work with interactive GUIs
> -- that is, it won't resize the window) --
>
> gcf().set_size_inches((4, 3))
>
> The unit is in inches -- the dpi of the figure can also be set in a
> similar way.
>
Hmm, the thing is that I'm using a barh() subplot underneath a series
of bar() subplots. The bar() subplots always have the same y axes,
but the number of items in the barh() subplot varies (I use the barh
() to illustrate features along a stretch of genomic DNA which also
has quantitative values attached to it in the bar() plots above). I
need to make a series of figures in this way wherein the bar()
subplots always have the same dimension, but only the "height" of the
barh() subplot varies (with the number of instances to plot) while
the Y axes ALL need to remain the same.
Can I size the whole figure with the above and fix the dimensions of
each of the subplots independently? If so I should be able to bodge it!
I'm pretty new to matplotlib and not really an expert programmer in
any case. While I'm very pleased with the quality of the figures, I'm
really struggling with ironing out a few maddening glitches.
Thanks again.
D
> Hope that at least helps,
> Mike
>> Many thanks
>>
>> David
>>
>>
>>
>> ---------------------------------------------------------------------
>> ----
>> This SF.Net email is sponsored by the Moblin Your Move Developer's
>> challenge
>> Build the coolest Linux based applications with Moblin SDK & win
>> great prizes
>> Grand prize is a trip for two to an Open Source event anywhere in
>> the world
>> http://moblin-contest.org/redirect.php?banner_id=100&url=/
>> _______________________________________________
>> Matplotlib-users mailing list
>> Mat...@li...
>> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
>>
>
> --
> Michael Droettboom
> Science Software Branch
> Operations and Engineering Division
> Space Telescope Science Institute
> Operated by AURA for NASA
>
|
|
From: Michael D. <md...@st...> - 2008-11-14 15:43:55
|
Michael Droettboom wrote: > or after the fact (which doesn't really work with interactive GUIs -- > that is, it won't resize the window) -- > > I'll correct myself on this point. According to the docs, the window will resize if forward=True for Gtk and Wx backends. Cheers, Mike -- Michael Droettboom Science Software Branch Operations and Engineering Division Space Telescope Science Institute Operated by AURA for NASA |
|
From: Michael D. <md...@st...> - 2008-11-14 15:10:47
|
DAVID HORNER wrote:
> Hi all,
>
> I'm having problems with axis labels for large integers (1471674 is
> represented as 1000 +1.479e6) .... I really need to see the number as
> a conventional integer. I have the feeling that it should be possible
> with ticker. FormatStrFormatter but I have not been able to work out
> how. Any advice would be greatly appreciated.
>
Assuming 'ax' is your current set of axes (obtained from gca() or a call
to subplot(), for example)...
from matplotlib import ticker
...
ax.xaxis.set_major_formatter(ticker.FormatStrFormatter("%d"))
ax.yaxis.set_major_formatter(ticker.FormatStrFormatter("%d"))
> While I'm asking stupid questions, I'd also like to know how to let
> the absolute dimensions of a subplot (with a barh() horizontal bar
> chart) adjust themselves according to the number of bars added
> (keeping the height of the bars strictly constant rather than the bar
> height adjusting according to the number of data points).
>
There's no direct way to do this, but by setting the figure size based
on the number of bars, you should be able to fake it. You can set the
overall figure size either when you create the figure:
figure(figsize=(4,3))
or after the fact (which doesn't really work with interactive GUIs --
that is, it won't resize the window) --
gcf().set_size_inches((4, 3))
The unit is in inches -- the dpi of the figure can also be set in a
similar way.
Hope that at least helps,
Mike
> Many thanks
>
> David
>
>
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
> Build the coolest Linux based applications with Moblin SDK & win great prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
>
--
Michael Droettboom
Science Software Branch
Operations and Engineering Division
Space Telescope Science Institute
Operated by AURA for NASA
|
|
From: Michael D. <md...@st...> - 2008-11-14 15:01:11
|
Can you provide more information about the platform and backend that you are using? D2Hitman wrote: > I am getting a memory leak when i am using the pylab.close() function. I am > running matplotlib-0.98.3. It happens in a very simple script such as: > > #!/usr/bin/python > import time > import pylab > > while True: > time.sleep(1) > print 'calling pylab' > pylab.box() > pylab.close() > > Every close seems to store megabytes in physical memory. Any idea why this > happens? > > Cheers. > > > -- Michael Droettboom Science Software Branch Operations and Engineering Division Space Telescope Science Institute Operated by AURA for NASA |
|
From: DAVID H. <dav...@un...> - 2008-11-14 08:15:40
|
Hi all, I'm having problems with axis labels for large integers (1471674 is represented as 1000 +1.479e6) .... I really need to see the number as a conventional integer. I have the feeling that it should be possible with ticker. FormatStrFormatter but I have not been able to work out how. Any advice would be greatly appreciated. While I'm asking stupid questions, I'd also like to know how to let the absolute dimensions of a subplot (with a barh() horizontal bar chart) adjust themselves according to the number of bars added (keeping the height of the bars strictly constant rather than the bar height adjusting according to the number of data points). Many thanks David |
|
From: John [H2O] <was...@gm...> - 2008-11-14 04:38:55
|
Hello, using matplotlib 0.98 with mpl_toolkit Basemap: I'm trying to create a plot with a series of ellipses over a map. I've followed the tutorial, and can create the same figure as shown here: http://matplotlib.sourceforge.net/users/screenshots.html#ellipses I can also create a series of ellipses over a map. Now I am trying to label each circle using the following snippet: for item in ells: #ells is now a tuple in the form: (Ellipse, (x,y)) and (x,y) is the same as for the Ellipse e = item[0] xy = item[1] ax.add_artist(e) e.set_clip_box(ax.bbox) e.set_alpha(.7) pyplot.text(xy[0],xy[1],e.get_label()) however, for some reason it fails. Can someone provide some ideas on what I am doing wrong? Also, is there more direct way to set the plots so that the labels are drawn? What is strange, is that it seems to work (at least debugging print statements after the loop are printed)... and I can move the text function out of the loop to label the 'last' ellipse... As it is it fails when savefig() or show() are called. The error is: TypeError: CXX : Error creating object of type N2Py3IntE THoughts? Thanks, john -- View this message in context: http://www.nabble.com/plotting-labels-for-each-%27artist%27-in-a-basemap-tp20494609p20494609.html Sent from the matplotlib - users mailing list archive at Nabble.com. |