matplotlib-users Mailing List for matplotlib (Page 118)

I am new to python and when using Matplotlib 0.99.1.1 [Scientific Linux
6.3, Python 2.6] to plot I get the following error:

/usr/lib64/python2.6/site-packages/matplotlib/backends/backend_gtk.py:621: DeprecationWarning: Use the new widget gtk.Tooltip
  self.tooltips = gtk.Tooltips()

This is when the program reaches:

	plt.show()

Where plt is the matplotlib.pyplot. Prior to this point of the code I am
able to produce pdf files of the figure by using plt.savefig(fname).

Reading other online comments I have tried to update Matplotlib. First I
installed the dependences via

	sudo yum-builddep python-matplotlib

Then:

	sudo yum install matplotlib

This then tells me that I have the latest version of matplotlib and
therefore does nothing. There are more recent versions available from
the Matplotlib website. I tried to install the latest version after
unpacking the tar.gz file. After using the command:

	sudo python setup.py install

I get the message below ending with error: 

	command 'gcc' failed with exit status 1

Can anyone suggest a way to install the latest matplotlib or stop the
message I get with using plt.show()?

Jonathan





basedirlist is: ['/usr/local', '/usr', 'usr/lib64']
============================================================================
BUILDING MATPLOTLIB
            matplotlib: 1.2.1
                python: 2.6.6 (r266:84292, Jun 18 2012, 09:57:52)  [GCC
                        4.4.6 20110731 (Red Hat 4.4.6-3)]
              platform: linux2

REQUIRED DEPENDENCIES
                 numpy: 1.4.1
             freetype2: 9.22.3

OPTIONAL BACKEND DEPENDENCIES
                libpng: 1.2.49
               Tkinter: Tkinter: 73770, Tk: 8.5, Tcl: 8.5
                        * Guessing the library and include directories
for
                        * Tcl and Tk because the tclConfig.sh and
                        * tkConfig.sh could not be found and/or parsed.
                  Gtk+: gtk+: 2.18.9, glib: 2.22.5, pygtk: 2.16.0,
                        pygobject: 2.20.0
       Mac OS X native: no
                    Qt: no
                   Qt4: Qt: 4.6.2, PyQt4: 4.7.4
                PySide: no
                 Cairo: 1.8.6

OPTIONAL DATE/TIMEZONE DEPENDENCIES
              dateutil: 1.4.1
                  pytz: 2010h

OPTIONAL USETEX DEPENDENCIES
                dvipng: no
           ghostscript: 8.70
                 latex: 3.141592
               pdftops: 0.12.4

[Edit setup.cfg to suppress the above messages]
============================================================================
pymods ['pylab']
packages ['matplotlib', 'matplotlib.backends',
'matplotlib.backends.qt4_editor', 'matplotlib.projections',
'matplotlib.testing', 'matplotlib.testing.jpl_units',
'matplotlib.tests', 'mpl_toolkits', 'mpl_toolkits.mplot3d',
'mpl_toolkits.axes_grid', 'mpl_toolkits.axes_grid1',
'mpl_toolkits.axisartist', 'matplotlib.sphinxext', 'matplotlib.tri',
'matplotlib.delaunay']
running install
running build
running build_py
copying lib/matplotlib/mpl-data/matplotlibrc ->
build/lib.linux-x86_64-2.6/matplotlib/mpl-data
running build_ext
building 'matplotlib.backends._backend_agg' extension
gcc -pthread -fno-strict-aliasing -O2 -g -pipe -Wall
-Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector
--param=ssp-buffer-size=4 -m64 -mtune=generic -D_GNU_SOURCE -fPIC
-fwrapv -DNDEBUG -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions
-fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic
-D_GNU_SOURCE -fPIC -fwrapv -fPIC -DPY_ARRAY_UNIQUE_SYMBOL=MPL_ARRAY_API
-DPYCXX_ISO_CPP_LIB=1 -I/usr/local/include -I/usr/include
-Iusr/lib64/include -Iusr/lib64/python2.6/include
-Iusr/lib64/python2.6/site-packages/include
-I/usr/lib64/python2.6/site-packages/numpy/core/include
-I/usr/local/include -I/usr/include -I.
-I/usr/lib64/python2.6/site-packages/numpy/core/include -Isrc
-Iagg24/include -I.
-I/usr/lib64/python2.6/site-packages/numpy/core/include
-I/usr/include/freetype2 -I/usr/local/include -I/usr/include -I.
-I/usr/include/python2.6 -c agg24/src/agg_trans_affine.cpp -o
build/temp.linux-x86_64-2.6/agg24/src/agg_trans_affine.o
gcc -pthread -fno-strict-aliasing -O2 -g -pipe -Wall
-Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector
--param=ssp-buffer-size=4 -m64 -mtune=generic -D_GNU_SOURCE -fPIC
-fwrapv -DNDEBUG -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions
-fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic
-D_GNU_SOURCE -fPIC -fwrapv -fPIC -DPY_ARRAY_UNIQUE_SYMBOL=MPL_ARRAY_API
-DPYCXX_ISO_CPP_LIB=1 -I/usr/local/include -I/usr/include
-Iusr/lib64/include -Iusr/lib64/python2.6/include
-Iusr/lib64/python2.6/site-packages/include
-I/usr/lib64/python2.6/site-packages/numpy/core/include
-I/usr/local/include -I/usr/include -I.
-I/usr/lib64/python2.6/site-packages/numpy/core/include -Isrc
-Iagg24/include -I.
-I/usr/lib64/python2.6/site-packages/numpy/core/include
-I/usr/include/freetype2 -I/usr/local/include -I/usr/include -I.
-I/usr/include/python2.6 -c agg24/src/agg_bezier_arc.cpp -o
build/temp.linux-x86_64-2.6/agg24/src/agg_bezier_arc.o
gcc -pthread -fno-strict-aliasing -O2 -g -pipe -Wall
-Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector
--param=ssp-buffer-size=4 -m64 -mtune=generic -D_GNU_SOURCE -fPIC
-fwrapv -DNDEBUG -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions
-fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic
-D_GNU_SOURCE -fPIC -fwrapv -fPIC -DPY_ARRAY_UNIQUE_SYMBOL=MPL_ARRAY_API
-DPYCXX_ISO_CPP_LIB=1 -I/usr/local/include -I/usr/include
-Iusr/lib64/include -Iusr/lib64/python2.6/include
-Iusr/lib64/python2.6/site-packages/include
-I/usr/lib64/python2.6/site-packages/numpy/core/include
-I/usr/local/include -I/usr/include -I.
-I/usr/lib64/python2.6/site-packages/numpy/core/include -Isrc
-Iagg24/include -I.
-I/usr/lib64/python2.6/site-packages/numpy/core/include
-I/usr/include/freetype2 -I/usr/local/include -I/usr/include -I.
-I/usr/include/python2.6 -c agg24/src/agg_curves.cpp -o
build/temp.linux-x86_64-2.6/agg24/src/agg_curves.o
gcc -pthread -fno-strict-aliasing -O2 -g -pipe -Wall
-Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector
--param=ssp-buffer-size=4 -m64 -mtune=generic -D_GNU_SOURCE -fPIC
-fwrapv -DNDEBUG -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions
-fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic
-D_GNU_SOURCE -fPIC -fwrapv -fPIC -DPY_ARRAY_UNIQUE_SYMBOL=MPL_ARRAY_API
-DPYCXX_ISO_CPP_LIB=1 -I/usr/local/include -I/usr/include
-Iusr/lib64/include -Iusr/lib64/python2.6/include
-Iusr/lib64/python2.6/site-packages/include
-I/usr/lib64/python2.6/site-packages/numpy/core/include
-I/usr/local/include -I/usr/include -I.
-I/usr/lib64/python2.6/site-packages/numpy/core/include -Isrc
-Iagg24/include -I.
-I/usr/lib64/python2.6/site-packages/numpy/core/include
-I/usr/include/freetype2 -I/usr/local/include -I/usr/include -I.
-I/usr/include/python2.6 -c agg24/src/agg_vcgen_dash.cpp -o
build/temp.linux-x86_64-2.6/agg24/src/agg_vcgen_dash.o
gcc -pthread -fno-strict-aliasing -O2 -g -pipe -Wall
-Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector
--param=ssp-buffer-size=4 -m64 -mtune=generic -D_GNU_SOURCE -fPIC
-fwrapv -DNDEBUG -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions
-fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic
-D_GNU_SOURCE -fPIC -fwrapv -fPIC -DPY_ARRAY_UNIQUE_SYMBOL=MPL_ARRAY_API
-DPYCXX_ISO_CPP_LIB=1 -I/usr/local/include -I/usr/include
-Iusr/lib64/include -Iusr/lib64/python2.6/include
-Iusr/lib64/python2.6/site-packages/include
-I/usr/lib64/python2.6/site-packages/numpy/core/include
-I/usr/local/include -I/usr/include -I.
-I/usr/lib64/python2.6/site-packages/numpy/core/include -Isrc
-Iagg24/include -I.
-I/usr/lib64/python2.6/site-packages/numpy/core/include
-I/usr/include/freetype2 -I/usr/local/include -I/usr/include -I.
-I/usr/include/python2.6 -c agg24/src/agg_vcgen_stroke.cpp -o
build/temp.linux-x86_64-2.6/agg24/src/agg_vcgen_stroke.o
gcc -pthread -fno-strict-aliasing -O2 -g -pipe -Wall
-Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector
--param=ssp-buffer-size=4 -m64 -mtune=generic -D_GNU_SOURCE -fPIC
-fwrapv -DNDEBUG -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions
-fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic
-D_GNU_SOURCE -fPIC -fwrapv -fPIC -DPY_ARRAY_UNIQUE_SYMBOL=MPL_ARRAY_API
-DPYCXX_ISO_CPP_LIB=1 -I/usr/local/include -I/usr/include
-Iusr/lib64/include -Iusr/lib64/python2.6/include
-Iusr/lib64/python2.6/site-packages/include
-I/usr/lib64/python2.6/site-packages/numpy/core/include
-I/usr/local/include -I/usr/include -I.
-I/usr/lib64/python2.6/site-packages/numpy/core/include -Isrc
-Iagg24/include -I.
-I/usr/lib64/python2.6/site-packages/numpy/core/include
-I/usr/include/freetype2 -I/usr/local/include -I/usr/include -I.
-I/usr/include/python2.6 -c agg24/src/agg_image_filters.cpp -o
build/temp.linux-x86_64-2.6/agg24/src/agg_image_filters.o
gcc -pthread -fno-strict-aliasing -O2 -g -pipe -Wall
-Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector
--param=ssp-buffer-size=4 -m64 -mtune=generic -D_GNU_SOURCE -fPIC
-fwrapv -DNDEBUG -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions
-fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic
-D_GNU_SOURCE -fPIC -fwrapv -fPIC -DPY_ARRAY_UNIQUE_SYMBOL=MPL_ARRAY_API
-DPYCXX_ISO_CPP_LIB=1 -I/usr/local/include -I/usr/include
-Iusr/lib64/include -Iusr/lib64/python2.6/include
-Iusr/lib64/python2.6/site-packages/include
-I/usr/lib64/python2.6/site-packages/numpy/core/include
-I/usr/local/include -I/usr/include -I.
-I/usr/lib64/python2.6/site-packages/numpy/core/include -Isrc
-Iagg24/include -I.
-I/usr/lib64/python2.6/site-packages/numpy/core/include
-I/usr/include/freetype2 -I/usr/local/include -I/usr/include -I.
-I/usr/include/python2.6 -c src/mplutils.cpp -o
build/temp.linux-x86_64-2.6/src/mplutils.o
In file included from /usr/include/python2.6/pyconfig.h:6,
                 from /usr/include/python2.6/Python.h:8,
                 from src/mplutils.h:18,
                 from src/mplutils.cpp:6:
/usr/include/python2.6/pyconfig-64.h:1034:1: warning: "_POSIX_C_SOURCE"
redefined
In file included
from /usr/lib/gcc/x86_64-redhat-linux/4.4.6/../../../../include/c
++/4.4.6/x86_64-redhat-linux/bits/os_defines.h:39,

from /usr/lib/gcc/x86_64-redhat-linux/4.4.6/../../../../include/c
++/4.4.6/x86_64-redhat-linux/bits/c++config.h:1687,

from /usr/lib/gcc/x86_64-redhat-linux/4.4.6/../../../../include/c
++/4.4.6/iostream:39,
                 from src/mplutils.cpp:3:
/usr/include/features.h:162:1: warning: this is the location of the
previous definition
In file included from /usr/include/python2.6/pyconfig.h:6,
                 from /usr/include/python2.6/Python.h:8,
                 from src/mplutils.h:18,
                 from src/mplutils.cpp:6:
/usr/include/python2.6/pyconfig-64.h:1043:1: warning: "_XOPEN_SOURCE"
redefined
In file included
from /usr/lib/gcc/x86_64-redhat-linux/4.4.6/../../../../include/c
++/4.4.6/x86_64-redhat-linux/bits/os_defines.h:39,

from /usr/lib/gcc/x86_64-redhat-linux/4.4.6/../../../../include/c
++/4.4.6/x86_64-redhat-linux/bits/c++config.h:1687,

from /usr/lib/gcc/x86_64-redhat-linux/4.4.6/../../../../include/c
++/4.4.6/iostream:39,
                 from src/mplutils.cpp:3:
/usr/include/features.h:164:1: warning: this is the location of the
previous definition
gcc -pthread -fno-strict-aliasing -O2 -g -pipe -Wall
-Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector
--param=ssp-buffer-size=4 -m64 -mtune=generic -D_GNU_SOURCE -fPIC
-fwrapv -DNDEBUG -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions
-fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic
-D_GNU_SOURCE -fPIC -fwrapv -fPIC -DPY_ARRAY_UNIQUE_SYMBOL=MPL_ARRAY_API
-DPYCXX_ISO_CPP_LIB=1 -I/usr/local/include -I/usr/include
-Iusr/lib64/include -Iusr/lib64/python2.6/include
-Iusr/lib64/python2.6/site-packages/include
-I/usr/lib64/python2.6/site-packages/numpy/core/include
-I/usr/local/include -I/usr/include -I.
-I/usr/lib64/python2.6/site-packages/numpy/core/include -Isrc
-Iagg24/include -I.
-I/usr/lib64/python2.6/site-packages/numpy/core/include
-I/usr/include/freetype2 -I/usr/local/include -I/usr/include -I.
-I/usr/include/python2.6 -c src/agg_py_transforms.cpp -o
build/temp.linux-x86_64-2.6/src/agg_py_transforms.o
gcc -pthread -fno-strict-aliasing -O2 -g -pipe -Wall
-Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector
--param=ssp-buffer-size=4 -m64 -mtune=generic -D_GNU_SOURCE -fPIC
-fwrapv -DNDEBUG -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions
-fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic
-D_GNU_SOURCE -fPIC -fwrapv -fPIC -DPY_ARRAY_UNIQUE_SYMBOL=MPL_ARRAY_API
-DPYCXX_ISO_CPP_LIB=1 -I/usr/local/include -I/usr/include
-Iusr/lib64/include -Iusr/lib64/python2.6/include
-Iusr/lib64/python2.6/site-packages/include
-I/usr/lib64/python2.6/site-packages/numpy/core/include
-I/usr/local/include -I/usr/include -I.
-I/usr/lib64/python2.6/site-packages/numpy/core/include -Isrc
-Iagg24/include -I.
-I/usr/lib64/python2.6/site-packages/numpy/core/include
-I/usr/include/freetype2 -I/usr/local/include -I/usr/include -I.
-I/usr/include/python2.6 -c CXX/cxxsupport.cxx -o
build/temp.linux-x86_64-2.6/CXX/cxxsupport.o
gcc -pthread -fno-strict-aliasing -O2 -g -pipe -Wall
-Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector
--param=ssp-buffer-size=4 -m64 -mtune=generic -D_GNU_SOURCE -fPIC
-fwrapv -DNDEBUG -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions
-fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic
-D_GNU_SOURCE -fPIC -fwrapv -fPIC -DPY_ARRAY_UNIQUE_SYMBOL=MPL_ARRAY_API
-DPYCXX_ISO_CPP_LIB=1 -I/usr/local/include -I/usr/include
-Iusr/lib64/include -Iusr/lib64/python2.6/include
-Iusr/lib64/python2.6/site-packages/include
-I/usr/lib64/python2.6/site-packages/numpy/core/include
-I/usr/local/include -I/usr/include -I.
-I/usr/lib64/python2.6/site-packages/numpy/core/include -Isrc
-Iagg24/include -I.
-I/usr/lib64/python2.6/site-packages/numpy/core/include
-I/usr/include/freetype2 -I/usr/local/include -I/usr/include -I.
-I/usr/include/python2.6 -c CXX/IndirectPythonInterface.cxx -o
build/temp.linux-x86_64-2.6/CXX/IndirectPythonInterface.o
gcc -pthread -fno-strict-aliasing -O2 -g -pipe -Wall
-Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector
--param=ssp-buffer-size=4 -m64 -mtune=generic -D_GNU_SOURCE -fPIC
-fwrapv -DNDEBUG -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions
-fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic
-D_GNU_SOURCE -fPIC -fwrapv -fPIC -DPY_ARRAY_UNIQUE_SYMBOL=MPL_ARRAY_API
-DPYCXX_ISO_CPP_LIB=1 -I/usr/local/include -I/usr/include
-Iusr/lib64/include -Iusr/lib64/python2.6/include
-Iusr/lib64/python2.6/site-packages/include
-I/usr/lib64/python2.6/site-packages/numpy/core/include
-I/usr/local/include -I/usr/include -I.
-I/usr/lib64/python2.6/site-packages/numpy/core/include -Isrc
-Iagg24/include -I.
-I/usr/lib64/python2.6/site-packages/numpy/core/include
-I/usr/include/freetype2 -I/usr/local/include -I/usr/include -I.
-I/usr/include/python2.6 -c CXX/cxx_extensions.cxx -o
build/temp.linux-x86_64-2.6/CXX/cxx_extensions.o
gcc -pthread -fno-strict-aliasing -O2 -g -pipe -Wall
-Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector
--param=ssp-buffer-size=4 -m64 -mtune=generic -D_GNU_SOURCE -fPIC
-fwrapv -DNDEBUG -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions
-fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic
-D_GNU_SOURCE -fPIC -fwrapv -fPIC -DPY_ARRAY_UNIQUE_SYMBOL=MPL_ARRAY_API
-DPYCXX_ISO_CPP_LIB=1 -I/usr/local/include -I/usr/include
-Iusr/lib64/include -Iusr/lib64/python2.6/include
-Iusr/lib64/python2.6/site-packages/include
-I/usr/lib64/python2.6/site-packages/numpy/core/include
-I/usr/local/include -I/usr/include -I.
-I/usr/lib64/python2.6/site-packages/numpy/core/include -Isrc
-Iagg24/include -I.
-I/usr/lib64/python2.6/site-packages/numpy/core/include
-I/usr/include/freetype2 -I/usr/local/include -I/usr/include -I.
-I/usr/include/python2.6 -c CXX/cxxextensions.c -o
build/temp.linux-x86_64-2.6/CXX/cxxextensions.o
gcc -pthread -fno-strict-aliasing -O2 -g -pipe -Wall
-Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector
--param=ssp-buffer-size=4 -m64 -mtune=generic -D_GNU_SOURCE -fPIC
-fwrapv -DNDEBUG -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions
-fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic
-D_GNU_SOURCE -fPIC -fwrapv -fPIC -DPY_ARRAY_UNIQUE_SYMBOL=MPL_ARRAY_API
-DPYCXX_ISO_CPP_LIB=1 -I/usr/local/include -I/usr/include
-Iusr/lib64/include -Iusr/lib64/python2.6/include
-Iusr/lib64/python2.6/site-packages/include
-I/usr/lib64/python2.6/site-packages/numpy/core/include
-I/usr/local/include -I/usr/include -I.
-I/usr/lib64/python2.6/site-packages/numpy/core/include -Isrc
-Iagg24/include -I.
-I/usr/lib64/python2.6/site-packages/numpy/core/include
-I/usr/include/freetype2 -I/usr/local/include -I/usr/include -I.
-I/usr/include/python2.6 -c src/backend_agg.cpp -o
build/temp.linux-x86_64-2.6/src/backend_agg.o
In file included from src/backend_agg.cpp:42:
src/file_compat.h:4:32: error: numpy/npy_3kcompat.h: No such file or
directory
In file included from src/backend_agg.cpp:42:
src/file_compat.h: In function ‘int npy_PyFile_CloseFile(PyObject*)’:
src/file_compat.h:125: warning: deprecated conversion from string
constant to ‘char*’
src/backend_agg.cpp: In member function ‘Py::Object
RendererAgg::write_rgba(const Py::Tuple&)’:
src/backend_agg.cpp:2040: error: ‘npy_PyFile_OpenFile’ was not declared
in this scope
src/backend_agg.cpp:2050: error: ‘npy_PyFile_Dup’ was not declared in
this scope
src/backend_agg.cpp:2054: error: ‘npy_PyFile_DupClose’ was not declared
in this scope
src/backend_agg.cpp:2064: error: ‘npy_PyFile_DupClose’ was not declared
in this scope
error: command 'gcc' failed with exit status 1

On Tue, Jul 2, 2013 at 11:57 PM, Nelle Varoquaux
<nel...@gm...>wrote:

> On 2 July 2013 16:33, Anthony Scopatz <sc...@gm...> wrote:
> >
> > On Tue, Jul 2, 2013 at 9:04 AM, Jason Grout <jas...@cr...
> >
> > wrote:
> >>
> >> On 7/1/13 9:33 AM, Michael Droettboom wrote:
> >> > SciPy 2013 was a great success.  I didn't get good headcount at the
> >> > matplotlib BOF, but it was a good number, and we had 15 participants
> at
> >> > various points during the sprints.  It was nice to see the diversity
> of
> >> > experience with matplotlib at the sprints, and I hope we oldtimers
> were
> >> > helpful to the newtimers getting started so they can continue to
> >> > contribute in the future.  It was also great to put some faces to many
> >> > of the talented names I've been seeing on github and the mailing list
> >> > lately.
> >> >
> >>
> >> On a slightly different, but related topic: is there any chance the
> >> entries (or at least the winning entries) to the plotting contest could
> >> be posted online?
> >
> >
> > Yes, We'll put try to put these on the conference website at the very
> least.
>
> We also talked about adding this to the matplotlib website, but we
> need to sort out first the copyright problems and then coding this
> part of the website.
>

+1

-- 
Damon McDougall
http://www.damon-is-a-geek.com
Institute for Computational Engineering Sciences
201 E. 24th St.
Stop C0200
The University of Texas at Austin
Austin, TX 78712-1229

Not a bother.  This is a fairly common problem because matplotlib, by
design, does not handle layouts for you. If you are looking for an
automated way of handling this, there is plt.tight_layout(), which is a
feature that was added in v1.2, IIRC, that tries adjusting certain spacing
and size parameters automatically in an effort to keep everything inside
the figure space. However, a solution like yours is often perfered because
it gives you explicit control over the plot, and is guaranteed to work the
same way, every time.

Cheers!
Ben Root


On Wed, Jul 3, 2013 at 2:08 PM, Florian Lindner <mai...@xg...> wrote:

> Am Mittwoch, 3. Juli 2013, 20:02:30 schrieb Florian Lindner:
> > Hello!
> >
> > I have that snipped to create a plot:
> >
> > import matplotlib.pyplot as plt
> > size = (6.1, 3.5)
> > fig = plt.figure(figsize=size)
> > plt.xlabel("$x/l_F$")
> >
> > it's being saved as eps for latex. At the size given the "F" from l_F is
> > truncated just a little bit. It works well if I change y-size to 3.6 but
> > that makes latex place to figure on a seperate page which I do not want.
> >
> > Is this behavior by design or a bug? How can I give just 0.1 more
> y-space to
> > the xlabel without altering the overall size?
>
> Ok, I should have read to docu before googling.
>
> plt.xlabel("$x/l_F$", labelpad = -0.1)
> did it.
>
> Sorry for bothering...
>
> Florian
>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Windows:
>
> Build for Windows Store.
>
> http://p.sf.net/sfu/windows-dev2dev
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
>

Am Mittwoch, 3. Juli 2013, 20:02:30 schrieb Florian Lindner:
> Hello!
> 
> I have that snipped to create a plot:
> 
> import matplotlib.pyplot as plt
> size = (6.1, 3.5)
> fig = plt.figure(figsize=size)
> plt.xlabel("$x/l_F$")
> 
> it's being saved as eps for latex. At the size given the "F" from l_F is
> truncated just a little bit. It works well if I change y-size to 3.6 but
> that makes latex place to figure on a seperate page which I do not want.
> 
> Is this behavior by design or a bug? How can I give just 0.1 more y-space to
> the xlabel without altering the overall size?

Ok, I should have read to docu before googling.

plt.xlabel("$x/l_F$", labelpad = -0.1)
did it.

Sorry for bothering...

Florian

Hello!

I have that snipped to create a plot:

import matplotlib.pyplot as plt
size = (6.1, 3.5)
fig = plt.figure(figsize=size)
plt.xlabel("$x/l_F$")

it's being saved as eps for latex. At the size given the "F" from l_F is 
truncated just a little bit. It works well if I change y-size to 3.6 but that 
makes latex place to figure on a seperate page which I do not want.

Is this behavior by design or a bug? How can I give just 0.1 more y-space to 
the xlabel without altering the overall size?

Thanks,
Florian

On Wed, Jul 3, 2013 at 3:13 AM, ChaoYue <cha...@gm...> wrote:

> Thanks Ben. I tried but still confused.
>
> In [8]: fig,ax = plt.subplots()
>
> In [9]: ax.plot(range(100))
> Out[9]: [<matplotlib.lines.Line2D at 0x4cadb50>]
>
> In [10]: ax.get_xticks()
> Out[10]: array([   0.,   20.,   40.,   60.,   80.,  100.])
>
> In [11]: ax.get_yticks()
> Out[11]: array([   0.,   20.,   40.,   60.,   80.,  100.])
>
> In [12]: draw()
>
> In [13]: cs = ax.imshow(np.arange(100).reshape(10,10))
>
> In [14]: draw()
>
> In [15]: cbar = plt.colorbar(cs,ticks=np.arange(0,100,10))
>
> In [16]: cbar.ax.get_yticks()
> Out[16]:
> array([ 0.        ,  0.1010101 ,  0.2020202 ,  0.3030303 ,  0.4040404 ,
>         0.50505051,  0.60606061,  0.70707071,  0.80808081,  0.90909091])
>
> there are many methods avaialbe for cbar.ax.yaxis object:
> In [19]: cbar.ax.yaxis.get*tick*?
> cbar.ax.yaxis.get_major_ticks
> cbar.ax.yaxis.get_majorticklabels
> cbar.ax.yaxis.get_majorticklines
> cbar.ax.yaxis.get_majorticklocs
> cbar.ax.yaxis.get_minor_ticks
> cbar.ax.yaxis.get_minorticklabels
> cbar.ax.yaxis.get_minorticklines
> cbar.ax.yaxis.get_minorticklocs
> cbar.ax.yaxis.get_ticklabel_extents
> cbar.ax.yaxis.get_ticklabels
> cbar.ax.yaxis.get_ticklines
> cbar.ax.yaxis.get_ticklocs
> cbar.ax.yaxis.get_ticks_position
>
> I tried
> In [20]: cbar.ax.yaxis.get_majorticklocs()
> Out[20]:
> array([ 0.        ,  0.1010101 ,  0.2020202 ,  0.3030303 ,  0.4040404 ,
>         0.50505051,  0.60606061,  0.70707071,  0.80808081,  0.90909091])
>
> But it doesn't give the tick locs as the normal axes?
>
> could you explain a bit further?
>
> thanks et cheers,
>
> Chao
>
>
Remember, there is a difference between a tick location, and a tick label.
A colormap works from 0 to 1, so that is its data coordinates.  We merely
label the ticks with the appropriate values.  Try
cbar.ax.yaxis.get_ticklabels().

Cheers!
Ben Root

Thanks Ben. I tried but still confused.

In [8]: fig,ax = plt.subplots()

In [9]: ax.plot(range(100))
Out[9]: [<matplotlib.lines.Line2D at 0x4cadb50>]

In [10]: ax.get_xticks()
Out[10]: array([   0.,   20.,   40.,   60.,   80.,  100.])

In [11]: ax.get_yticks()
Out[11]: array([   0.,   20.,   40.,   60.,   80.,  100.])

In [12]: draw()

In [13]: cs = ax.imshow(np.arange(100).reshape(10,10))

In [14]: draw()

In [15]: cbar = plt.colorbar(cs,ticks=np.arange(0,100,10))

In [16]: cbar.ax.get_yticks()
Out[16]:
array([ 0.        ,  0.1010101 ,  0.2020202 ,  0.3030303 ,  0.4040404 ,
        0.50505051,  0.60606061,  0.70707071,  0.80808081,  0.90909091])

there are many methods avaialbe for cbar.ax.yaxis object:
In [19]: cbar.ax.yaxis.get*tick*?
cbar.ax.yaxis.get_major_ticks
cbar.ax.yaxis.get_majorticklabels
cbar.ax.yaxis.get_majorticklines
cbar.ax.yaxis.get_majorticklocs
cbar.ax.yaxis.get_minor_ticks
cbar.ax.yaxis.get_minorticklabels
cbar.ax.yaxis.get_minorticklines
cbar.ax.yaxis.get_minorticklocs
cbar.ax.yaxis.get_ticklabel_extents
cbar.ax.yaxis.get_ticklabels
cbar.ax.yaxis.get_ticklines
cbar.ax.yaxis.get_ticklocs
cbar.ax.yaxis.get_ticks_position

I tried
In [20]: cbar.ax.yaxis.get_majorticklocs()
Out[20]:
array([ 0.        ,  0.1010101 ,  0.2020202 ,  0.3030303 ,  0.4040404 ,
        0.50505051,  0.60606061,  0.70707071,  0.80808081,  0.90909091])

But it doesn't give the tick locs as the normal axes?

could you explain a bit further?

thanks et cheers,

Chao



On Tue, Jul 2, 2013 at 4:17 PM, Benjamin Root-2 [via matplotlib] <
ml-...@n5...> wrote:

> This is a constant source of confusion.  The colorbar object should be
> thought of as just another subaxes.  To get the ticks, you want the ticks
> from the colorbar's yaxis or xaxis object accordingly.  Of course, I could
> have sworn we added a helper function for this at some point, but I could
> be wrong.
>
> I hope that helps!
> Ben Root
>
>
> On Tue, Jul 2, 2013 at 5:43 AM, Chao YUE <[hidden email]<http://user/SendEmail.jtp?type=node&node=41365&i=0>
> > wrote:
>
>> Dear all matplotlib users,
>>
>> I found there is not a get_ticks method available for colorbar instance,
>> how could I quick get the ticks of a colorbar?
>>
>> thanks,
>>
>> Chao
>> --
>>
>> ***********************************************************************************
>> Chao YUE
>> Laboratoire des Sciences du Climat et de l'Environnement (LSCE-IPSL)
>> UMR 1572 CEA-CNRS-UVSQ
>> Batiment 712 - Pe 119
>> 91191 GIF Sur YVETTE Cedex
>> Tel: (33) 01 69 08 29 02; Fax:01.69.08.77.16
>>
>> ************************************************************************************
>>
>>
>> ------------------------------------------------------------------------------
>> This SF.net email is sponsored by Windows:
>>
>> Build for Windows Store.
>>
>> http://p.sf.net/sfu/windows-dev2dev
>> _______________________________________________
>> Matplotlib-users mailing list
>> [hidden email] <http://user/SendEmail.jtp?type=node&node=41365&i=1>
>> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
>>
>>
>
> ------------------------------------------------------------------------------
>
> This SF.net email is sponsored by Windows:
>
> Build for Windows Store.
>
> http://p.sf.net/sfu/windows-dev2dev
> _______________________________________________
> Matplotlib-users mailing list
> [hidden email] <http://user/SendEmail.jtp?type=node&node=41365&i=2>
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
>
>
> ------------------------------
>  If you reply to this email, your message will be added to the discussion
> below:
>
> http://matplotlib.1069221.n5.nabble.com/quickly-return-colorbar-ticks-tp41361p41365.html
>  To start a new topic under matplotlib - users, email
> ml-...@n5...
> To unsubscribe from matplotlib, click here<http://matplotlib.1069221.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=2&code=Y2hhb3l1ZWpveUBnbWFpbC5jb218MnwxMzg1NzAzMzQx>
> .
> NAML<http://matplotlib.1069221.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>



-- 
***********************************************************************************
Chao YUE
Laboratoire des Sciences du Climat et de l'Environnement (LSCE-IPSL)
UMR 1572 CEA-CNRS-UVSQ
Batiment 712 - Pe 119
91191 GIF Sur YVETTE Cedex
Tel: (33) 01 69 08 29 02; Fax:01.69.08.77.16
************************************************************************************




--
View this message in context: http://matplotlib.1069221.n5.nabble.com/quickly-return-colorbar-ticks-tp41361p41384.html
Sent from the matplotlib - users mailing list archive at Nabble.com.

Thanks Ben. extendrect keyword is in mat 1.3, I didn't try this but I tried
set_under and extend='min'
with mat 1.2 and it works very nice.

cheers,

Chao

On Tue, Jul 2, 2013 at 4:14 PM, Benjamin Root-2 [via matplotlib] <
ml-...@n5...> wrote:

> There is the "set_over" and "set_under" members of a colormap, and the
> plt.colorbar() function takes an "extend='min'" argument to add an extra
> color at the beginning of the colorbar. Setting "extendrect=True", the
> added color will be rectangular instead of triangular.
>
> Hopefully that helps.
>
> Cheers,
> Ben Root
>
>
>
> On Tue, Jul 2, 2013 at 6:14 AM, Chao YUE <[hidden email]<http://user/SendEmail.jtp?type=node&node=41364&i=0>
> > wrote:
>
>> One way I could think of is to make two contingent mat.axes.Axes,
>> with a smaller one setting as white backgroud, and the other bigger on
>> holding the colorbar. Is there some better way?
>>
>> Chao
>>
>>
>> On Tue, Jul 2, 2013 at 12:12 PM, Chao YUE <[hidden email]<http://user/SendEmail.jtp?type=node&node=41364&i=1>
>> > wrote:
>>
>>> Dear all,
>>>
>>> Does anyone have similar experience that to make a colorbar
>>> starting from a different color in the colormap? for example, to
>>> denote the region with invalid data. I attahced a figure to show
>>> what I would like to have, the withe region in the colorbar in the
>>> attahced figure shows no data.
>>>
>>> thanks a lot for any help,
>>>
>>> best,
>>>
>>> Chao
>>>
>>> --
>>>
>>> ***********************************************************************************
>>> Chao YUE
>>> Laboratoire des Sciences du Climat et de l'Environnement (LSCE-IPSL)
>>> UMR 1572 CEA-CNRS-UVSQ
>>> Batiment 712 - Pe 119
>>> 91191 GIF Sur YVETTE Cedex
>>> Tel: (33) 01 69 08 29 02; Fax:01.69.08.77.16
>>>
>>> ************************************************************************************
>>>
>>
>>
>>
>> --
>>
>> ***********************************************************************************
>> Chao YUE
>> Laboratoire des Sciences du Climat et de l'Environnement (LSCE-IPSL)
>> UMR 1572 CEA-CNRS-UVSQ
>> Batiment 712 - Pe 119
>> 91191 GIF Sur YVETTE Cedex
>> Tel: (33) 01 69 08 29 02; Fax:01.69.08.77.16
>>
>> ************************************************************************************
>>
>>
>> ------------------------------------------------------------------------------
>> This SF.net email is sponsored by Windows:
>>
>> Build for Windows Store.
>>
>> http://p.sf.net/sfu/windows-dev2dev
>> _______________________________________________
>> Matplotlib-users mailing list
>> [hidden email] <http://user/SendEmail.jtp?type=node&node=41364&i=2>
>> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
>>
>>
>
> ------------------------------------------------------------------------------
>
> This SF.net email is sponsored by Windows:
>
> Build for Windows Store.
>
> http://p.sf.net/sfu/windows-dev2dev
> _______________________________________________
> Matplotlib-users mailing list
> [hidden email] <http://user/SendEmail.jtp?type=node&node=41364&i=3>
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
>
>
> ------------------------------
>  If you reply to this email, your message will be added to the discussion
> below:
>
> http://matplotlib.1069221.n5.nabble.com/how-to-make-a-colorbar-starting-with-a-different-color-tp41362p41364.html
>  To start a new topic under matplotlib - users, email
> ml-...@n5...
> To unsubscribe from matplotlib, click here<http://matplotlib.1069221.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=2&code=Y2hhb3l1ZWpveUBnbWFpbC5jb218MnwxMzg1NzAzMzQx>
> .
> NAML<http://matplotlib.1069221.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>



-- 
***********************************************************************************
Chao YUE
Laboratoire des Sciences du Climat et de l'Environnement (LSCE-IPSL)
UMR 1572 CEA-CNRS-UVSQ
Batiment 712 - Pe 119
91191 GIF Sur YVETTE Cedex
Tel: (33) 01 69 08 29 02; Fax:01.69.08.77.16
************************************************************************************




--
View this message in context: http://matplotlib.1069221.n5.nabble.com/how-to-make-a-colorbar-starting-with-a-different-color-tp41362p41383.html
Sent from the matplotlib - users mailing list archive at Nabble.com.

On 2 July 2013 16:33, Anthony Scopatz <sc...@gm...> wrote:
>
> On Tue, Jul 2, 2013 at 9:04 AM, Jason Grout <jas...@cr...>
> wrote:
>>
>> On 7/1/13 9:33 AM, Michael Droettboom wrote:
>> > SciPy 2013 was a great success.  I didn't get good headcount at the
>> > matplotlib BOF, but it was a good number, and we had 15 participants at
>> > various points during the sprints.  It was nice to see the diversity of
>> > experience with matplotlib at the sprints, and I hope we oldtimers were
>> > helpful to the newtimers getting started so they can continue to
>> > contribute in the future.  It was also great to put some faces to many
>> > of the talented names I've been seeing on github and the mailing list
>> > lately.
>> >
>>
>> On a slightly different, but related topic: is there any chance the
>> entries (or at least the winning entries) to the plotting contest could
>> be posted online?
>
>
> Yes, We'll put try to put these on the conference website at the very least.

We also talked about adding this to the matplotlib website, but we
need to sort out first the copyright problems and then coding this
part of the website.

Thanks,
Nelle

>
> Be Well
> Anthony
>
>>
>>
>> Thanks,
>>
>> Jason
>>
>>
>>
>> ------------------------------------------------------------------------------
>> This SF.net email is sponsored by Windows:
>>
>> Build for Windows Store.
>>
>> http://p.sf.net/sfu/windows-dev2dev
>> _______________________________________________
>> Matplotlib-users mailing list
>> Mat...@li...
>> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
>
>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Windows:
>
> Build for Windows Store.
>
> http://p.sf.net/sfu/windows-dev2dev
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
>

On вторник, 02 јули 2013 at 11:04 AM, Ian Thomas wrote:
>
>You need to use a matplotlib.tri.Triangulation (your use of triplot does
>this for you behind the scenes anyway), something like:
>
>import matplotlib.tri as mtri
>triang = mtri.Triangulation(xpoints, ypoints)
>
>Now triang.triangles is an array of integers of shape (?, 3) such that
>triang.triangles[i,:] are the three indices of the points that comprise
>triangle i.  You will need to use these to determine the information you
>want.  The triplot example (
>http://matplotlib.org/examples/pylab_examples/triplot_demo.html) 
>does something similar, identifying which triangles are within a 
>particular circle; I guess in your case a simple approach would be to test if 
>the distance from the centre of each triangle edge to your circle of 
>interest is below some threshold or not.

Ian, thanks for you reply

Using threshold like you described is not applicable as there is no 
guarantee of minimum distance between pattern objects.

I wanted to replicate CGAL crust demo in Python, and in the meantime
I found the algorithm by Nina Amenta:

========================================
compute Vor(P);
let V be the Voronoi vertices of Vor(P);
compute Del(P U V);
E := 0;
for each edge pq in Del(P U V) do
  if p in P and q in P
      E := E U pq;
  endif
output E.
========================================

So, Voronoi vertices have property to cluster wanted objects in a manner
that we can use edges of Delaunay triangulation from original points and
Voronoi vertices of that same points, and simply check if they lay on
original points.

I used Deleanay and Voronoi functions from scipy.spatial and worth
mentioning is that I had hard time finding that edges from triangulation
can be found by this command:

========================================
t = Delaunay(PUV)
edges = t.points[t.vertices]
========================================

Cheers


>
>Incidentally, if you have a Triangulation object then subsequent 
>calls to functions like triplot can be of the form triplot(triang), which 
>will be faster than repeated calls to triplot(xpoints, ypoints) as in the 
>latter case a separate Delaunay triangulation needs to be performed for 
>each triplot call.
>
>Ian

Greetings!

Relative newbie here.

I'm trying to plot wind vectors using basemap quiver and to fit my ortho
projection. This is essentially a hack of Jeff Whitaker's animate.py found
at 

https://github.com/matplotlib/basemap/blob/master/examples/animate.py

The data source I'm connecting to, however, has the latitudes in decreasing
order, so I get the "lats and lons must be in increasing order!" exception
when trying to use the transform_vector method which seems to be required to
fit the vectors to the projection.  (ugliness occurs when failing to
transform)

What would be the best way to transform latitudes (to increasing) as needed
by transform_vector, while also accounting for the data order of my u and v
grids?

-kevin.



--
View this message in context: http://matplotlib.1069221.n5.nabble.com/Basemap-transform-vector-for-decreasing-latitudes-tp41375.html
Sent from the matplotlib - users mailing list archive at Nabble.com.

Šand this afternoon, shortly after I sent this email, my test cases for
this approach abruptly stopped functioning. Whoops. So y'all may want to
hold off on this.
(I thought it looked too easyŠ)

Been that kind of day. :)
-jo

On 7/2/13 11:57 AM, "Valentine Cooper, Jo"
<Jo....@na...> wrote:

>Ran into a bug this morning with draggable annotations. It would seem that
>finalize_offset() forcibly overrides the annotation's textcoords status to
>"axes fraction" so it can set the coordinates properly. That's all well
>and good, but if you were using some text coordinates system other than
>"axes fraction" (say, for example, "data"), this can cause fun side
>effects such as annotations that used to pan around with the rest of the
>graph suddenly being frozen in place. :(
>
>Attached is a patch to restore the old textcoords mode in
>finalize_offset(). All it does  is save the old textcoords mode before
>making the change to "axes fraction" and restores it afterwards.
>
>Hope this helps!
>-jo
>
>

[Apologies for cross-posting]

The matplotlib developers want to hear from you!

We are conducting a user survey to determine how and where matplotlib is 
being used in order to focus its further development.

This should only take a couple of minutes.  To fill it out, visit:

https://docs.google.com/spreadsheet/viewform?fromEmail=true&formkey=dHpQS25pcTZIRWdqX0pNckNSU01sMHc6MQ 
<https://docs.google.com/spreadsheet/viewform?fromEmail=true&formkey=dHpQS25pcTZIRWdqX0pNckNSU01sMHc6MQ>

Please forward to your colleagues, particularly those who don't read 
these mailing lists.

Cheers,
Michael Droettboom, and the matplotlib team

Ran into a bug this morning with draggable annotations. It would seem that
finalize_offset() forcibly overrides the annotation's textcoords status to
"axes fraction" so it can set the coordinates properly. That's all well
and good, but if you were using some text coordinates system other than
"axes fraction" (say, for example, "data"), this can cause fun side
effects such as annotations that used to pan around with the rest of the
graph suddenly being frozen in place. :(

Attached is a patch to restore the old textcoords mode in
finalize_offset(). All it does  is save the old textcoords mode before
making the change to "axes fraction" and restores it afterwards.

Hope this helps!
-jo

On 07/02/2013 10:04 AM, Jason Grout wrote:
> On 7/1/13 9:33 AM, Michael Droettboom wrote:
>> SciPy 2013 was a great success.  I didn't get good headcount at the
>> matplotlib BOF, but it was a good number, and we had 15 participants at
>> various points during the sprints.  It was nice to see the diversity of
>> experience with matplotlib at the sprints, and I hope we oldtimers were
>> helpful to the newtimers getting started so they can continue to
>> contribute in the future.  It was also great to put some faces to many
>> of the talented names I've been seeing on github and the mailing list
>> lately.
>>
> On a slightly different, but related topic: is there any chance the
> entries (or at least the winning entries) to the plotting contest could
> be posted online?
>
My understanding is that they will be posted soon, along with the slides 
and other materials from the other papers.

For the impatient, they are in this git repo:

https://github.com/scipy/scipy2013_talks

Mike

On Tue, Jul 2, 2013 at 9:04 AM, Jason Grout <jas...@cr...>wrote:

> On 7/1/13 9:33 AM, Michael Droettboom wrote:
> > SciPy 2013 was a great success.  I didn't get good headcount at the
> > matplotlib BOF, but it was a good number, and we had 15 participants at
> > various points during the sprints.  It was nice to see the diversity of
> > experience with matplotlib at the sprints, and I hope we oldtimers were
> > helpful to the newtimers getting started so they can continue to
> > contribute in the future.  It was also great to put some faces to many
> > of the talented names I've been seeing on github and the mailing list
> > lately.
> >
>
> On a slightly different, but related topic: is there any chance the
> entries (or at least the winning entries) to the plotting contest could
> be posted online?
>

Yes, We'll put try to put these on the conference website at the very least.

Be Well
Anthony


>
> Thanks,
>
> Jason
>
>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Windows:
>
> Build for Windows Store.
>
> http://p.sf.net/sfu/windows-dev2dev
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
>

On 7/1/13 9:33 AM, Michael Droettboom wrote:
> SciPy 2013 was a great success.  I didn't get good headcount at the
> matplotlib BOF, but it was a good number, and we had 15 participants at
> various points during the sprints.  It was nice to see the diversity of
> experience with matplotlib at the sprints, and I hope we oldtimers were
> helpful to the newtimers getting started so they can continue to
> contribute in the future.  It was also great to put some faces to many
> of the talented names I've been seeing on github and the mailing list
> lately.
>

On a slightly different, but related topic: is there any chance the 
entries (or at least the winning entries) to the plotting contest could 
be posted online?

Thanks,

Jason

This is a constant source of confusion.  The colorbar object should be
thought of as just another subaxes.  To get the ticks, you want the ticks
from the colorbar's yaxis or xaxis object accordingly.  Of course, I could
have sworn we added a helper function for this at some point, but I could
be wrong.

I hope that helps!
Ben Root


On Tue, Jul 2, 2013 at 5:43 AM, Chao YUE <cha...@gm...> wrote:

> Dear all matplotlib users,
>
> I found there is not a get_ticks method available for colorbar instance,
> how could I quick get the ticks of a colorbar?
>
> thanks,
>
> Chao
> --
>
> ***********************************************************************************
> Chao YUE
> Laboratoire des Sciences du Climat et de l'Environnement (LSCE-IPSL)
> UMR 1572 CEA-CNRS-UVSQ
> Batiment 712 - Pe 119
> 91191 GIF Sur YVETTE Cedex
> Tel: (33) 01 69 08 29 02; Fax:01.69.08.77.16
>
> ************************************************************************************
>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Windows:
>
> Build for Windows Store.
>
> http://p.sf.net/sfu/windows-dev2dev
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
>
>

There is the "set_over" and "set_under" members of a colormap, and the
plt.colorbar() function takes an "extend='min'" argument to add an extra
color at the beginning of the colorbar. Setting "extendrect=True", the
added color will be rectangular instead of triangular.

Hopefully that helps.

Cheers,
Ben Root



On Tue, Jul 2, 2013 at 6:14 AM, Chao YUE <cha...@gm...> wrote:

> One way I could think of is to make two contingent mat.axes.Axes,
> with a smaller one setting as white backgroud, and the other bigger on
> holding the colorbar. Is there some better way?
>
> Chao
>
>
> On Tue, Jul 2, 2013 at 12:12 PM, Chao YUE <cha...@gm...> wrote:
>
>> Dear all,
>>
>> Does anyone have similar experience that to make a colorbar
>> starting from a different color in the colormap? for example, to
>> denote the region with invalid data. I attahced a figure to show
>> what I would like to have, the withe region in the colorbar in the
>> attahced figure shows no data.
>>
>> thanks a lot for any help,
>>
>> best,
>>
>> Chao
>>
>> --
>>
>> ***********************************************************************************
>> Chao YUE
>> Laboratoire des Sciences du Climat et de l'Environnement (LSCE-IPSL)
>> UMR 1572 CEA-CNRS-UVSQ
>> Batiment 712 - Pe 119
>> 91191 GIF Sur YVETTE Cedex
>> Tel: (33) 01 69 08 29 02; Fax:01.69.08.77.16
>>
>> ************************************************************************************
>>
>
>
>
> --
>
> ***********************************************************************************
> Chao YUE
> Laboratoire des Sciences du Climat et de l'Environnement (LSCE-IPSL)
> UMR 1572 CEA-CNRS-UVSQ
> Batiment 712 - Pe 119
> 91191 GIF Sur YVETTE Cedex
> Tel: (33) 01 69 08 29 02; Fax:01.69.08.77.16
>
> ************************************************************************************
>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Windows:
>
> Build for Windows Store.
>
> http://p.sf.net/sfu/windows-dev2dev
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
>
>

One way I could think of is to make two contingent mat.axes.Axes,
with a smaller one setting as white backgroud, and the other bigger on
holding the colorbar. Is there some better way?

Chao

On Tue, Jul 2, 2013 at 12:12 PM, Chao YUE <cha...@gm...> wrote:

> Dear all,
>
> Does anyone have similar experience that to make a colorbar
> starting from a different color in the colormap? for example, to
> denote the region with invalid data. I attahced a figure to show
> what I would like to have, the withe region in the colorbar in the
> attahced figure shows no data.
>
> thanks a lot for any help,
>
> best,
>
> Chao
>
> --
>
> ***********************************************************************************
> Chao YUE
> Laboratoire des Sciences du Climat et de l'Environnement (LSCE-IPSL)
> UMR 1572 CEA-CNRS-UVSQ
> Batiment 712 - Pe 119
> 91191 GIF Sur YVETTE Cedex
> Tel: (33) 01 69 08 29 02; Fax:01.69.08.77.16
>
> ************************************************************************************
>



-- 
***********************************************************************************
Chao YUE
Laboratoire des Sciences du Climat et de l'Environnement (LSCE-IPSL)
UMR 1572 CEA-CNRS-UVSQ
Batiment 712 - Pe 119
91191 GIF Sur YVETTE Cedex
Tel: (33) 01 69 08 29 02; Fax:01.69.08.77.16
************************************************************************************

Dear all,

Does anyone have similar experience that to make a colorbar
starting from a different color in the colormap? for example, to
denote the region with invalid data. I attahced a figure to show
what I would like to have, the withe region in the colorbar in the
attahced figure shows no data.

thanks a lot for any help,

best,

Chao

-- 
***********************************************************************************
Chao YUE
Laboratoire des Sciences du Climat et de l'Environnement (LSCE-IPSL)
UMR 1572 CEA-CNRS-UVSQ
Batiment 712 - Pe 119
91191 GIF Sur YVETTE Cedex
Tel: (33) 01 69 08 29 02; Fax:01.69.08.77.16
************************************************************************************

Dear all matplotlib users,

I found there is not a get_ticks method available for colorbar instance,
how could I quick get the ticks of a colorbar?

thanks,

Chao
-- 
***********************************************************************************
Chao YUE
Laboratoire des Sciences du Climat et de l'Environnement (LSCE-IPSL)
UMR 1572 CEA-CNRS-UVSQ
Batiment 712 - Pe 119
91191 GIF Sur YVETTE Cedex
Tel: (33) 01 69 08 29 02; Fax:01.69.08.77.16
************************************************************************************

On 1 July 2013 13:40, zetah <ot...@hu...> wrote:

> Hi,
>
> I have set of points in a plane and make triplot:
>
>     subplot(121)
>     plot(points[:,0], points[:,1], 'o')
>     title('Set of points')
>     subplot(122)
>     triplot(points[:,0], points[:,1])
>     title('Triangulation')
>
> result: http://i.imgur.com/1LG4fxC.png
>
> Does anyone know how to extract just the lines describing each
> circumscribed circle in this example?
> Perhaps by using Delaunay from scipy.spatial?
>
> Just to inform you, I want to do this through triangulation and above
> example is trivial that can be solved differently, while real problem
> doesn't contain circles...
>

You need to use a matplotlib.tri.Triangulation (your use of triplot does
this for you behind the scenes anyway), something like:

import matplotlib.tri as mtri
triang = mtri.Triangulation(xpoints, ypoints)

Now triang.triangles is an array of integers of shape (?, 3) such that
triang.triangles[i,:] are the three indices of the points that comprise
triangle i.  You will need to use these to determine the information you
want.  The triplot example (
http://matplotlib.org/examples/pylab_examples/triplot_demo.html) does
something similar, identifying which triangles are within a particular
circle; I guess in your case a simple approach would be to test if the
distance from the centre of each triangle edge to your circle of interest
is below some threshold or not.

Incidentally, if you have a Triangulation object then subsequent calls to
functions like triplot can be of the form triplot(triang), which will be
faster than repeated calls to triplot(xpoints, ypoints) as in the latter
case a separate Delaunay triangulation needs to be performed for each
triplot call.

Ian

William Ray Wing wrote
> On Jul 1, 2013, at 1:42 PM, psb1967 <

> psb67@

> > wrote:
> 
> 
> Suresh,  I think the most likely reason no one has answered is that the
> intersection of the set of matplotlib experts and the set of people who
> know what Bollinger bands are is too close to zero.  I'm a beginner at
> matplotlib, but I do know what Bollinger bands are, and I'd suggest your
> best approach is to take a look at the matplotlib demo gallery here:  
> 
> http://matplotlib.org/examples
> 
> in particular, study the code for the fifth example from the top here: 
> http://matplotlib.org/examples/pylab_examples/plotfile_demo.html
> 
> which implements a plot of Open, High. Low, and Closing prices.  I'm
> assuming you know enough math to implement a Bollinger band version of a
> moving average, and can just substitute it for the code that plots the
> extra lines on the example.
> 
> Good luck,
> Bill

Hi Bill,

I am truly overwhelmed to see the kind of efforts taken to guide when one
requires guidance, esp. the fresh programmers. One of the things that I
learned when no one responds with a specific answer but shown the direction
is that I am given an opportunity to learn and work  by myself. I really
appreciate your time and will start working on the example you have cited.

In fact, I did get a complete Bollinger bands script however, I will start
working on the line you have shown; it may open up new avenues. 

Regards.

Suresh



--
View this message in context: http://matplotlib.1069221.n5.nabble.com/To-add-Bollinger-Bands-in-finance-work2-py-tp41310p41359.html
Sent from the matplotlib - users mailing list archive at Nabble.com.

Hi all,

after John's untimely passing we had a memorial service in Chicago,
but only a few on these lists were able to attend. At last week's
scipy conference I read a slightly edited version of the eulogy from
that memorial service, and I figured some of you might be interested
if you missed the conference:

http://blog.fperez.org/2013/07/in-memoriam-john-d-hunter-iii-1968-2012.html

Cheers,

f

--
Fernando Perez (@fperez_org; http://fperez.org)
fperez.net-at-gmail: mailing lists only (I ignore this when swamped!)
fernando.perez-at-berkeley: contact me here for any direct mail