matplotlib-users Mailing List for matplotlib

There appears to be a bug in the latest basemap distrib. (0.3.1) that
prevents it from being installed in a non-standard location. 
In basemap.py, the required data file location is specified as:
_datadir =
os.path.join(sys.prefix,'share/basemap-py'+repr(sys.version_info[0])+rep
r(sys.version_info[1]))
On my system, sys.prefix returns '/usr'. However, I installed the
package using the --prefix option and a different path than /usr. Then
when basemap tries to access data files for coastlines, etc. with
open(os.path.join(_datadir,'gshhs_'+resolution+'.txt'))
it's looking for the files in /usr and they ain't there.
Since I don't have root privileges on my own machine, I can't do a
symbolic link (and that would be tacky anyway). Jeff, could you fix
this? Thanks.
Jeff Orrey

On 2005年4月16日 00:19:37 +0200, Olive <enc...@ya...> wrote
:
> I forgot to take the version number of the freetype library before
> leaving work, I will get it on monday.
> 
Version of freetype is 2.1.7 !

Hi,
The more I am using matplotlib, the more I like it. But using it more 
means I more often hit the limits of the code, so I was wondering if 
there is any plan for a routine to plot data points w.r.t 3 axes (so a 
perspective scatter plot with x,y,z, data and a viewing angle). Of 
course another (maybe more difficult) goal would be to be able to draw 
surfaces, but already a simple scatter plot in 3D would help 
tremendously there (I realize the concept of "axis" has then to be 
revised, but well I have no idea how much effort this is).
(if there is no - coming - plan for this, is there any way around it?)
Please let me know, and congrats for the work already achieved!
Cheers
Eric
-- 
===============================================================
Observatoire de Lyon ems...@ob...
9 av. Charles-Andre tel: +33 4 78 86 83 84
69561 Saint-Genis Laval Cedex fax: +33 4 78 86 83 86
France http://www-obs.univ-lyon1.fr/eric.emsellem
===============================================================

Hi everyone
Last week I stumbled about a bug in imshow, which can easily be 
reproduced by doing the following:
python
 >>> from pylab import *
 >>> imshow(ones((20,40)),aspect='preserve',origin='lower')
 >>> show()
Note that the y-axis is wrong and resizing makes this even worse.
I tried versions 0.71 to 0.80 which show all the same behaviour.
It is obviously the aspect='preserve' option, that introduces this bug.
So I'd like to address two issues:
First of course I'd like to ask if this bug could be fixed since 
constant aspect ratio is very crucial for me.
Second it seems that the plotting area is always maximum size and the 
aspect='preserve' option just rescales the axis. I think it would be 
more natural to rescale the plotting area.
Cheers,
Nikolai

Hi David,
Thanks for the info.
See you
Werner
D Brown wrote:
> Werner,
> 
> Recently I reported a batch plot memory issue when using
> mostly matlab-style commands and TkAgg backend. In my case
> I found that the memory increased when I called close(). 
> If I stopped using this the memory use became more or less
> constant. Based on Fernando Perez's comments I also
> started using import gc and gc.collect() to reduce memory
> use more. This just calls the garbage collector more
> frequently to clean up memory. If your system is paging to
> disk because of memory use it can speed things up quite a
> bit. In my case it keeps the total python footprint
> significantly reduced.
> 
> Good Luck,
> 
> David
> 
> 
>>From: "Werner F. Bruhin" <wer...@fr...>
>>Date: 2005年4月14日 11:42:34 +0200
>>Subject: [Matplotlib-users] Memory usage
> 
> 
>>Hi All,
>>
>>Doing multiple plots I see that memory usage grows and
> 
> grows.
> 
>>Before doing a new plot I do "self.figure.clear()", or 
>>"self.figure.clf()", is there some other call I should
> 
> use?
> 
>>See you
>>Werner
> 
> 
> +_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+
> 
> __________________________________________________
> Do You Yahoo!?
> Tired of spam? Yahoo! Mail has the best spam protection around 
> http://mail.yahoo.com 
> 
> 
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now.
> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

In some of my plots I show month names as axes labels.
When I run this on a machine in "French" (i.e. on Win XP changing the 
Settings - Regional and Language settings" to French the labels don't 
show correctly if there is an accented character in there e.g. "déc".
I changed the line 256 in dates.py (matplotlib 0.8) from:
return dt.strftime(fmt)
to:
return unicode(dt.strftime(fmt), 'iso-8859-1')
Obviously this is not a correct fix as it will only work in some situations.
I tried to use sys.getdefaultencoding(), instead of hard coding 
'iso-8859-1', but on my machine it returns "ascii".
Any suggestions on how to handle this correctly will be very appreciated.
See you
Werner

Hi Stephen,
On Fri, Apr 15, 2005 at 10:01:30AM -0700, Stephen Walton wrote:
> What I really meant was that the PostScript file produced by MPL starts=
=20
> with '%!PS-Adobe-3.0', which I thought meant Postscript level 3. =20
> Changing the 3.0 to 2.0 by hand still doesn't allow it to print. dvips=
=20
> output files print fine on this printer, and they start with=20
> '%!PS-Adobe-2.0'.
Confusingly enough there are two kinds of version numbers involved, here.
There is the PostScript language level, which can be 1, 2, or 3.
Additionally there is something called DSC (Document structuring
conventions), which gives additional information in PostScript comments
(lines starting with a percent sign). This DSC thing allows PostScript
viewers to go back to the previous page, allows to print single pages
=66rom a PostScript file, etc. DSC also comes in several versions.
The "%!PS-Adobe-3.0" indicated that the document confirms to DSC version 3.
This does not imply anything for the PostScript language level. Since
all DSC stuff is most probably ignored by the Printer, it should not
cause any problems.
> Thanks for the suggestion, but I'm afraid this didn't help. The=20
> workaround I found was to do a dvipdf on the LaTeX file which included=20
> the MPL doc, read it with Acrobat Reader, and tell acroread to print it=
=20
> at Postscript level 1.
GhostScript has also a converting-fancy-PostScript-into-simple-PostScript
functionality which might come in handy here.
All the best,
Jochen
--=20
http://seehuhn.de/

Werner,
Recently I reported a batch plot memory issue when using
mostly matlab-style commands and TkAgg backend. In my case
I found that the memory increased when I called close(). 
If I stopped using this the memory use became more or less
constant. Based on Fernando Perez's comments I also
started using import gc and gc.collect() to reduce memory
use more. This just calls the garbage collector more
frequently to clean up memory. If your system is paging to
disk because of memory use it can speed things up quite a
bit. In my case it keeps the total python footprint
significantly reduced.
Good Luck,
David
>From: "Werner F. Bruhin" <wer...@fr...>
>Date: 2005年4月14日 11:42:34 +0200
>Subject: [Matplotlib-users] Memory usage
>Hi All,
>
>Doing multiple plots I see that memory usage grows and
grows.
>
>Before doing a new plot I do "self.figure.clear()", or 
>"self.figure.clf()", is there some other call I should
use?
>
>See you
>Werner
+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com