Re: [Matplotlib-users] plt.close() not releasing memory? Or memory leak elsewhere?

2012-05-22 Thread Stevenson, Samuel
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


--
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
Matplotlib-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-users


Re: [Matplotlib-users] plt.close() not releasing memory? Or memory leak elsewhere?

2012-05-22 Thread Benjamin Root
On Tue, May 22, 2012 at 8:44 AM, Stevenson, Samuel 
samuel.steven...@coherent.com 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
--
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
Matplotlib-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-users


Re: [Matplotlib-users] plt.close() not releasing memory? Or memory leak elsewhere?

2012-05-22 Thread Stevenson, Samuel
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.v.r...@gmail.com [mailto:ben.v.r...@gmail.com] On Behalf Of Benjamin 
Root
Sent: 22 May 2012 14:14
To: Stevenson, Samuel
Cc: matplotlib-users@lists.sourceforge.net
Subject: Re: [Matplotlib-users] plt.close() not releasing memory? Or memory 
leak elsewhere?


On Tue, May 22, 2012 at 8:44 AM, Stevenson, Samuel 
samuel.steven...@coherent.commailto:samuel.steven...@coherent.com 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

--
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
Matplotlib-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-users


[Matplotlib-users] Fwd: [ferret_users] PyFerret (beta) documentation and release available from Ferret website

2012-05-22 Thread Chao YUE
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 karl.sm...@noaa.gov
Date: 2012/5/22
Subject: [ferret_users] PyFerret (beta) documentation and release available
from Ferret website
To: ferret ferret_us...@noaa.gov


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

--
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
Matplotlib-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-users


Re: [Matplotlib-users] strange behaviour with sankey diagram (maybe a bug)

2012-05-22 Thread Giovanni

  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

--
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
Matplotlib-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-users


Re: [Matplotlib-users] how to remove colorbar?

2012-05-22 Thread wiswit

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
 Matplotlib-users@lists.sourceforge.net
 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.


--
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
Matplotlib-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-users