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
(8) |
2
(7) |
3
(8) |
4
(12) |
5
(1) |
6
(1) |
7
(9) |
8
(2) |
9
|
10
(1) |
11
|
12
(6) |
13
(6) |
14
(2) |
15
(7) |
16
(10) |
17
|
18
(3) |
19
(4) |
20
(4) |
21
(10) |
22
(8) |
23
(17) |
24
(13) |
25
(9) |
26
(1) |
27
(1) |
28
(4) |
29
(7) |
30
(2) |
31
(10) |
|
|
Thanks Jerzy. It works fine. I may return to this topic for more discussion later. chao Jerzy Karczmarczuk-2 wrote: > > Benjamin Root : >> Colorbars are a bit tricky. They are actually a subplot axes separate >> from your plotting axes. And I don't think they are very easy to >> remove. You could do a "cbar.axes.cla()", but that would still leave >> the "ticks", tick labels and the colorbar label. >> >> I am sure that there is a way to get to what you want, but it isn't >> immediately obvious. > Well, I tried with some success the following. Suppose the programme is: > > from pylab import * > fig = figure() > ax = fig.add_subplot(111) > data = rand(250, 250) > cax = ax.imshow(data) > cbar = fig.colorbar(cax) > show() > > Now, fig has two axes, the main, and the bar. The command > > fig.delaxes(fig.axes[1]) > > gets rid of the bar and the ticks. > Is there anything wrong with that? Of course, I knew that fig.axes[1] > was the bar, but finding it in a more complicated case should not be > difficult. > > All the best. > > Jerzy Karczmarczuk > > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > Matplotlib-users mailing list > Mat...@li... > https://lists.sourceforge.net/lists/listinfo/matplotlib-users > > -- View this message in context: http://old.nabble.com/how-to-remove-colorbar--tp33882320p33892056.html Sent from the matplotlib - users mailing list archive at Nabble.com.
lunedì 21 maggio 2012, 21:30, Kevin Davies: > Hi Giovanni, > > Thanks for your report. It looks like in this case the "dip" in the > large, single input caused the input label to be at the center of the > diagram. You might want to try increasing the trunklength > parameter. Maybe someone has ideas to make this sort of thing more > automatic, but otherwise it takes some manual tweaking. Hi Kevin and thanks for replying. I've tried increasing the trunklength parameter, but i can't get the patch label in the center. Giovanni
Dear all, ferret now has a pyferret module available through python. Just in case some people have used ferret before and might be interesting :) cheers, Chao ---------- Forwarded message ---------- From: Karl Smith <kar...@no...> Date: 2012年5月22日 Subject: [ferret_users] PyFerret (beta) documentation and release available from Ferret website To: ferret <fer...@no...> For those interested in trying out PyFerret (Ferret as a Python module), or those just interested in knowing more about PyFerret, there are now documentation and download pages available on the Ferret website under the documentation tab: http://ferret.pmel.noaa.gov/Ferret/documentation/pyferret Toward the bottom part of the page is the link for the Downloads page, which gives links for pre-built binaries and for source (as gzipped tar files). Below it is a link for the Installing or Building PyFerret page, which gives step-by-step instructions for installing or building the program. There is also a link for the Known Issues page, listing changes in behavior and the most serious bugs that I am aware of. This is the latest version (0.0.8) of PyFerret which produces better graphics and supports saving images directly as PNG and PDF files. (The XGKS graphics library has been replaced with Cairo and PyQt. It still uses Plot+, so those PPL commands still work). It contains the latest released version of Ferret, and is (statically) linked with NetCDF-4.2 libraries. I still am considering it a beta version because of the bugs listed in the Known Issues page. -- Karl -- Karl M. Smith, Ph.D. JISAO Univ. Wash. and TMAP/PMEL NOAA "The contents of this message are mine personally and do not necessarily reflect any position of the Government or the National Oceanic and Atmospheric Administration." -- *********************************************************************************** Chao YUE Laboratoire des Sciences du Climat et de l'Environnement (LSCE-IPSL) UMR 1572 CEA-CNRS-UVSQ Batiment 712 - Pe 119 91191 GIF Sur YVETTE Cedex Tel: (33) 01 69 08 29 02; Fax:01.69.08.77.16 ************************************************************************************
Hi Ben I am using 1.0.0. My colleague has 1.1.0 installed on his machine and is able to reproduce the same problem. Thanks Sam From: ben...@gm... [mailto:ben...@gm...] On Behalf Of Benjamin Root Sent: 22 May 2012 14:14 To: Stevenson, Samuel Cc: mat...@li... Subject: Re: [Matplotlib-users] plt.close() not releasing memory? Or memory leak elsewhere? On Tue, May 22, 2012 at 8:44 AM, Stevenson, Samuel <Sam...@co...<mailto:Sam...@co...>> wrote: Hi All After spending all day working on this I have discovered that if I explicity change the matplotlib backend in spyder from 'Qt4Agg' to 'Agg' then my code executes as expected with no memory errors. Any ideas about this? It seems like a bug in Qt4Agg of some kind---is there somewhere I should file a bug report? Thanks Sam Which version of mpl are you using? There have already been some efforts to close out memory leaks and yours may already be fixed in the development version of mpl. Ben Root
On Tue, May 22, 2012 at 8:44 AM, Stevenson, Samuel < Sam...@co...> wrote: > Hi All**** > > ** ** > > After spending all day working on this I have discovered that if I > explicity change the matplotlib backend in spyder from ‘Qt4Agg’ to ‘Agg’ > then my code executes as expected with no memory errors. **** > > ** ** > > Any ideas about this? It seems like a bug in Qt4Agg of some kind---is > there somewhere I should file a bug report? **** > > ** ** > > Thanks**** > > > Sam **** > > ** ** > > ** > Which version of mpl are you using? There have already been some efforts to close out memory leaks and yours may already be fixed in the development version of mpl. Ben Root
Hi All After spending all day working on this I have discovered that if I explicity change the matplotlib backend in spyder from 'Qt4Agg' to 'Agg' then my code executes as expected with no memory errors. Any ideas about this? It seems like a bug in Qt4Agg of some kind---is there somewhere I should file a bug report? Thanks Sam
Hi All. I'm experiencing some memory issues with some python/matplotlib code. I have a large object/class containing a lot of data, and whilst using that object to create (about 30) graphs I keep running into memory errors. Here is a description of my problem: Firstly, I am able to create each graph individually. So if I run each graph creation function individually in the interpreter I get the desired result: MyClass.TypicalPlot(save=True, show = False) However, if I create a new function to run each graph function in a script then I get a "MemoryError: Could not allocate memory for path". (varies at the precise point where, but its normally after 3 or 4 graphs). I am able to run each plot function in an interpreter without issue, so I can only assume its some kind of memory/garbage collection issue. def saveAllPlots(self, comments = False): if self.comment is None: comment = False else: comment = True self.TypicalPlot(save=True, show=False, comment=comment) self.AnotherPlot(save=True, show=False) self.AnotherPlot2(save=True, show=False) self.AnotherPlot3(save=True, show=False) ...etc, etc, etc Here is what a typical plot function looks like in my code (they are all very similar) def TypicalPlot(self, title=None, comment=False, save=False, show=True): if title is None: title = self.dat.title fig = plt.figure() host = SubplotHost(fig, 111) fig.add_subplot(host) par = host.twinx() host.set_xlabel("Time (hrs)") host.set_ylabel("Power (W)") par.set_ylabel("Temperature (C)") p1, = host.plot(self.dat.timebase1, self.dat.pwr, 'b,', label="Power", markevery= self.skip) p2, = par.plot(self.dat.timebase2, self.dat.Temp1, 'r,', label="Temp 1", markevery= self.skip) p3, = par.plot(self.dat.timebase2, self.dat.Temp2, 'g,', label="Temp 2", markevery= self.skip) p4, = par.plot(self.dat.timebase2, self.dat.Temp3, 'm,', label="Temp 3", markevery= self.skip) host.axis["left"].label.set_color(p1.get_color()) # par.axis["right"].label.set_color(p2.get_color()) #host.legend(loc='lower left') plt.title(title+" Temperature") leg=host.legend(loc='lower left',fancybox=True) #leg.get_frame().set_alpha(0.5) frame = leg.get_frame() frame.set_facecolor('0.80') ### make the legend text smaller for t in leg.get_texts(): t.set_fontsize('small') ### set the legend text color to the same color as the plots for added ### readability leg.get_texts()[0].set_color(p1.get_color()) leg.get_texts()[1].set_color(p2.get_color()) leg.get_texts()[2].set_color(p3.get_color()) leg.get_texts()[3].set_color(p4.get_color()) if show is True and save is True: plt.show() plt.savefig('temp.png') elif show is True and save is False: plt.show() elif show is False and save is True: plt.savefig('temp.png') plt.clf() plt.close(fig) Has anyone come across this before? Regards, Sam Stevenson
<html> <head> <meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type"> </head> <body text="#000000" bgcolor="#FFFFFF"> <pre wrap="">Hi Giovanni, Thanks for your report. It looks like in this case the "dip" in the large, single input caused the input label to be at the center of the diagram. You might want to try increasing the trunklength parameter. Maybe someone has ideas to make this sort of thing more automatic, but otherwise it takes some manual tweaking. I hope this helps. Kevin </pre> <br> On 05/21/2012 11:39 AM, Giovanni wrote: <blockquote cite="mid:201...@in..." type="cite"> <pre wrap=""> Hi all! I'm experiencing a strange behaviour with sankey diagram. As you can see from the attached image, the patch label it's not positioned in the middle of the patch (as it should), but it's plotted over the first label... The code is attached also. Any hints? Thanks, Giovanni</pre> <br> <fieldset class="mimeAttachmentHeader"></fieldset> <br> <pre wrap="">------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. <a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/">http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/</a></pre> <br> <fieldset class="mimeAttachmentHeader"></fieldset> <br> <pre wrap="">_______________________________________________ Matplotlib-users mailing list <a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:Mat...@li...">Mat...@li...</a> <a moz-do-not-send="true" class="moz-txt-link-freetext" href="https://lists.sourceforge.net/lists/listinfo/matplotlib-users">https://lists.sourceforge.net/lists/listinfo/matplotlib-users</a> </pre> </blockquote> <br> <br> </body> </html>