matplotlib-users Mailing List for matplotlib (Page 4)

On Jan 22, 2008 11:11 PM,  <dj...@ph...> wrote:

> I checked the instructions on :
> http://matplotlib.sourceforge.net/interactive.html
> and have used the config file there with minor changes for TkAgg and
> interactive mode.  However this also did not work.  Note : again under
> cygwin I placed the file in ~/.matplotlib/matplotlibrc rather than the
> suggested windows location and this seemed to work.
>
> While interactive mode is useful it is not mandatory for what I am doing
> and perhaps the easiest thing to do is set matplotlib to dump all output
> to files...

I have never used mpl under cygwin in windows, but it might help to
make sure your parameters and config files are as you expect.  For
example, in interactive mode, you should not need to call show to get
the figure to appear.  Please report the output of a test script in
the same environment with the --verbose-helpful flag

> python test.py --verbose-helpful

where test.py is something like:

  from pylab import plot, show
  plot([1,2,3])
  show()

this should echo your backedn and interactive settings, as well as the
matplotlibrc file location.

JDH

Just another note:

If you can use wxPython 2.8.*, then this problem should go away. 2.8 
added some methods that allow more directly moving bitmaps from Agg to 
wxPython, eliminating the need for any extension code.

-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...

dj...@ph... writes:

 > On a more general note it seems there are dozens of different ways
 > to run matplotlib under windows.

TkAgg gave me the same set of problems as you on Windows (native).
I was able to use WxAgg instead.  wxPython 2.8 did not work but
switching to 2.6 cured that.  IIRC others hacked some binaries to get
2.8 going.
-- 
Pete Forman                -./\.-  Disclaimer: This post is originated
WesternGeco                  -./\.-   by myself and does not represent
pet...@we...    -./\.-   the opinion of Schlumberger or
http://petef.port5.com           -./\.-   WesternGeco.

Hello Ken,
Hello Mike,
Hello all,

On Tuesday 22 January 2008 19:33, Ken McIvor wrote:
> On Jan 22, 2008, at 11:00 AM, Matthias Michler wrote:
> > I was not up to date with my installation and I tried to use the
> > latest svn
> > version (trunk) on my Debian etch. I have a problem to build
> > matplotlib
> > including support for wxPython as backend. The output is attached
> > below.
> >
> > Actually I cannot find a file "wxPython.h" on my system.
>
> The wxPython Debian packages do not include the development headers
> required to build the WXAgg accelerator module.  The WXAgg backend
> will work just fine without it, so you should disable the module by
> editing setup.cfg and uncommenting the line "wxagg = False" in the
> "gui_support" section.
>
> Please let me know if you haven't created a setup.cfg file and are
> receiving this error straight "out of the box", as that's indicative
> of a bug in the build system.  Thanks!

First of all thanks a lot for your (Mike and Ken) suggestions. I will try it 
later that day.
I'm quite sure I did not create a setup.cfg file before this error message 
occured the first time. I deleted my setup.cfg and the error message seems 
quite similar (it is attached).

thanks again for your help, best regards 
Matthias

Hi there,

I feel like I am really close to getting matplotlib working under
cygwin/ipython (although the problem persists in the conventional python
shell also).

On a more general note it seems there are dozens of different ways to run
matplotlib under windows.  I used as many cygwin packages as seemed
relvant including the cygwin version of python and X etc.  I then
installed numpy and ipython from source (following the linux
instructions).  I tried to install pygtk and wxpython without success
(also from source).  I am a bit confused in this situation when I should
follow windows installation and when I should follow unix e.g. Windows
installers of python packages appear not to work at all...

There were only two minor issues.  I had to run ash / rebaseall

Also I had to create the following symbolic links :

cd /lib
ln -s libtk84.a libtk8.4.a
ln -s libtcl84.a libtcl8.4.a


Anyway my problem is the following :

from pylab import *
from numpy import *
contour(eye(100))
show()

This then produces the image and the function show() blocks on the shell. 
This is all normal behaviour (it also happens in linux).

However If I then close the window and then type :
contour(eye(100))

A "Figure 1" window appears, but nothing happens in it (on linux the
contour plot would reappear).
in this situation show() also does nothing.  From this point on nothing I
do can make the figure plot...

I checked the instructions on :
http://matplotlib.sourceforge.net/interactive.html
and have used the config file there with minor changes for TkAgg and
interactive mode.  However this also did not work.  Note : again under
cygwin I placed the file in ~/.matplotlib/matplotlibrc rather than the
suggested windows location and this seemed to work.

While interactive mode is useful it is not mandatory for what I am doing
and perhaps the easiest thing to do is set matplotlib to dump all output
to files...

Thanks in advance for any help!

David

Hi S=F8ren,

I've put this back on the list in case it's useful to anyone else, or
if there are better suggestions or improvements around. Hope you don't
mind.

On 22/01/2008, S=F8ren Nielsen <sor...@gm...> wrote:
> Yeah i'd like to see your code if I can..

import numpy as n

def get_poly_pts(x, y, shape):
"""Creates convex polygon mask from list of corners.

    Parameters
    ----------
    x : array_like
        x co-ordinates of corners
    y : array_like
        y co-ordinates of corners, in order corresponding to x
    shape : array_like
        dimension sizes of result

    Returns
    -------
    build : ndarray
        2-D array of shape shape with values True inside polygon

    Notes
    -----
    Code is constrained to convex polygons by "inside"
    assessment criterion.

    """
    x =3D n.asarray(x)
    y =3D n.asarray(y)
    shape =3D n.asarray(shape)
    npts =3D x.size # should probably assert x.size =3D=3D y.size
    inds =3D n.indices( shape )
    xs =3D inds[0]
    ys =3D inds[1]
    xav =3D n.round(x.mean()).astype(int)
    yav =3D n.round(y.mean()).astype(int)
    for i in xrange(npts): # iterate over pairs of co-ordinates
        j =3D (i + 1) % npts
        m =3D (y[j] - y[i])/(x[j] - x[i])
        c =3D (x[j] * y[i] - x[i] * y[j])/(x[j] - x[i])
        thisone =3D ( ys > m * xs + c )
        if thisone[xav, yav] =3D=3D False:
            thisone =3D ~thisone
        if i =3D=3D 0:
            build =3D thisone
        else:
            build &=3D thisone
    return build

(released under BSD licence)

> I just needed the push over the edge to know how to draw on the canvas,
> mapping clicks etc. since i'm still fairly new to matplotlib, so I think
> your code will be helpfull.

I hope so. As you can see this code doesn't do any of the drawing or
click collecting, but the cookbook page should be able to guide you
there. Ask again on the list if you have any further questions and
we'll see if we can help.

Also, the code assumes that the average co-ordinate is inside the
shape - that's true for convex polygons, but not necessarily for
arbitrary ones. I use if after taking a convex hull of a greater list
of points (using the delaunay module in scipy (now in scikits, I
hear)), which ensures convexity. You just need to be aware of that
limitation.

Cheers,

A.
--=20
AJC McMorland, PhD candidate
Physiology, University of Auckland

On Jan 22, 2008, at 11:00 AM, Matthias Michler wrote:
>
> I was not up to date with my installation and I tried to use the  
> latest svn
> version (trunk) on my Debian etch. I have a problem to build  
> matplotlib
> including support for wxPython as backend. The output is attached  
> below.
>
> Actually I cannot find a file "wxPython.h" on my system.

The wxPython Debian packages do not include the development headers  
required to build the WXAgg accelerator module.  The WXAgg backend  
will work just fine without it, so you should disable the module by  
editing setup.cfg and uncommenting the line "wxagg = False" in the  
"gui_support" section.

Please let me know if you haven't created a setup.cfg file and are  
receiving this error straight "out of the box", as that's indicative  
of a bug in the build system.  Thanks!

Ken

This is a known bug in the Debian packaging of wxPython.

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=326440

There are some workarounds mentioned in that post.

Personally, I usually end up building wxPython from source (which 
doesn't have this header file problem) to keep up with its fairly 
frequent bugfixes anyway.  If you'd prefer to stick with deb packages, 
you could *try* the wxPython-provided .deb packages (i.e. not the 
Debian-provided ones) here, though I don't know whether they also 
exhibit this problem:

http://wiki.wxpython.org/InstallingOnUbuntuOrDebian

Cheers,
Mike

Matthias Michler wrote:
> Hello list,
> 
> I was not up to date with my installation and I tried to use the latest svn 
> version (trunk) on my Debian etch. I have a problem to build matplotlib 
> including support for wxPython as backend. The output is attached below.
> 
> Actually I cannot find a file "wxPython.h" on my system.
> 
> Can anybody give me a hint what I'm doing wrong?
> How can I find wx headers and tell their location matplotlib?
> 
> best regards and thanks in advance for any hint,
> Matthias
> 
> 
> 
> $ python setup.py build
> ============================================================================
> BUILDING MATPLOTLIB
>             matplotlib: 0.98pre
>                 python: 2.4.4 (#2, Apr  5 2007, 20:11:18)  [GCC 4.1.2
>                         20061115 (prerelease) (Debian 4.1.1-21)]
>               platform: linux2
> 
> REQUIRED DEPENDENCIES
>                  numpy: 1.0.4
>              freetype2: 9.10.3
> 
> OPTIONAL BACKEND DEPENDENCIES
>                 libpng: 1.2.15beta5
>                Tkinter: Tkinter: 39220, Tk: 8.4, Tcl: 8.4
>               wxPython: 2.6.3.2
>                         * Could not find wxPython headers in any of
>                         * '/usr/lib/wx/include/gtk2-unicode-release-2.6',
>                         * '/usr/include/wx-2.6'
>                   Gtk+: gtk+: 2.8.20, glib: 2.12.4, pygtk: 2.8.6, pygobject:
>                         [pre-pygobject]
>                     Qt: Qt: 3.3.6, PyQt: 3.16
>                    Qt4: no
>                  Cairo: 1.2.0
> 
> OPTIONAL DATE/TIMEZONE DEPENDENCIES
>               datetime: present, version unknown
>               dateutil: present, version unknown
>                   pytz: 2006p
> 
> OPTIONAL USETEX DEPENDENCIES
>                 dvipng: 1.9
>            ghostscript: 8.15.3
>                  latex: 3.141592
>                pdftops: 3.01
> 
> EXPERIMENTAL CONFIG PACKAGE DEPENDENCIES
>              configobj: matplotlib will provide
>       enthought.traits: matplotlib will provide
> 
> [Edit setup.cfg to suppress the above messages]
> ============================================================================
> running build
> running build_py
> copying lib/matplotlib/mpl-data/matplotlibrc -> 
> build/lib.linux-i686-2.4/matplotlib/mpl-data
> copying lib/matplotlib/mpl-data/matplotlib.conf -> 
> build/lib.linux-i686-2.4/matplotlib/mpl-data
> running build_ext
> building 'matplotlib.backends._wxagg' extension
> C compiler: 
> gcc -pthread -fno-strict-aliasing -DNDEBUG -g -O2 -Wall -Wstrict-prototypes -fPIC
> 
> compile 
> options: '-DGTK_NO_CHECK_CASTS -D__WXGTK__ -D_FILE_OFFSET_BITS=64 -D_LARGE_FILES -D_LARGEFILE_SOURCE=1 -DNO_GCC_PRAGMA -I/usr/include/libpng12 -I/usr/local/include -I/usr/include -I. -I/var/lib/python-support/python2.4/numpy/core/include -Isrc -Iagg24/include -I. -I/usr/include/freetype2 -I/usr/local/include -I/usr/include -I. -I/usr/lib/wx/include/gtk2-unicode-release-2.6 -I/usr/include/wx-2.6 -I/usr/include/python2.4 -c'
> gcc: src/_wxagg.cpp
> cc1plus: warning: command line option "-Wstrict-prototypes" is valid for 
> Ada/C/ObjC but not for C++
> In file included from /usr/include/python2.4/Python.h:8,
>                  from ./CXX/WrapPython.h:47,
>                  from ./CXX/Extensions.hxx:48,
>                  from src/_backend_agg.h:8,
>                  from src/_wxagg.cpp:48:
> /usr/include/python2.4/pyconfig.h:851:1: warning: "_POSIX_C_SOURCE" redefined
> In file included from /usr/include/string.h:26,
>                  
> from /usr/lib/gcc/i486-linux-gnu/4.1.2/../../../../include/c++/4.1.2/cstring:52,
>                  from src/_wxagg.cpp:38:
> /usr/include/features.h:150:1: warning: this is the location of the previous 
> definition
> src/_wxagg.cpp:55:34: error: wx/wxPython/wxPython.h: No such file or directory
> src/_wxagg.cpp: In member function 'Py::Object 
> _wxagg_module::convert_agg_to_wx_image(const Py::Tuple&)':
> src/_wxagg.cpp:103: error: 'wxPyConstructObject' was not declared in this 
> scope
> src/_wxagg.cpp: In member function 'Py::Object 
> _wxagg_module::convert_agg_to_wx_bitmap(const Py::Tuple&)':
> src/_wxagg.cpp:125: error: 'wxPyConstructObject' was not declared in this 
> scope
> src/_wxagg.cpp: In function 'void init_wxagg()':
> src/_wxagg.cpp:253: error: 'wxPyCoreAPI_IMPORT' was not declared in this scope
> /var/lib/python-support/python2.4/numpy/core/include/numpy/__multiarray_api.h: 
> At global scope:
> /var/lib/python-support/python2.4/numpy/core/include/numpy/__multiarray_api.h:943: 
> warning: 'int _import_array()' defined but not used
> cc1plus: warning: command line option "-Wstrict-prototypes" is valid for 
> Ada/C/ObjC but not for C++
> In file included from /usr/include/python2.4/Python.h:8,
>                  from ./CXX/WrapPython.h:47,
>                  from ./CXX/Extensions.hxx:48,
>                  from src/_backend_agg.h:8,
>                  from src/_wxagg.cpp:48:
> /usr/include/python2.4/pyconfig.h:851:1: warning: "_POSIX_C_SOURCE" redefined
> In file included from /usr/include/string.h:26,
>                  
> from /usr/lib/gcc/i486-linux-gnu/4.1.2/../../../../include/c++/4.1.2/cstring:52,
>                  from src/_wxagg.cpp:38:
> /usr/include/features.h:150:1: warning: this is the location of the previous 
> definition
> src/_wxagg.cpp:55:34: error: wx/wxPython/wxPython.h: No such file or directory
> src/_wxagg.cpp: In member function 'Py::Object 
> _wxagg_module::convert_agg_to_wx_image(const Py::Tuple&)':
> src/_wxagg.cpp:103: error: 'wxPyConstructObject' was not declared in this 
> scope
> src/_wxagg.cpp: In member function 'Py::Object 
> _wxagg_module::convert_agg_to_wx_bitmap(const Py::Tuple&)':
> src/_wxagg.cpp:125: error: 'wxPyConstructObject' was not declared in this 
> scope
> src/_wxagg.cpp: In function 'void init_wxagg()':
> src/_wxagg.cpp:253: error: 'wxPyCoreAPI_IMPORT' was not declared in this scope
> /var/lib/python-support/python2.4/numpy/core/include/numpy/__multiarray_api.h: 
> At global scope:
> /var/lib/python-support/python2.4/numpy/core/include/numpy/__multiarray_api.h:943: 
> warning: 'int _import_array()' defined but not used
> error: 
> Command "gcc -pthread -fno-strict-aliasing -DNDEBUG -g -O2 -Wall -Wstrict-prototypes -fPIC -DGTK_NO_CHECK_CASTS -D__WXGTK__ -D_FILE_OFFSET_BITS=64 -D_LARGE_FILES -D_LARGEFILE_SOURCE=1 -DNO_GCC_PRAGMA -I/usr/include/libpng12 -I/usr/local/include -I/usr/include -I. -I/var/lib/python-support/python2.4/numpy/core/include -Isrc -Iagg24/include -I. -I/usr/include/freetype2 -I/usr/local/include -I/usr/include -I. -I/usr/lib/wx/include/gtk2-unicode-release-2.6 -I/usr/include/wx-2.6 -I/usr/include/python2.4 -c 
> src/_wxagg.cpp -o build/temp.linux-i686-2.4/src/_wxagg.o" failed with exit 
> status 1
> 
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users

-- 
Michael Droettboom
Science Software Branch
Operations and Engineering Division
Space Telescope Science Institute
Operated by AURA for NASA

Hello list,

I was not up to date with my installation and I tried to use the latest svn 
version (trunk) on my Debian etch. I have a problem to build matplotlib 
including support for wxPython as backend. The output is attached below.

Actually I cannot find a file "wxPython.h" on my system.

Can anybody give me a hint what I'm doing wrong?
How can I find wx headers and tell their location matplotlib?

best regards and thanks in advance for any hint,
Matthias



$ python setup.py build
============================================================================
BUILDING MATPLOTLIB
            matplotlib: 0.98pre
                python: 2.4.4 (#2, Apr  5 2007, 20:11:18)  [GCC 4.1.2
                        20061115 (prerelease) (Debian 4.1.1-21)]
              platform: linux2

REQUIRED DEPENDENCIES
                 numpy: 1.0.4
             freetype2: 9.10.3

OPTIONAL BACKEND DEPENDENCIES
                libpng: 1.2.15beta5
               Tkinter: Tkinter: 39220, Tk: 8.4, Tcl: 8.4
              wxPython: 2.6.3.2
                        * Could not find wxPython headers in any of
                        * '/usr/lib/wx/include/gtk2-unicode-release-2.6',
                        * '/usr/include/wx-2.6'
                  Gtk+: gtk+: 2.8.20, glib: 2.12.4, pygtk: 2.8.6, pygobject:
                        [pre-pygobject]
                    Qt: Qt: 3.3.6, PyQt: 3.16
                   Qt4: no
                 Cairo: 1.2.0

OPTIONAL DATE/TIMEZONE DEPENDENCIES
              datetime: present, version unknown
              dateutil: present, version unknown
                  pytz: 2006p

OPTIONAL USETEX DEPENDENCIES
                dvipng: 1.9
           ghostscript: 8.15.3
                 latex: 3.141592
               pdftops: 3.01

EXPERIMENTAL CONFIG PACKAGE DEPENDENCIES
             configobj: matplotlib will provide
      enthought.traits: matplotlib will provide

[Edit setup.cfg to suppress the above messages]
============================================================================
running build
running build_py
copying lib/matplotlib/mpl-data/matplotlibrc -> 
build/lib.linux-i686-2.4/matplotlib/mpl-data
copying lib/matplotlib/mpl-data/matplotlib.conf -> 
build/lib.linux-i686-2.4/matplotlib/mpl-data
running build_ext
building 'matplotlib.backends._wxagg' extension
C compiler: 
gcc -pthread -fno-strict-aliasing -DNDEBUG -g -O2 -Wall -Wstrict-prototypes -fPIC

compile 
options: '-DGTK_NO_CHECK_CASTS -D__WXGTK__ -D_FILE_OFFSET_BITS=64 -D_LARGE_FILES -D_LARGEFILE_SOURCE=1 -DNO_GCC_PRAGMA -I/usr/include/libpng12 -I/usr/local/include -I/usr/include -I. -I/var/lib/python-support/python2.4/numpy/core/include -Isrc -Iagg24/include -I. -I/usr/include/freetype2 -I/usr/local/include -I/usr/include -I. -I/usr/lib/wx/include/gtk2-unicode-release-2.6 -I/usr/include/wx-2.6 -I/usr/include/python2.4 -c'
gcc: src/_wxagg.cpp
cc1plus: warning: command line option "-Wstrict-prototypes" is valid for 
Ada/C/ObjC but not for C++
In file included from /usr/include/python2.4/Python.h:8,
                 from ./CXX/WrapPython.h:47,
                 from ./CXX/Extensions.hxx:48,
                 from src/_backend_agg.h:8,
                 from src/_wxagg.cpp:48:
/usr/include/python2.4/pyconfig.h:851:1: warning: "_POSIX_C_SOURCE" redefined
In file included from /usr/include/string.h:26,
                 
from /usr/lib/gcc/i486-linux-gnu/4.1.2/../../../../include/c++/4.1.2/cstring:52,
                 from src/_wxagg.cpp:38:
/usr/include/features.h:150:1: warning: this is the location of the previous 
definition
src/_wxagg.cpp:55:34: error: wx/wxPython/wxPython.h: No such file or directory
src/_wxagg.cpp: In member function 'Py::Object 
_wxagg_module::convert_agg_to_wx_image(const Py::Tuple&)':
src/_wxagg.cpp:103: error: 'wxPyConstructObject' was not declared in this 
scope
src/_wxagg.cpp: In member function 'Py::Object 
_wxagg_module::convert_agg_to_wx_bitmap(const Py::Tuple&)':
src/_wxagg.cpp:125: error: 'wxPyConstructObject' was not declared in this 
scope
src/_wxagg.cpp: In function 'void init_wxagg()':
src/_wxagg.cpp:253: error: 'wxPyCoreAPI_IMPORT' was not declared in this scope
/var/lib/python-support/python2.4/numpy/core/include/numpy/__multiarray_api.h: 
At global scope:
/var/lib/python-support/python2.4/numpy/core/include/numpy/__multiarray_api.h:943: 
warning: 'int _import_array()' defined but not used
cc1plus: warning: command line option "-Wstrict-prototypes" is valid for 
Ada/C/ObjC but not for C++
In file included from /usr/include/python2.4/Python.h:8,
                 from ./CXX/WrapPython.h:47,
                 from ./CXX/Extensions.hxx:48,
                 from src/_backend_agg.h:8,
                 from src/_wxagg.cpp:48:
/usr/include/python2.4/pyconfig.h:851:1: warning: "_POSIX_C_SOURCE" redefined
In file included from /usr/include/string.h:26,
                 
from /usr/lib/gcc/i486-linux-gnu/4.1.2/../../../../include/c++/4.1.2/cstring:52,
                 from src/_wxagg.cpp:38:
/usr/include/features.h:150:1: warning: this is the location of the previous 
definition
src/_wxagg.cpp:55:34: error: wx/wxPython/wxPython.h: No such file or directory
src/_wxagg.cpp: In member function 'Py::Object 
_wxagg_module::convert_agg_to_wx_image(const Py::Tuple&)':
src/_wxagg.cpp:103: error: 'wxPyConstructObject' was not declared in this 
scope
src/_wxagg.cpp: In member function 'Py::Object 
_wxagg_module::convert_agg_to_wx_bitmap(const Py::Tuple&)':
src/_wxagg.cpp:125: error: 'wxPyConstructObject' was not declared in this 
scope
src/_wxagg.cpp: In function 'void init_wxagg()':
src/_wxagg.cpp:253: error: 'wxPyCoreAPI_IMPORT' was not declared in this scope
/var/lib/python-support/python2.4/numpy/core/include/numpy/__multiarray_api.h: 
At global scope:
/var/lib/python-support/python2.4/numpy/core/include/numpy/__multiarray_api.h:943: 
warning: 'int _import_array()' defined but not used
error: 
Command "gcc -pthread -fno-strict-aliasing -DNDEBUG -g -O2 -Wall -Wstrict-prototypes -fPIC -DGTK_NO_CHECK_CASTS -D__WXGTK__ -D_FILE_OFFSET_BITS=64 -D_LARGE_FILES -D_LARGEFILE_SOURCE=1 -DNO_GCC_PRAGMA -I/usr/include/libpng12 -I/usr/local/include -I/usr/include -I. -I/var/lib/python-support/python2.4/numpy/core/include -Isrc -Iagg24/include -I. -I/usr/include/freetype2 -I/usr/local/include -I/usr/include -I. -I/usr/lib/wx/include/gtk2-unicode-release-2.6 -I/usr/include/wx-2.6 -I/usr/include/python2.4 -c 
src/_wxagg.cpp -o build/temp.linux-i686-2.4/src/_wxagg.o" failed with exit 
status 1

On 22/01/2008, S=F8ren Nielsen <sor...@gm...> wrote:
> I'm looking for a way to do masking of an Image.. I need to be able to ma=
ke
> a circle / box or a user made polygon on an image using the mouse and
> retrieve the pixellocations of all pixels inside the masked area.. (which
> will then be processed later)

I have very recently written some code that creates a binary mask (2-D
array) of an irregular polygon given the co-ordinates of the corners.
It successively uses equations of the line segments between pairs of
neighbouring points around the polygon edge and sets the pixels on the
inner side of those lines. I doubt it's the most efficient code, but
seem so to work, and I'm happy to send you a copy it if it might be
helpful.

> Has anyone tried this? What is the easiest way
> to start? I'm using wxpython for the GUI.

It's relatively easy to capture successive mouse clicks using mpl, and
use those co-ordinates for the polygon calculating code. An example of
capturing mouse co-ordinates is in the cookbook:
http://www.scipy.org/Cookbook/Matplotlib/Interactive_Plotting.

Best regards,

Angus.
--=20
AJC McMorland, PhD candidate
Physiology, University of Auckland

Hi,

I'm looking for a way to do masking of an Image.. I need to be able to make
a circle / box or a user made polygon on an image using the mouse and
retrieve the pixellocations of all pixels inside the masked area.. (which
will then be processed later) Has anyone tried this? What is the easiest way
to start? I'm using wxpython for the GUI.

Thanks!
Soren Nielsen

Hello,

I would like to know if there is a way to plot "broken" axis using
matplotlib. I would like to plot only the left and the right part of a
spectrum, and put a mark on the X axis to show that the axis scaling is
interrupted here.

Thank you,
-- 
Darckense
http://darckense.online.fr

> To use non-ascii characters, you need prefix the string literal with a
> 'u'.  For example:

I thought that the u"string" notation was only needed when characters had to
be handled with their utf-8 code


Replacing the r's with u's in the strings in your example solves the
> problem for me on 0.91.2.  (I wasn't able to test 0.90.1 -- that still
> may have internal problems handling Unicode strings in some backends.)


This works fine for me with the SVN version (matplotlib :  0.98pre) but not
with matplotlib 0.90.1

Thanks

Hi everyone, I've been trying to solve this problem for the last few
days without success. I am afraid that part of the problem is my own
lack of understanding of matplotlib/wx's inner workings, this is my
first attempt to a GUI-tool.

I am using th networkx (https://networkx.lanl.gov/wiki) package to
generate a graph, this graph is according to the API "a pylab friendly
function that will use the current pylab figure axes (e.g. subplot)."

I want to embed this graph in the wx main application window. I've
been trying to do this using the wxmpl-package
(http://agni.phys.iit.edu/~kmcivor/wxmpl/) which creates a wx.Panel
containing a matplotlib.Figure. What I cant manage to do is to get the
networkx-graph (figure? subplot?) into the panel created by wxmpl.

What _does_ work is getting an embedded matplot-graph into the wxPanel
however I cant get the figure created by networkx to be drawn there
instead of an empty one. I think using the set_figure() function would
be a obvious way to do it, but I can't get it to work.

I realise that the problem might not be related to matplotlib at all
but I was hoping someone could give me help/pointers to a solution.

I attatched an .py example that shows what I am trying to do (you will
need wx, matplotlib, wxmpl and networkx).
Thanks!

The pie wedges are approximated using a 72-sided polygon (each side 5 
degrees), rather than a true ellipse.  There is a bug that if the wedge 
is smaller than a half of a side of this polygon (2.5 degrees) it 
creates only one side of the wedge.

This has been fixed on the 0.91.x maintenance branch in SVN r4882.

The SVN trunk uses a completely different approach using bezier curves, 
so doesn't exhibit this problem.

Cheers,
Mike

James Battat wrote:
> It looks like pie() omits slices that are smaller than a few percent.
> 
> In the following example, only one pie slice is drawn:
> 
>>>> import pylab
>>>> pylab.pie([98,2])
>>>> pylab.show()
> 
> The missing pie slice has neither a color fill nor a boundary (the
> arc of the pie slice is missing).
> 
> By contrast, the following works as expected:
>>>> pylab.pie([97,3])
> 
> It seems that the problem occurs for small slices, apparently the
> threshold is around 2-3%.
> 
> Any ideas?
> 
> Thanks in advance,
> James
> 
> 
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users

-- 
Michael Droettboom
Science Software Branch
Operations and Engineering Division
Space Telescope Science Institute
Operated by AURA for NASA

It looks like pie() omits slices that are smaller than a few percent.

In the following example, only one pie slice is drawn:

>>> import pylab
>>> pylab.pie([98,2])
>>> pylab.show()

The missing pie slice has neither a color fill nor a boundary (the
arc of the pie slice is missing).

By contrast, the following works as expected:
>>> pylab.pie([97,3])

It seems that the problem occurs for small slices, apparently the
threshold is around 2-3%.

Any ideas?

Thanks in advance,
James

Rob,

You might try substituting "ax.pcolorfast(data)" for 
"ax.pcolormesh(data)".  It is much faster and uses less memory, unless 
you specify a non-rectilinear grid, in which case it falls back on the 
quadmesh code behind pcolormesh.

pcolorfast is a unification of slightly modified code from image, 
NonUniformImage, and quadmesh.  It is tagged as "experimental" because 
it may need some API tweaks, and maybe a different name.  It is not yet 
exposed via pyplot or pylab interfaces.

The API is similar but not identical to that for pcolormesh; read the 
docstring (and code if necessary) for details.

Eric

To use non-ascii characters, you need prefix the string literal with a 
'u'.  For example:

	u"This is a Unicode string"

Alternatively, you can write out an 8-bit string and then explicitly 
decode it into Unicode:

	unicode("This is UTF-8", "utf-8")

Replacing the r's with u's in the strings in your example solves the 
problem for me on 0.91.2.  (I wasn't able to test 0.90.1 -- that still 
may have internal problems handling Unicode strings in some backends.)

Cheers,
Mike

BL wrote:
> I'm using a basic Debian Etch distribution.
> I've attached a very simple file showing the problem. On my computer, 
> neither the title, nor the legend are displayed correctly, and I've got 
> square instead of each non ascii characters.
> 
> The attached script gives me the following informations :
> 
> matplotlib :  0.90.1
> backend    :  TkAgg
> encoding   :  UTF-8
> 
> I will try to install a SVN version of matplotlib and see if this works 
> better.
> 
> 
> ------------------------------------------------------------------------
> 
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users

-- 
Michael Droettboom
Science Software Branch
Operations and Engineering Division
Space Telescope Science Institute
Operated by AURA for NASA

  Hi,

Is there a way to create annotation or text object at an automatic "best
location", to prevent  different annotation from overlapping each other ?
I've seen the " loc='best' " keyword for the legend  class and I was
wondering is something similar existed for annotation and text.
Otherwise, is-there a way to move the annotation interactively ?


-- 
BL

I'm using a basic Debian Etch distribution.
I've attached a very simple file showing the problem. On my computer,
neither the title, nor the legend are displayed correctly, and I've got
square instead of each non ascii characters.

The attached script gives me the following informations :

matplotlib :  0.90.1
backend    :  TkAgg
encoding   :  UTF-8

I will try to install a SVN version of matplotlib and see if this works
better.

This probably depends on the backend you are using.  Which backend and 
on which platform are you having trouble with?  0.90.1 had a number of 
Unicode and non-ascii problems that 0.91.2 resolves.  You may want to 
try that.

Failing that, can you attach a small script that exhibits the problem? 
There may be all kinds of things going wrong, from the encoding of the 
source file, to an incorrect font etc. and an example would help us 
narrow it down.

Cheers,
Mike

BL wrote:
>    Hi,
>  
> I would like to use non ascii characters in title and label but with my 
> current intallation it does not work properly.
> There's no warning or error messages when I set a title with some non 
> ascii characters (I use iso-88599-1 characters, like é or à), but I get 
> a empty square instead of theses characters in the figure.
>  
> I'm using matplotlib-0.90.1.
> Is there anything to configure to handle non ascii characters ?
>  
> Regards,
>  
> -- 
> BL
>  
>  
>  
> 
> 
> ------------------------------------------------------------------------
> 
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users

-- 
Michael Droettboom
Science Software Branch
Operations and Engineering Division
Space Telescope Science Institute
Operated by AURA for NASA

On Thursday 17 January 2008 09:05:53 am Michael Droettboom wrote:
> Darren Dale wrote:
> > On Wednesday 16 January 2008 08:22:45 am Michael Droettboom wrote:
> >> But reading Darren's new bug report makes me wonder if my fix was
> >> correct.  To be honest, I'm a little confused by the bug report, not out
> >> of any lack of clarity on Darren's part, but I think due to insufficient
> >> understanding of the problem.  As assumption about the purpose of cla is
> >>   that is should return the plot to a pristine state -- and in this case
> >> that means linear axes.  But are you suggesting that sometimes that is
> >> not the case?
> >
> > If you have hold=True, and the x or y scale is log, repeated calls to
> > plot() will add new lines to the plot without changing the scaling. If
> > hold is instead False, one might reasonably expect that future calls to
> > plot would replace the old line with the new one, again without changing
> > the scaling. That would be consistent. Instead, the scaling changes.
>
> That indeed is a problem.  I suspect it has something to do with the
> extra step that log scales do to "round" to the nearest decade.  I can
> have a look when I get a chance, or let me know if you'd like to tackle
> it, Darren.

I don't know when I would have a chance to look into this (my wife and I are 
trying to buy a house). 

Darren

   Hi,

I would like to use non ascii characters in title and label but with my
current intallation it does not work properly.
There's no warning or error messages when I set a title with some non ascii
characters (I use iso-88599-1 characters, like =E9 or =E0), but I get a emp=
ty
square instead of theses characters in the figure.

I'm using matplotlib-0.90.1.
Is there anything to configure to handle non ascii characters ?

Regards,

--=20
BL

I was just wondering if there is any "editor" for the figures done in 
matplotlib. I mean something like the matlab(TM) figure or esayplot for 
QToctave. Since I use a software that use embedded matplotlib and after 
having the plot it could be very helpful to have somthing that can help 
"tweaking" the figure without using command line
Thanks in advance for every hints/suggestion
Giorgio

Hi Adeola,

OpenGL must be expecting a certain "packing" but your image data is 
packed differently. You have (at least) two options: 1) alter your numpy 
arrays to match the packing of OpenGL. This can be done by creating an 
array with the appropriate .strides value. 2) alter OpenGL's idea of how 
the data is packed. For this, see "7. Watch Your Pixel Store Alignment" 
in http://www.opengl.org/resources/features/KilgardTechniques/oglpitfall/ 

-Andrew

Adeola Bannis wrote:
> Hi,
>
> I have a set of images I want to render with OpenGL, and I do this by
> doing some calculations, producing an array, then passing this array
> to OpenGL.  Here's the relevant OpenGL call, for reference:
>
> gluBuild2DMipmaps(GL_TEXTURE_2D, 1, image.shape[0], image.shape[1],
> 							GL_LUMINANCE, GL_UNSIGNED_BYTE, flatImage)
>
> flatImage is just image as a flattened, contiguous numpy array... all
> that matters is that it contains the same values as in image.
>
> The problem is that passing my arrays to pylab.imshow() displays them
> exactly as they are meant to be, but in OpenGL they are 'twisted'.
> There is an offset that is _different_ for each picture that only
> seems to be resolved by replacing 'image.shape[0]' by
> 'image.shape[0]-5' or some other numbers that make the rows shorter.
> How is it that OpenGL does weird things with the row length but pylab
> is always happy?
>
> I can send pictures of the problem if it helps....
>
> Adeola
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
>