matplotlib-users Mailing List for matplotlib

hello matplotlib-community,

the x,y,z labels of Axes3D are not oriented in the same 
azimuth/elevation as the plot is and often interferes with the ticks.
is this a known problem and does anybody know how to circumvent this?

thanks a lot!
michael

-- 
Michael Held, Dipl.-Inf.
ETH Zurich
Institute of Biochemistry
HPM E17, Schafmattstrasse 18
8093 Zuerich, Switzerland
Phone: +41 44 632 3148, Fax: +41 44 632 1269
mic...@bc...

Hi,
   I'm trying to build FC4 i386 and x86_64 rpms of matplotlib-0.87.7 with 
GTK and/or GTKAgg backends.

Install Environment:

FC4 i386 
gtk+-devel-1.2.10-39
gtk+-1.2.10-39
numpy-1.0-1
numpy-debuginfo-1.0-1
pygtk2-2.6.2-0.fc4.4
pygtk2-devel-2.6.2-0.fc4.4
pygtk2-libglade-2.6.2-0.fc4.4

X11 is currently running on the box.

Snipit of 'rpmbuild -ba python-matplotlib.spec'

import gtk # directory /usr/lib/python2.4/site-packages/gtk-2.0/gtk
# /usr/lib/python2.4/site-packages/gtk-2.0/gtk/__init__.pyc matches 
/usr/lib/python2.4/site-packages/gtk-2.0/gtk/__init__.py
import gtk # precompiled from 
/usr/lib/python2.4/site-packages/gtk-2.0/gtk/__init__.pyc
dlopen("/usr/lib/python2.4/site-packages/gtk-2.0/gobject.so", 2);
import gobject # dynamically loaded from 
/usr/lib/python2.4/site-packages/gtk-2.0/gobject.so
# /usr/lib/python2.4/site-packages/gtk-2.0/gtk/keysyms.pyc matches 
/usr/lib/python2.4/site-packages/gtk-2.0/gtk/keysyms.py
import gtk.keysyms # precompiled from 
/usr/lib/python2.4/site-packages/gtk-2.0/gtk/keysyms.pyc
dlopen("/usr/lib/python2.4/site-packages/gtk-2.0/gtk/_gtk.so", 2);
# /usr/lib/python2.4/encodings/utf_8.pyc matches 
/usr/lib/python2.4/encodings/utf_8.py
import encodings.utf_8 # precompiled from 
/usr/lib/python2.4/encodings/utf_8.pyc
pygtk present but import failed
import gtk # directory /usr/lib/python2.4/site-packages/gtk-2.0/gtk
# /usr/lib/python2.4/site-packages/gtk-2.0/gtk/__init__.pyc matches 
/usr/lib/python2.4/site-packages/gtk-2.0/gtk/__init__.py
import gtk # precompiled from 
/usr/lib/python2.4/site-packages/gtk-2.0/gtk/__init__.pyc
pygtk present but import failed
TKAgg requires TkInter
# /usr/lib/python2.4/ConfigParser.pyc matches 
/usr/lib/python2.4/ConfigParser.py
import ConfigParser # precompiled from /usr/lib/python2.4/ConfigParser.pyc
# /usr/lib/python2.4/distutils/command/build.pyc matches 
/usr/lib/python2.4/distutils/command/build.py
import distutils.command.build # precompiled from 
/usr/lib/python2.4/distutils/command/build.pyc
running build
running build_py
# /usr/lib/python2.4/distutils/command/build_py.pyc matches 
/usr/lib/python2.4/distutils/command/build_py.py
import distutils.command.build_py # precompiled from 
/usr/lib/python2.4/distutils/command/build_py.pyc
creating build

After building the rpm I can then install it and do the following:

Python 2.4.3 (#1, Jun 13 2006, 16:41:18)
[GCC 4.0.2 20051125 (Red Hat 4.0.2-8)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import pylab
>>> import gtk
>>>

Importing gtk only fails when I run rpmbuild.  I can manually enter 
/usr/src/redhat/SOURCES/matplotlib-0.87.7/ and run 'python setup.py 
build' and get no errors.

TKAgg requires TkInter
running build
running build_py
running build_ext


What am I doing wrong??

Thanks!
Adam Miller

Teemu
> Any ideas where the conflict might be coming from?
When you type from MA import *, you overwrite the definition of 'array'. And 
surprisingly enough, a masked array  in numpy.core.ma is an object 
independent of ndarray. Some functions such as swapaxes are not imported by 
MA (because they were not implemented for one reason or another): you then 
use the regular numpy function, which doesn't know how to deal with these 
'masked arrays' objects. (I simplify a bit, here, but the gist is there)

As you've noticed, the best solution is to use
import MA
That way, you leave the original numpy namespace alone, and are sure to use 
only "MA-approved" functions. But you'll likely gonna have to use MA.sqrt, 
MA.log all over your code. And may run into problems with functions that 
don't handle masked arrays. Still, it's the cleanest solution (the "from blah 
import *" tend to be frowned upon these days anyway).

An alternative solution is to try the new implementation of masked arrays I've 
been working on: with this implementation, masked arrays are subclasses of 
regular arrays, which simplifies life a lot.The source file is available 
here:
http://projects.scipy.org/scipy/numpy/wiki/MaskedArray
Note the disclaimer: it's still a work in progress (even if I use it everyday 
and it works fine) and you'll have to modify a line in the matplotlib source 
to make it work OK with matplotlib, which is a bit tedious I agree. But it 
works. And it's actively maintained.

Hope it helps
P.

Hi,

I downloaded&installed matplotlib 0.87.7 and other binary packages from
pythonmac.org for my new Intel Mac Pro. Then I downloaded and compiled the
latest scipy package. My collection of packages runs ok otherwise but there
seems to be something wrong with pylab/masked array behavior.

This works on my older installations (g5):

import matplotlib
matplotlib.use("TkAgg")
from pylab import *
from MA import *
#import MA
a=arange(100)
a.shape=(5,20)
a=swapaxes(a,0,1)
m=array([1,2,3],mask=[0,1,0])
#m=MA.array([1,2,3],mask=[0,1,0])

On my Intel Mac Pro, I get:
File "test.py", line 12, in ?
    a=swapaxes(a,0,1)
  File
"/Library/Frameworks/Python.framework/Versions/2.4/lib/python2.4/site-packages/numpy/core/fromnumeric.py",
line 106, in swapaxes
    return _wrapit(a, 'swapaxes', axis1, axis2)
  File
"/Library/Frameworks/Python.framework/Versions/2.4/lib/python2.4/site-packages/numpy/core/fromnumeric.py",
line 39, in _wrapit
    result = getattr(asarray(obj),method)(*args, **kwds)
  File
"/Library/Frameworks/Python.framework/Versions/2.4/lib/python2.4/site-packages/numpy/core/numeric.py",
line 132, in asarray
    return array(a, dtype, copy=False, order=order)
ValueError: object __array__ method not producing an array


There seems to be some kind of name space conflict. The line
'a=swapaxes(a,0,1)' works as expected without 'from MA import *'. If I do
'import MA' and use MA.array etc for all operations with masked arrays
everything seems to work fine. 

Any ideas where the conflict might be coming from? 

--
Teemu Rinne
Dept Psychology
University of Helsinki

>>>>> "Christopher" == Christopher Barker <Chr...@no...> writes:

    Christopher> Dav...@no... wrote:
    >> OK, I see (kind of, i.e., via the pylab interface) how to do it
    >> - indirectly, i.e., by catching the click-on-figure event, then
    >> figuring out where that event happened and comparing that to
    >> the locations of the figure's pieces -

    Christopher> Does MPL have some kind of hit-testing built-in? this
    Christopher> seems a bit harder than it should be.

There is an Axes.pick method that will pick on lines, text and
patches.  See examples/picker_demo.py.  I plan on extending and
refining this functionality in the not-too-distant-future.

JDH

Dav...@no... wrote:
> OK, I see (kind of, i.e., via the pylab interface) how to do it -
> indirectly, i.e., by catching the click-on-figure event, then figuring
> out where that event happened and comparing that to the locations of the
> figure's pieces - 

Does MPL have some kind of hit-testing built-in? this seems a bit harder 
than it should be.

> using matplotlib only, so here's hoping that wxmpl has
> made it A) more direct (i.e., provided some way to access a figure's
> pieces seemingly directly, i.e., without having to figure out where in
> the figure those pieces are as an explicit intermediate step), and
> thereby B) easier.

I don't' think so....

However, Mplot may be worth a look-see:

http://cars9.uchicago.edu/~newville/Epics/Python/MPlot/

As far as I can tell, it provides a user-editable plot. However, I can't 
tell with a quick perusal if you can click on an axis and get feedback 
for that.

It would be nice if wxMPL and MPlot shored a code base, but alas -- they 
were started independently.

-Chris


-- 
Christopher Barker, Ph.D.
Oceanographer

Emergency Response Division
NOAA/NOS/OR&R            (206) 526-6959   voice
7600 Sand Point Way NE   (206) 526-6329   fax
Seattle, WA  98115       (206) 526-6317   main reception

Chr...@no...

I'm not sure, but I guess you should make
matplotlib.interactive(False) and matplotlib.use('PS') BEFORE
importing pylab.

Nicolas Grilly

On 11/16/06, Emin.shopper Martinian.shopper <emi...@gm...> wrote:
> Whenever I try to use matplotlib from a python session inside emacs, python
> freezes. What I do is start GNU Emacs version 21.1.3 for Windows, do ESC-x
> shell and enter the commands shown below. Note that I set the backend to PS
> and interactive to false, but my python interpreter still freezes. I suspect
> that this is because matplotlib is generating some GUI events which upset
> emacs. The example works fine if I run python through the shell without
> emacs, but I would very much like to run python through an emacs session.
> Similar problems happen with other backends. Any suggestions on how to solve
> this problem would be much appreciated.