matplotlib-users Mailing List for matplotlib (Page 11)

Smith, Frank wrote:
>Help!. I'd like to show traditional "lesser-than-or-equal" and
>"greater-than-or-equal" symbols in a title or label fields but can't
>find anything in the documentation and I've tried a number of guesses
>but to no avail. Given the range of mathematical expressions that
>matplot can support I'm sure there is something better than "<=". Thanks
>in advance.
>Frank
>
>
> 
>
Frank:
Try this:
 >>> from pylab import *
 >>> plot([1,2,3])
 >>> title(u'\N{GREATER-THAN OR EQUAL TO}')
 >>> show()
-Jeff
-- 
Jeffrey S. Whitaker Phone : (303)497-6313
Meteorologist FAX : (303)497-6449
NOAA/OAR/CDC R/CDC1 Email : Jef...@no...
325 Broadway Office : Skaggs Research Cntr 1D-124
Boulder, CO, USA 80303-3328 Web : http://tinyurl.com/5telg

On Wed, 2005年10月05日 at 15:32 -0400, Smith, Frank wrote:
> Help!. I'd like to show traditional "lesser-than-or-equal" and
> "greater-than-or-equal" symbols in a title or label fields but can't
> find anything in the documentation and I've tried a number of guesses
> but to no avail. Given the range of mathematical expressions that
> matplot can support I'm sure there is something better than "<=". Thanks
> in advance.
You can use the \leq latex symbol when using either the mathtext module.
See the screenshots page for a demo of it.
http://matplotlib.sourceforge.net/screenshots/mathtext_demo.py
http://matplotlib.sourceforge.net/screenshots/mathtext_demo_large.png
Also, this page contains a list of latex math symbols.
http://www.fi.uib.no/Fysisk/Teori/KURS/WRK/TeX/symALL.html
Regards,
John
--
John Byrnes (by...@bu...)
Graduate Student
Electrical Engineering
Boston University
To obtain a man's opinion of you, make him mad.
		-- Oliver Wendell Holmes

Help!. I'd like to show traditional "lesser-than-or-equal" and
"greater-than-or-equal" symbols in a title or label fields but can't
find anything in the documentation and I've tried a number of guesses
but to no avail. Given the range of mathematical expressions that
matplot can support I'm sure there is something better than "<=3D". =
Thanks
in advance.
Frank

On 05 Oct, 2005, at 09:25, Nicholas Young wrote:
>
> There's a patch from me on the devel list from sometime ago which
> contains a patch to add an arrowhead marker style to lines. This
> obviously isn't a solution but on the off chance its useful its here:
> http://sourceforge.net/mailarchive/message.php?msg_id=12411835
>
So to apply the patch I can manually edit lines.py
or can I just write my own function. I am not familiar with renderer.
Also your patch mentions a patch.arrow class. Where is that documented?

Hi all,
I've been trying to put my pie-chart into a nice layout. More
specifically, I am wondering whether it is possible to place a label
completely outside the wedges of a pie-chart? My current labels are half
written on top of the pie wedges.
Thanks in advance for any pointers.
Dominik

I'm having trouble compiling 0.84 on Python 2.4 / Ubuntu Hoary (5.04).
It seems like when GCC tries to build ft2font it can't find the two
files referenced in CXX/extensions.hxx and CXX/objects.hxx.
Here are the beginning of the error messages:
(Plenty of things were compiled correctly before this so they don't show up=
):
running build
running build_py
running build_ext
building 'matplotlib.ft2font' extension
gcc -pthread -fno-strict-aliasing -DNDEBUG -g -O3 -Wall
-Wstrict-prototypes -fPIC -I/usr/local/include -I/usr/include
-I/usr/local/include/freetype2 -I/usr/include/freetype2
-I/usr/local/include/python2.4 -c src/ft2font.cpp -o
build/temp.linux-i686-2.4/src/ft2font.o
In file included from src/ft2font.cpp:2:
src/ft2font.h:18:30: CXX/Extensions.hxx: No such file or directory
src/ft2font.h:19:27: CXX/Objects.hxx: No such file or directory
In file included from src/ft2font.cpp:2:
src/ft2font.h:35: error: `Py' is not a class or namespace
src/ft2font.h:35: error: no class template named `PythonExtension' in `Py'
src/ft2font.h:35: error: invalid base-class specification
src/ft2font.h:39: error: parse error before `::' token
src/ft2font.h:40: error: syntax error before `::' token
src/ft2font.h:43: error: syntax error before `::' token
The error messages then scroll off into a world of pain.
I have the default Ubuntu libfreetype2.1.7 installed, and installed
2.1.10 from source (but this problem was identical before I installed
2.1.10 from source). I have no idea if this matters.
I installed (through apt) python-cxx, but this didn't seem to change anythi=
ng.
This seems like a completely trivial problem (especially compared to
the other frutrations I have had with matplotlib in the past), but I
don't know how to fix it...
Any assitance appreciated.
-Chris Mutel

On Wed, 2005年10月05日 at 09:43 -0500, John Hunter wrote:
> I need to plot vectors along a manifold (curve). The quiver plot
> AFAI can tell only plots arrows on a grid not just
> along a curve. In general I need a scatter plot where each plotted
> point is a vector. where (x,y) is the base of vector
> and (u,v) is the vector. The plot could take in arrays X Y U V
> where as in the quiver plot X Y U V are matrices.
> 
> Anyone have any suggestions how I might go about generating such a
> plot even if I have to do it by repurposing something else.
> In general how would I position an arbitrary arrow somewhere on a
> plot?
There's a patch from me on the devel list from sometime ago which
contains a patch to add an arrowhead marker style to lines. This
obviously isn't a solution but on the off chance its useful its here:
http://sourceforge.net/mailarchive/message.php?msg_id=12411835
Nick

Sam Smith is having trouble posting to the list, so I'm posting this
form him
From: "Samuel M. Smith" <sm...@sa...>
Date: 04 October, 2005 22:52:57 MDT
To: mat...@li...
Cc: "Samuel M. Smith" <sm...@sa...>
Subject: Plotting vectors (arrows) on a manifold
I need to plot vectors along a manifold (curve). The quiver plot
AFAI can tell only plots arrows on a grid not just
along a curve. In general I need a scatter plot where each plotted
point is a vector. where (x,y) is the base of vector
and (u,v) is the vector. The plot could take in arrays X Y U V
where as in the quiver plot X Y U V are matrices.
Anyone have any suggestions how I might go about generating such a
plot even if I have to do it by repurposing something else.
In general how would I position an arbitrary arrow somewhere on a
plot?
I suppose I could brute force it by superimposing 3 line plots for
each arrow where each plot draws one part of the arrow ( body, left
head, right head). This amounts to a lot of plots. Is there a
better way?
What would also be useful is a combination of a comet plot with an
arrow pointing in the direction the comet is moving.
This would be great for animation.
**********************************************************************
Samuel M. Smith Ph.D.
2966 Fort Hill Road
Eagle Mountain, Utah 84043
801-768-2768 voice
801-768-2769 fax
**********************************************************************
"The greatest source of failure and unhappiness in the world is
giving up what we want most for what we want at the moment"
**********************************************************************

>>>>> "Robert" == Robert Kern <rk...@uc...> writes:
 Robert> I guess I should officially submit this as a patch:
 Robert> http://article.gmane.org/gmane.comp.python.matplotlib.general/3272/
Added to CVS -- thanks.
Checking in lib/matplotlib/texmanager.py;
/cvsroot/matplotlib/matplotlib/lib/matplotlib/texmanager.py,v <--
texmanager\
.py
new revision: 1.28; previous revision: 1.27
done
JDH

>>>>> "Erik" == Erik Curiel <ec...@ke...> writes:
 Erik> incredibly simple, anyway). After two solid days of
 Erik> commenting this and that out, recompiling everything and its
 Erik> mother 76 different ways from Sunday, poring over a legion
 Erik> of Solaris sys includes, slaughtering a few spotlessly white
 Erik> lambs and one pure black sheep, wrapping the bones and
This information is incredibly helpful -- please do make a wiki entry.
 Erik> There is one remaining item I find extremely puzzling about
 Erik> the whole affair, though. Since I don't have a recent
 Erik> glib/gtk+ library installed, and didn't want to make more
 Erik> hoops for myself to jump through, I attempted to build
 Erik> muhpuhbuh without gtk+ support. Nothing I did would get it
 Erik> to build without gtk+ support, though. I finally commented
 Erik> out every line in setup.py and setupext.py that had anything
 Erik> to with gtk+ (the variables BUILD_GTKAGG, BUILD_GTK, etc.,
 Erik> the conditional code-blocks if BUILD_GTK:, if BUILD_GTKAGG:,
This is totally normal. All the backend_gtk*.py files will be
installed regardless of your setup.py settings. Don't go to any
heroics in that file (eg trying to comment out the build_* funcs as
you did). Just set the advertised flags (eg BUILD_GTKAGG flag). This
will affect what *extension code* gets compiled, but not what python
files get installed. 
Your problem is that you failed to heed my somewhat cryptic advice at
the end of my last post, particularly the bit at the end that I
reproduce here
 Another lurking gotcha along these lines is the backend setting.
 backend : GTKAgg # the default backend
 numerix : Numeric # Numeric or numarray
 As with numerix, the backend setting requires you have the
 appropriate GUI toolkit installed (eg pygtk) often at compile time
 if you want to use a GUI. If you are only doing offline image
 production you can make the backend Agg. See also
 http://matplotlib.sf.net/backends.html.
The basic point which I failed to make clear is that the *runtime
configuration* is independent of the *compile time* configuration.
Yes, this is suboptimal but it is. So you need to change the default
backend which is chosen at runtime in your rc file, as described in
http://matplotlib.sf.net/matplotlibrc. Clear?
matplotlib / pylab does a lot of magic under the hood. In the best of
circumstances, it "just works". Obviously based on your experience we
have a ways to go before this mantra actually holds. One way to tease
apart what mpl is doing under the hood is to create a simple test
script like
 from pylab import plot, show
 plot([1,2,3])
 show()
and run it with
 > python myscript --verbose-helpful
This will show you what rc file is being parsed, what backend is set,
what your numerix setting is, and so forth.
Good luck!
JDH

Dev Gorur wrote:
> Hello,
> 
> I am able to use tex in matplotlib, and it works fine. However, I would
> like to make the default font Helvetica, which is the sans-serif font in
> the latex package times. Of course, I can achieve this effect by putting
> \sf at the beginning of *every* text string. Is there a better way? I
> tried the following:
> --------------------------------------
> from matplotlib import rc
> from matplotlib.font_manager import *
> from pylab import *
> import string
> 
> rc('text', usetex=True)
> 
> f = FontProperties()
> f.set_family('sans-serif')
> f.set_name(['Helvetica'])
> 
> <some plot commands>
> title('Test latex')
> ---------------------------------------
> As expected, this doesn't work - it retains serif as the default tex
> font. Is there a way to change the default tex font?
I guess I should officially submit this as a patch:
http://article.gmane.org/gmane.comp.python.matplotlib.general/3272/
-- 
Robert Kern
rk...@uc...
"In the fields of hell where the grass grows high
 Are the graves of dreams allowed to die."
 -- Richard Harter

Hello,
I am able to use tex in matplotlib, and it works fine. However, I would lik=
e
to make the default font Helvetica, which is the sans-serif font in the
latex package times. Of course, I can achieve this effect by putting \sf at
the beginning of *every* text string. Is there a better way? I tried the
following:
--------------------------------------
from matplotlib import rc
from matplotlib.font_manager import *
from pylab import *
import string
rc('text', usetex=3DTrue)
f =3D FontProperties()
f.set_family('sans-serif')
f.set_name(['Helvetica'])
<some plot commands>
title('Test latex')
---------------------------------------
As expected, this doesn't work - it retains serif as the default tex font.
Is there a way to change the default tex font?
Regards,
Dev

> Hi Erik -- if you succeed, then we'll have convincing proof that
> compiling mpl on solaris is easier than giving up the sauce.
Well, it has turned out to be easier than giving up the sauce (at least
for me), but only by a whisker. In the end, the fix is incredibly simple
(if you consider recompiling python and manually adjusting the
auto-produced pyconfig.h incredibly simple, anyway). After two solid days
of commenting this and that out, recompiling everything and its mother 76
different ways from Sunday, poring over a legion of Solaris sys includes,
slaughtering a few spotlessly white lambs and one pure black sheep,
wrapping the bones and tendons and viscera in a double layer of fat and
burning the offering to Delphic Apollo, I found the answer:
1) download Python 2.4.2
2) after extracting it and running ./configure, edit the generated
pyconfig.h as follows:
	i) if _XOPEN_SOURCE is defined to be 600 (i.e., if the line
	"#define _XOPEN_SOURCE 600" appears in the file), redefine it to
	500
	ii) if _XOPEN_SOURCE_EXTENDED is defined at all (i.e. if the line
 "#define _XOPEN_SOURCE_EXTENDED 1" appears in the file),
	comment out its definition
3) make && make install
The problem was with Solaris's support for the X/Open standards. To make
a long story short, you can use Open Group Technical Standard, Issue 6
(XPG6/UNIX 03/SUSv3) (_XOPEN_SOURCE == 600) if and only if you are using
an ISO C99 compiler. If you use X/Open CAE Specification, Issue 5
(XPG5/UNIX 98/SUSv2) (_XOPEN_SOURCE == 500), you don't have to use an ISO
C99 compiler. For full details, see the Solaris header file
/usr/include/sys/feature_tests.h.
This is why muhpubuh (AKA matplotlib---long story) compiles
on Solaris 10 if you have the big bucks and can afford Sun's OpenStudio 10
compiler. gcc does not have full C99 support yet. In particular, its
lack of support for the wide character library makes the build go
bust. (See, e.g., http://gcc.gnu.org/c99status.html.)
There is one remaining item I find extremely puzzling about the whole
affair, though. Since I don't have a recent glib/gtk+ library installed,
and didn't want to make more hoops for myself to jump through, I attempted
to build muhpuhbuh without gtk+ support. Nothing I did would get it to
build without gtk+ support, though. I finally commented out every line in
setup.py and setupext.py that had anything to with gtk+ (the variables
BUILD_GTKAGG, BUILD_GTK, etc., the conditional code-blocks if BUILD_GTK:,
if BUILD_GTKAGG:, etc., the functions build_gdk, build_gtkagg, etc.), but
to no avail. There, in my
local/lib/python2.4/site-packages/matplotlib/backends/, big as life, are
backend_gtk.py, backend_gtkagg.py, etc. When I tried to import pylab from
the command-line interpreter, I naturally got lots of errors from those
spurious backends complaining about not being able to find libgobject.so,
etc. I finally had to manually change the backend parameter in my
.matplotlibrc to TkAgg to get it to work. What's up with that?
E

Travis Brady wrote:
>I'd like to make a map of the U.S. where I draw the state lines and
>apply a color to each state based on a ratio I've got in my data. I'm
>staring at the example here:
>http://matplotlib.sourceforge.net/screenshots/plotmap.py, but what I'm
>trying to do is much simpler so I'm wondering if there's a helper
>function somewhere.
>
>thanks,
>
>Travis
> 
>
Travis: I posted an example of how to color state polygons with random 
colors earlier - here's a modification that colors the states based on 
population density. It shows how to use a colormap to choose the colors 
based upon your data - I think this is closer to what you were asking for.
-Jeff
-- 
Jeffrey S. Whitaker Phone : (303)497-6313
Meteorologist FAX : (303)497-6449
NOAA/OAR/CDC R/CDC1 Email : Jef...@no...
325 Broadway Office : Skaggs Research Cntr 1D-124
Boulder, CO, USA 80303-3328 Web : http://tinyurl.com/5telg

>>>>> "Jeff" == Jeff Peery <jef...@se...> writes:
 Jeff> I know this bug has already been posted. I was wondering if
 Jeff> there is a way to get around it? ... 
Use scatter, which is functionally equivalent and supports alpha.
JDH

>>>>> "Erik" == Erik Curiel <ec...@ke...> writes:
 Erik> interpreter. Any suggestions about where to start looking,
 Erik> and what to look for, to debug this will be greatly
 Erik> appreciated.
 Erik> _transforms_module::new_value _transforms_module::new_value
 Erik> _transforms_module::new_point Point::Point
 Erik> _transforms_module::new_value _transforms_module::new_value
 ...snip snip
You have VERBOSE=True in setup.py. While this is fine, it's really
only useful when debugging segfaults in the extension code (not python
exceptions). When debugging python level problems, it suffices to run
with 
 > python myscript.py --verbose-helpful
 > python myscript.py --verbose-debug
The default verbose setting is set in your rc file
http://matplotlib.sf.net/matplotlibrc
 Erik> line 9, in ? from backend_agg import FigureCanvasAgg File
 Erik> "/home/erik/util/lib/python2.4/site-packages/matplotlib/backends/backend_agg.py",
 Erik> line 94, in ? from _nc_backend_agg import RendererAgg as
 Erik> _RendererAgg ImportError: No module named _nc_backend_agg
Hmmm.. Do you have Numeric installed? Ie, in the environment in
which you are building, can you do
> python
>>> import Numeric
matplotlib supports both Numeric and numarray via the numerix module,
and builds two extensions for each extension code module, ie,
_nc_backend_agg and _na_backend_agg. Which one it builds depends on
what it finds at compile time (Numeric or numarray). If for example
you have only numarray installed, it will build only for numarray.
Unfortunately, the rc file is pretty dumb, and doesn't reflect these
dynamic compile time settings. 
But the default rc setting for numerix is Numeric. My guess is that
this is your problem, and can be fixed either by setting numerix :
numarray or installing Numeric and recompiling.
In any case, you will want to turn off VERBOSE in setup.py, flush the
build subdir, and recompile.
Another lurking gotcha along these lines is the backend setting.
 backend : GTKAgg # the default backend
 numerix : Numeric # Numeric or numarray
As with numerix, the backend setting requires you have the appropriate
GUI toolkit installed (eg pygtk) often at compile time if you want to
use a GUI. If you are only doing offline image production you can
make the backend Agg. See also 
 http://matplotlib.sf.net/backends.html.
JDH

I finally got the thing to compile. What I had to do was long and
involved. I'll write it up and slap it on the wiki when I am confident I
know what's going on. For the moment, however, even though it compiles, I
still don't think I know what's going on. I get the following messages
and terminating error when I try to import pylab from the python
interpreter. Any suggestions about where to start looking, and what to
look for, to debug this will be greatly appreciated.
Thanks!
E
$ python
Python 2.4.2 (#1, Oct 3 2005, 14:10:19)
[GCC 3.4.4] on sunos5
Type "help", "copyright", "credits" or "license" for more information.
>>> import pylab
LazyValue::init_type
Value::init_type
BinOp::init_type
Point::init_type
Interval::init_type
Bbox::init_type
Func::init_type
FuncXY::init_type
Transformation::init_type
SeparableTransformation::init_type
NonseparableTransformation::init_type
Affine::init_type
init_nc_transforms
Glyph::init_type
FT2Font::init_type
_transforms_module::new_value
_transforms_module::new_value
_transforms_module::new_point
Point::Point
_transforms_module::new_value
_transforms_module::new_value
_transforms_module::new_point
Point::Point
_transforms_module::new_bbox
Bbox::Bbox
_transforms_module::new_value
_transforms_module::new_value
_transforms_module::new_point
Point::Point
_transforms_module::new_value
_transforms_module::new_value
_transforms_module::new_point
Point::Point
_transforms_module::new_bbox
Bbox::Bbox
_transforms_module::new_func
_transforms_module::new_func
_transforms_module::new_separable_transformation
BBoxTransformation::BBoxTransformation
SeparableTransformation::SeparableTransformation
init_nc_image
Image::init_type
_transforms_module::new_value
Value::~Value
Traceback (most recent call last):
 File "<stdin>", line 1, in ?
 File "/home/erik/util/lib/python2.4/site-packages/pylab.py", line 1, in
?
 from matplotlib.pylab import *
 File "/home/erik/util/lib/python2.4/site-packages/matplotlib/pylab.py",
line 217, in ?
 new_figure_manager, draw_if_interactive, show = pylab_setup()
 File
"/home/erik/util/lib/python2.4/site-packages/matplotlib/backends/__init__.py",
line 24, in pylab_setup
 globals(),locals(),[backend_name])
 File
"/home/erik/util/lib/python2.4/site-packages/matplotlib/backends/backend_gtkagg.py",
line 9, in ?
 from backend_agg import FigureCanvasAgg
 File
"/home/erik/util/lib/python2.4/site-packages/matplotlib/backends/backend_agg.py",
line 94, in ?
 from _nc_backend_agg import RendererAgg as _RendererAgg
ImportError: No module named _nc_backend_agg

>>>>> "Erik" == Erik Curiel <ec...@ke...> writes:
 Erik> Hi, my name is Erik, and I have a compiling problem. I hope
 Erik> to get it resolved in fewer than 12 steps.
Hi Erik -- if you succeed, then we'll have convincing proof that
compiling mpl on solaris is easier than giving up the sauce.
 Erik> In particular, I'm the Erik Curiel, referred to in this
 Erik> posting from a few months ago by John Hunter, who had (and
 Erik> still has) problems compiling mpb on solaris 10:
 Erik> http://sourceforge.net/mailarchive/message.php?msg_id=12122609
Remind me whether you are using the solaris compiler or gcc. As far
as I know, people have had more luck with gcc so if this is an option
for you, please use it. Skip Montanaro recently got mpl working on
Solaris with a few hacks to the distutils setup, and Nadia has as
well.
Have you googled this error message (I assume you are still getting
this one)?
 "error: `::btowc" has not been declared"
Some posts suggest that it is a bug in the solaris C++ implementation.
Also, did you follow the advice in the paragraphs you linked to,
specifically
 Fourth from the top and was
 http://lists.schmorp.de/pipermail/rxvt-unicode/2005q2/000092.html .
 This thread is not related to matplotlib, and first response there
 isn"t too helpful, but if you follow the rest of the thread you"ll
 get lots of good information. In particular, this response
 (including all the posts in the thread) looks helpful
 http://lists.schmorp.de/pipermail/rxvt-unicode/2005q2/000104.html
If so, do you have anything to report from these attempts?
 Erik> Although I've asked John multiple times to forward me the
 Erik> information from Mike Rightmire and Thomas Wessell, who, it
So many questions, so little time. And a ring to hold to boot.
You'll have to forgive me.
JDH

I installed the fink version of mpl on my 10.3.9 laptop the other day. I've
not been able to work around font problems and am looking for suggestions.
When I run "ipython -pylab" (GTKAgg backend) I get this traceback:
 File "/sw/bin/ipython", line 28, in ?
 IPython.Shell.start().mainloop()
 File "/sw/lib/python2.3/site-packages/IPython/Shell.py", line 883, in start
 return shell()
 File "/sw/lib/python2.3/site-packages/IPython/Shell.py", line 810, in __init__
 IPShellGTK.__init__(self,argv,user_ns,debug,shell_class=MatplotlibMTShell)
 File "/sw/lib/python2.3/site-packages/IPython/Shell.py", line 618, in __init__
 on_kill=[mainquit])
 File "/sw/lib/python2.3/site-packages/IPython/ipmaker.py", line 85, in make_IPython
 IP = shell_class('__IP',user_ns=user_ns,**kw)
 File "/sw/lib/python2.3/site-packages/IPython/Shell.py", line 500, in __init__
 user_ns,b2 = self._matplotlib_config(name)
 File "/sw/lib/python2.3/site-packages/IPython/Shell.py", line 373, in _matplotlib_config
 from matplotlib import backends
 File "/sw/lib/python2.3/site-packages/matplotlib/backends/__init__.py", line 56, in ?
 new_figure_manager, draw_if_interactive, show = pylab_setup()
 File "/sw/lib/python2.3/site-packages/matplotlib/backends/__init__.py", line 24, in pylab_setup
 globals(),locals(),[backend_name])
 File "/sw/lib/python2.3/site-packages/matplotlib/backends/backend_gtkagg.py", line 8, in ?
 from matplotlib.figure import Figure
 File "/sw/lib/python2.3/site-packages/matplotlib/figure.py", line 3, in ?
 from axes import Axes, Subplot, PolarSubplot, PolarAxes
 File "/sw/lib/python2.3/site-packages/matplotlib/axes.py", line 14, in ?
 from axis import XAxis, YAxis
 File "/sw/lib/python2.3/site-packages/matplotlib/axis.py", line 25, in ?
 from font_manager import FontProperties
 File "/sw/lib/python2.3/site-packages/matplotlib/font_manager.py", line 993, in ?
 fontManager = FontManager()
 File "/sw/lib/python2.3/site-packages/matplotlib/font_manager.py", line 837, in __init__
 rebuild()
 File "/sw/lib/python2.3/site-packages/matplotlib/font_manager.py", line 830, in rebuild
 self.ttfdict = createFontDict(self.ttffiles)
 File "/sw/lib/python2.3/site-packages/matplotlib/font_manager.py", line 456, in createFontDict
 font = ft2font.FT2Font(str(fpath))
 RuntimeError: Could not load facefile /Library/Fonts/CharcoalCY.dfont; Unknown_File_Format
I went looking for a solution and found this page:
 http://www.soe.ucsc.edu/~you/notes/matplotlib-fink-install.html
It suggested copying ttf files from Windows, setting TTFPATH and removing
~/.ttfont.cache. Not having Windows, I poked around some more and found
fondu:
 http://fondu.sourceforge.net/
I downloaded and built that, then converted all the fonts in /Library/Fonts,
set TTFPATH and removed ~/.ttfont.cache. No change. Any ideas?
Thx,
-- 
Skip Montanaro
Katrina Benefit Concerts: http://www.musi-cal.com/katrina
sk...@po...

John,
There may be a couple of related questions:
1) For how long do we maintain compatibility with older versions of 
Numeric and numarray? Even if the array interface has been added, or is 
being added, to numarray, it won't be present in older versions or on 
classic Numeric.
2) Even if the array interface is the way to go for the future, it may 
be easier for now to let cntr.c continue to use the Numeric C API, which 
I think is maintained intact in scipy. In fact, doing it this way looks 
very easy indeed.
It may be that I am misunderstanding something fundamental about how the 
array interface works and is implemented; I haven't looked at it closely.
Eric
John Hunter wrote:
>>>>>>"Eric" == Eric Firing <ef...@ha...> writes:
> 
> 
> Eric> To use scipy as a complete replacement for Numeric or
> Eric> numarray will require work in numerix, in the setup.py build
> Eric> system, and possibly in cntr.c, which needs to build
> Eric> separate versions for numarray and Numeric. (I expect little
> Eric> or no change will actually be needed in cntr.c.)
> 
> I talked to Travis about this at scipy and he said that with the new
> array interface, we wouldn't need to compile separate extensions for
> each of Numeric, numarray and scipy (as we do now, eg with
> _nc_transforms, _na_transforms, etc). This is good news because it
> implies shorter compile times and smaller binary distributions, but I
> can't quite understand how this would work yet, eg, to support the
> there packages with one binary *.so). But this may be some of the
> black magic of the new array interface. If correct, this approach
> would require *either* Numeric 24, numarray (something recent) or
> scipy_base.
> 
> Perhaps Todd has further insight, as the author of numerix and
> presumably the implementor of the array interface for numarray...
> 
> JDH

Hi, my name is Erik, and I have a compiling problem. I hope to get it
resolved in fewer than 12 steps.
In particular, I'm the Erik Curiel, referred to in this posting from a few
months ago by John Hunter, who had (and still has) problems compiling mpb
on solaris 10:
http://sourceforge.net/mailarchive/message.php?msg_id=12122609
Although I've asked John multiple times to forward me the information from
Mike Rightmire and Thomas Wessell, who, it would seem, managed to get mpb
to compile on solaris 10 after much effort, he persists in blowing me off
(and this even though he is to be the best man at my wedding in March). I
am hoping that I can extract this information from him by applying the
lever of public shame. 
If John cannot be so easily shamed, would Mike or Thomas please email me
the information? I'll be happy to take responsibility for posting it
somewhere publicly accessible (e.g., the mpb wiki), so poor suckers such
as myself won't have to resort, in the future, to attempting to shame John
in to getting off his ass and disseminating the information.
Thanks!
Erik

Eric Firing wrote:
> No, [new scipy core] *does* include masked arrays.
Someone should tell Paul Dubois then :-) . See the bottom of this thread:
http://sourceforge.net/mailarchive/forum.php?thread_id=8355108&forum_id=4890

>>>>> "Eric" == Eric Firing <ef...@ha...> writes:
 Eric> To use scipy as a complete replacement for Numeric or
 Eric> numarray will require work in numerix, in the setup.py build
 Eric> system, and possibly in cntr.c, which needs to build
 Eric> separate versions for numarray and Numeric. (I expect little
 Eric> or no change will actually be needed in cntr.c.)
I talked to Travis about this at scipy and he said that with the new
array interface, we wouldn't need to compile separate extensions for
each of Numeric, numarray and scipy (as we do now, eg with
_nc_transforms, _na_transforms, etc). This is good news because it
implies shorter compile times and smaller binary distributions, but I
can't quite understand how this would work yet, eg, to support the
there packages with one binary *.so). But this may be some of the
black magic of the new array interface. If correct, this approach
would require *either* Numeric 24, numarray (something recent) or
scipy_base.
Perhaps Todd has further insight, as the author of numerix and
presumably the implementor of the array interface for numarray...
JDH

> Chris Fonnesbeck wrote:
> 
>> I think there is more to it than that. There are all sorts of
>> dependencies on either Numeric or numarray that need to be addressed.
>> Try installing matplotlib without either Numeric or numarray -- I dont
>> think you will get very far.
>> 
>>
> Ah, good point. It would be good to begin work on this, but IMHO the 
> new scipy_core has a bit to go before it is ready for prime time. 
> Someone just pointed out on the numpy list, for example, that it 
> presently does not include masked arrays, a capability I use often and 
> support for which was painstakingly added to Matplotlib over the last 
> year or so.
> 
No, it *does* include masked arrays. Try:
import scipy.base.ma as ma
To use scipy as a complete replacement for Numeric or numarray will 
require work in numerix, in the setup.py build system, and possibly in 
cntr.c, which needs to build separate versions for numarray and Numeric. 
 (I expect little or no change will actually be needed in cntr.c.)
I haven't figured out yet exactly what is present and what is missing 
relative to old Numeric, and the things that numerix imports, so I am 
not sure whether scipy_core has everything needed for a one-to-one 
substitution; it looks like it is close, at least.
Eric

Sascha wrote:
> Try changing the resolution to a value of 300 or 600 dpi. This should
> give you very high quality figures when using the Agg backend. The
> standard is 80 which is ok for screen display but for printing
> purposes you should use a higher value. See
> http://matplotlib.sourceforge.net/matplotlib.pylab.html#-figure (dpi
> keyword argument).
Except that savefig() overrides the Figure dpi, so you need to pass the 
desired dpi in to the savefig function (or method):
savefig(filename, dpi=300)
-Chris
-- 
Christopher Barker, Ph.D.
Oceanographer
 		
NOAA/OR&R/HAZMAT (206) 526-6959 voice
7600 Sand Point Way NE (206) 526-6329 fax
Seattle, WA 98115 (206) 526-6317 main reception
Chr...@no...