On 08.04.2008, at 19:51, Manuel Metz wrote:
> Jochen Küpper wrote:
>>
>> matplotlib creates a contour plot with an x-axes labels of
>> "0.324", ... and adds a "+1" in the lower right corner.
>> Actually, it is often not visible at all.
Hi,
when I create a contour plot with the following grid:
xval = [ 1.3324, 1.9971, 1.00016618]
yval = [250, 260, 270]
data = ones((3,3))
contourf(xval, yval, data)
matplotlib creates a contour plot with an x-axes labels of
"0.324", ... and adds a "+1" in the lower righ
On 04.06.2007, at 23:19, Russell E. Owen wrote:
I've only checked WXAgg and TKAgg on my PPC Mac. If anyone could
test it
on an Intel Mac I would be grateful.
I have tested the MacPorts port of matplotlib 0.90.1 with GTKAgg on
OS X Intel -- that works.
Greetings,
Jochen
--
Einigkeit und R
On 31.05.2007, at 20:34, Jeff Whitaker wrote:
The fink matplotlib package uses GTKAgg as the default backend, and
works fine over an ssh tunnel. The admin will have to:
0) make sure X11.app (and the X11 SDK) is installed.
1) install fink
2) run 'fink selfupdate'
3) run 'fink install matplotlib
On 21.05.2007, at 19:55, Christopher Barker wrote:
Please don't cross-post quite so much!
My apologies for make so much fuzz about this!
(But is a posting to two mailing lists really posted too wide?)
there are some issues with building MPL against wxPython, but it looks
like you've got wxPy
Hi,
I am having problems installing matplotlib-0.90.0 under Mac OS X
(using MacPorts) when having wxPython-2.8.4.0 installed, getting the
following error at build-time:
DEBUG: Assembled command: 'cd "/opt/local/var/db/dports/build/
_Users_jochen_source_macports-trunk_dports_python_py-matpl
On 20.05.2007, at 16:22, David Nordquest wrote:
I recently installed Matplotlib .90 under CentOS 5 (like RHEL 5).
When I
import pylab, it wants numarray rather than the numpy I have
installed.
Do you need both or is there a config file that needs editing?
Edit ~/.matplotlib/matplotlibrc
G
On 12.05.2007, at 16:37, Jouni K. Seppänen wrote:
for the PostScript backend using (I think) dvips with psfrag, and
neither of these is easily generalizable to work with svg or pdf.
What's the problem of using dvi2pdf, dvipdfm, dvipdfmx, or soemthing
like that for PDF?
Looks quite similar
