matplotlib-users Mailing List for matplotlib (Page 12)

I have seen this problem when matplotlib wasn't fully rebuilt after 
upgrading Numpy.  I would assume, since you're installing from Gentoo 
packages, that the package manager is smart enough to blitz the 
matplotlib build products before rebuilding, but maybe not.  (Python 
distutils doesn't do proper dependency resolution.)  Have you tried 
removing the "build" directory from the matplotlib tree before rebuilding?

Mike

On 02/08/2011 07:56 AM, Philippe Baucour wrote:
> hello,
> I get a segmentation fault with the pylab mode and I made several
> test to track down a bug but it's beyond my level and I still don't now
> if it's an ipython bug or matplotlib bug ...
>
> let's reproduce the bug !!!!
>       ________________
> ____/   try 1 Qt4Agg \_____
>
> phil@Numokh ~ % ipython -pylab
> In [1]: plt.plot([4])
> segmentation fault  ipython -pylab
>
> By default I have Qt4Agg as backend but it doesn't work with all
> backends
>
>       _______________
> ____/   try 2 TkAgg \_____
>
> phil@Numokh ~ % ipython -pylab
>
> In [1]: plt.rcParams['backend']='TkAgg'
>
> In [2]: plt.get_backend()
> Out[2]: 'TkAgg'
>
> In [3]: plt.plot([4])
> segmentation fault  ipython -pylab
>
>
>       ____________________________
> ____/   try 3 Qt4Agg + backtrace \_____
>
>
> I made a backtrace with gdb
> phil@Numokh ~ % gdb python
> GNU gdb (Gentoo 7.2 p1) 7.2
> Copyright (C) 2010 Free Software Foundation, Inc.
> License GPLv3+: GNU GPL version 3 or later
> <http://gnu.org/licenses/gpl.html>  This is free software: you are free
> to change and redistribute it. There is NO WARRANTY, to the extent
> permitted by law.  Type "show copying" and "show warranty" for details.
> This GDB was configured as "x86_64-pc-linux-gnu".
> For bug reporting instructions, please see:
> <http://bugs.gentoo.org/>...
> Reading symbols from /usr/bin/python...(no debugging symbols
> found)...done. (gdb) r /usr/bin/ipython -pylab
> Starting program: /usr/bin/python /usr/bin/ipython -pylab
> process 4149 is executing new program: /usr/bin/python2.7
> [Thread debugging using libthread_db enabled]
> process 4149 is executing new program: /usr/bin/python2.7
> [Thread debugging using libthread_db enabled]
>
> In [1]: plt.plot([4])
>
> Program received signal SIGSEGV, Segmentation fault.
> 0x00007fffe82d5ce7 in __cxa_allocate_exception ()
>     from /usr/lib/gcc/x86_64-pc-linux-gnu/4.4.4/libstdc++.so.6
> (gdb) bt
> #0  0x00007fffe82d5ce7 in __cxa_allocate_exception ()
>     from /usr/lib/gcc/x86_64-pc-linux-gnu/4.4.4/libstdc++.so.6
> #1  0x00007fffe4d1f8a4 in py_to_agg_transformation_matrix(_object*,
> bool) () from /usr/lib64/python2.7/site-packages/matplotlib/_path.so
> #2  0x00007fffe4d2a42b in _path_module::update_path_extents(Py::Tuple
> const&) () from /usr/lib64/python2.7/site-packages/matplotlib/_path.so
> #3  0x00007fffe4d31108 in
> Py::ExtensionModule<_path_module>::invoke_method_varargs(void*,
> Py::Tuple const&) ()
> from /usr/lib64/python2.7/site-packages/matplotlib/_path.so #4
> 0x00007fffe4d1acbd in method_varargs_call_handler ()
> from /usr/lib64/python2.7/site-packages/matplotlib/_path.so #5
> 0x00007ffff7b09263 in PyEval_EvalFrameEx ()
> from /usr/lib/libpython2.7.so.1.0 #6  0x00007ffff7b0ab50 in
> PyEval_EvalCodeEx () from /usr/lib/libpython2.7.so.1.0 #7
> 0x00007ffff7b09337 in PyEval_EvalFrameEx ()
> from /usr/lib/libpython2.7.so.1.0 #8  0x00007ffff7b0ab50 in
> PyEval_EvalCodeEx () from /usr/lib/libpython2.7.so.1.0
> #9  0x00007ffff7b09337 in PyEval_EvalFrameEx ()
>     from /usr/lib/libpython2.7.so.1.0
> #10 0x00007ffff7b0ab50 in PyEval_EvalCodeEx ()
>     from /usr/lib/libpython2.7.so.1.0
> ---Type<return>  to continue, or q<return>  to quit---
> #11 0x00007ffff7b09337 in PyEval_EvalFrameEx ()
>     from /usr/lib/libpython2.7.so.1.0
> #12 0x00007ffff7b0ab50 in PyEval_EvalCodeEx ()
>     from /usr/lib/libpython2.7.so.1.0
> #13 0x00007ffff7a95f26 in ?? () from /usr/lib/libpython2.7.so.1.0
> #14 0x00007ffff7a6d542 in PyObject_Call ()
> from /usr/lib/libpython2.7.so.1.0 #15 0x00007ffff7b07a27 in
> PyEval_EvalFrameEx () from /usr/lib/libpython2.7.so.1.0
> #16 0x00007ffff7b0ab50 in PyEval_EvalCodeEx ()
>     from /usr/lib/libpython2.7.so.1.0
> #17 0x00007ffff7b09337 in PyEval_EvalFrameEx ()
>     from /usr/lib/libpython2.7.so.1.0
> #18 0x00007ffff7b0ab50 in PyEval_EvalCodeEx ()
>     from /usr/lib/libpython2.7.so.1.0
> #19 0x00007ffff7b0ac62 in PyEval_EvalCode ()
> from /usr/lib/libpython2.7.so.1.0 #20 0x00007ffff7b0a155 in
> PyEval_EvalFrameEx () from /usr/lib/libpython2.7.so.1.0
> #21 0x00007ffff7b0ab50 in PyEval_EvalCodeEx ()
>     from /usr/lib/libpython2.7.so.1.0
> #22 0x00007ffff7b09337 in PyEval_EvalFrameEx ()
>     from /usr/lib/libpython2.7.so.1.0
> #23 0x00007ffff7b0ab50 in PyEval_EvalCodeEx ()
>     from /usr/lib/libpython2.7.so.1.0
> ---Type<return>  to continue, or q<return>  to quit---
> #24 0x00007ffff7b09337 in PyEval_EvalFrameEx ()
>     from /usr/lib/libpython2.7.so.1.0
> #25 0x00007ffff7b09464 in PyEval_EvalFrameEx ()
>     from /usr/lib/libpython2.7.so.1.0
> #26 0x00007ffff7b0ab50 in PyEval_EvalCodeEx ()
>     from /usr/lib/libpython2.7.so.1.0
> #27 0x00007ffff7b09337 in PyEval_EvalFrameEx ()
>     from /usr/lib/libpython2.7.so.1.0
> #28 0x00007ffff7b0ab50 in PyEval_EvalCodeEx ()
>     from /usr/lib/libpython2.7.so.1.0
> #29 0x00007ffff7b09337 in PyEval_EvalFrameEx ()
>     from /usr/lib/libpython2.7.so.1.0
> #30 0x00007ffff7b0ab50 in PyEval_EvalCodeEx ()
>     from /usr/lib/libpython2.7.so.1.0
> #31 0x00007ffff7b09337 in PyEval_EvalFrameEx ()
>     from /usr/lib/libpython2.7.so.1.0
> #32 0x00007ffff7b0ab50 in PyEval_EvalCodeEx ()
>     from /usr/lib/libpython2.7.so.1.0
> #33 0x00007ffff7b0ac62 in PyEval_EvalCode ()
> from /usr/lib/libpython2.7.so.1.0 #34 0x00007ffff7b24e8c in ?? ()
> from /usr/lib/libpython2.7.so.1.0 #35 0x00007ffff7b24f62 in
> PyRun_FileExFlags () from /usr/lib/libpython2.7.so.1.0
> #36 0x00007ffff7b2649c in PyRun_SimpleFileExFlags ()
> ---Type<return>  to continue, or q<return>  to quit---
>     from /usr/lib/libpython2.7.so.1.0
> #37 0x00007ffff7b37619 in Py_Main () from /usr/lib/libpython2.7.so.1.0
> #38 0x00007ffff74cebbd in __libc_start_main () from /lib/libc.so.6
> #39 0x00000000004008c9 in _start ()
>
>       ___________________________
> ____/   try 4 Qt4Agg + q4thread \_____
>
> With a ipython -pylab -q4thread
> everything seems to work except the autoindent feature
>
>
>       ___________________
> ____/   try 5 python -i \_____
>
> with python -i no pb at all
>
> phil@Numokh ~ % python -i
> Python 2.7.1 (r271:86832, Feb  8 2011, 00:36:24)
> [GCC 4.4.4] on linux2
> Type "help", "copyright", "credits" or "license" for more information.
>    
>>>> from pylab import *
>>>> plot([4])
>>>>          
> [<matplotlib.lines.Line2D object at 0x17c0ed0>]
>    
>>>> show()
>>>>
>>>>          
>       _____________________
> ____/   try 6 ipython git \_____
>
> I tried with ipython from git
> phil@Numokh ipython % python ipython.py --pylab
> Python 2.7.1 (r271:86832, Feb  8 2011, 00:36:24)
> Type "copyright", "credits" or "license" for more information.
>
> IPython 0.11.dev -- An enhanced Interactive Python.
> ?         ->  Introduction and overview of IPython's features.
> %quickref ->  Quick reference.
> help      ->  Python's own help system.
> object?   ->  Details about 'object', use 'object??' for extra details.
>
> Welcome to pylab, a matplotlib-based Python environment [backend:
> Qt4Agg]. For more information, type 'help(pylab)'.
>
> In [1]: plot([4])
> Out[1]: [<matplotlib.lines.Line2D object at 0x1f8e5d0>]
>
> but in this case I have issues with unicode pb ...
> In [2]: xlabel('température')
> UnicodeEncodeError: 'ascii' codec can't encode character u'\xe9' in
> position 12: ordinal not in range(128)
>
>
>       _________
> ____/   specs \_____
>
> here is my python package :
> - dev-lang/python-2.7.1
> - dev-python/numpy-1.5.1
> - sci-libs/scipy-0.8.1
> - dev-python/matplotlib-1.0.1 (with the USEFLAGS cairo examples excel
>    gtk latex qt4 tk traits wxwidgets -doc -fltk)
> - dev-python/ipython-0.10.1 (with the USEFLAGS doc examples readline
>    smp wxwidgets -emacs -gnuplot -test)
>
>
> At this point I'm lost !!! any idea
>
> Philippe Baucour
>
>
> ------------------------------------------------------------------------------
> The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
> Pinpoint memory and threading errors before they happen.
> Find and fix more than 250 security defects in the development cycle.
> Locate bottlenecks in serial and parallel code that limit performance.
> http://p.sf.net/sfu/intel-dev2devfeb
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
>    


-- 
Michael Droettboom
Science Software Branch
Space Telescope Science Institute
Baltimore, Maryland, USA

Bram,





Although I don't quite see the point, I would simply suggest that you 
re-call ax.legend(ncol=2) , that would delete the previous and redraw a 
new one





from matplotlib doc: When the legend command is called, a new legend instance is created and old ones are removed from the axes. 








Thomas




**********************
Thomas Lecocq

Geologist
Ph.D.Student (Seismology)
Royal Observatory of Belgium
**********************



Date: Tue, 8 Feb 2011 14:50:00 +0100
From: sa...@kn...
To: thl...@ms...
CC: mat...@li...
Subject: Re: [Matplotlib-users] set ncol for legend



  


    
  
  
    I realize that I have not been clear enough. 

    

    I have already created a legend instance in my_own_plot_function,
    for example, a legend with one column by default:  

    

    fig = plt.figure()

      ax = fig.add_subplot(111)

      my_own_plot_function(ax, data)    # gives, for example, one column
      legend by default

    

    So ax is an axes instance containing the legend. 

    

    Incidentally, after inspecting the automatically created plots, I
    want a particular figure to have a two column legend. I would like
    to do this without adding an extra kwarg for the number of columns
    to my_own_plot_function. It should be possible to do something like
    this:

    

    legend = ax.get_legend()

      legend.set_ncol(2)          # something like this 

    
    

    Once again, thanks for any help!

    

    Bram

    

    

    On 02/08/2011 12:35 PM, Thomas Lecocq wrote:
    
      
      Bram,

       

       

      fig = plt.figure()

      ax = fig.add_subplot(111)

      plot1 = plot.plot(X,Y,label='1')

      plot2 = plot.plot(X,Y,label='2')

      ...

      plotN = plot.plot(X,Y,label='N')

       

      legend = plt.legend(ncol=2)

       

      should work...

       

      so, for your "own_plot_function", you have to return the legend
      and set it accordingly...

       

      Thomas

       

      

      

      **********************

      Thomas Lecocq 

      Geologist

      Ph.D.Student (Seismology)

      Royal Observatory of Belgium

      **********************

      

      

       

      
      Date: Tue, 8 Feb 2011 11:25:58 +0100

      From: sa...@kn...

      To: mat...@li...

      Subject: [Matplotlib-users] set ncol for legend

      

      
      Hi, 

      

      I want to update the number of columns in my legend. How should I
      do that?

      

      I'm looking for something like:

      

      fig = plt.figure()

      ax = fig.add_subplot(111)

      my_own_plot_function(ax, data)    # gives, for example, one column
      legend by default

      legend = ax.get_legend()

      legend.set_ncol(2)          # something like this 

      

      

      However, ncol is not in the legend.properties() list for
      properties to be set through legend.set.

      

      

      Thanks for any help, 

      Bram 

      

      

      ------------------------------------------------------------------------------
      The ultimate all-in-one performance toolkit: Intel(R) Parallel
      Studio XE: Pinpoint memory and threading errors before they
      happen. Find and fix more than 250 security defects in the
      development cycle. Locate bottlenecks in serial and parallel code
      that limit performance. http://p.sf.net/sfu/intel-dev2devfeb

      _______________________________________________ Matplotlib-users
      mailing list Mat...@li...
      https://lists.sourceforge.net/lists/listinfo/matplotlib-users 
    
 		 	   		  

 I realize that I have not been clear enough.

I have already created a legend instance in my_own_plot_function, for
example, a legend with one column by default: 

fig = plt.figure()
ax = fig.add_subplot(111)
my_own_plot_function(ax, data)    # gives, for example, one column
legend by default

So ax is an axes instance containing the legend.

Incidentally, after inspecting the automatically created plots, I want a
particular figure to have a two column legend. I would like to do this
without adding an extra kwarg for the number of columns to
my_own_plot_function. It should be possible to do something like this:

legend = ax.get_legend()
/legend.set_ncol(2)/          # something like this

Once again, thanks for any help!

Bram


On 02/08/2011 12:35 PM, Thomas Lecocq wrote:
> Bram,
>  
>  
> fig = plt.figure()
> ax = fig.add_subplot(111)
> plot1 = plot.plot(X,Y,label='1')
> plot2 = plot.plot(X,Y,label='2')
> ...
> plotN = plot.plot(X,Y,label='N')
>  
> legend = plt.legend(ncol=2)
>  
> should work...
>  
> so, for your "own_plot_function", you have to return the legend and
> set it accordingly...
>  
> Thomas
>  
>
>
> **********************
> Thomas Lecocq
> Geologist
> Ph.D.Student (Seismology)
> Royal Observatory of Belgium
> **********************
>
>
>  
> ------------------------------------------------------------------------
> Date: Tue, 8 Feb 2011 11:25:58 +0100
> From: sa...@kn...
> To: mat...@li...
> Subject: [Matplotlib-users] set ncol for legend
>
> Hi,
>
> I want to update the number of columns in my legend. How should I do that?
>
> I'm looking for something like:
>
> fig = plt.figure()
> ax = fig.add_subplot(111)
> my_own_plot_function(ax, data)    # gives, for example, one column
> legend by default
> legend = ax.get_legend()
> /legend.set_ncol(2)/          # something like this
>
>
> However, /ncol/ is not in the legend.properties() list for properties
> to be set through legend.set.
>
>
> Thanks for any help,
> Bram
>
>
> ------------------------------------------------------------------------------
> The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio
> XE: Pinpoint memory and threading errors before they happen. Find and
> fix more than 250 security defects in the development cycle. Locate
> bottlenecks in serial and parallel code that limit performance.
> http://p.sf.net/sfu/intel-dev2devfeb
> _______________________________________________ Matplotlib-users
> mailing list Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users 

hello,
I get a segmentation fault with the pylab mode and I made several
test to track down a bug but it's beyond my level and I still don't now
if it's an ipython bug or matplotlib bug ...

let's reproduce the bug !!!!
     ________________
____/   try 1 Qt4Agg \_____

phil@Numokh ~ % ipython -pylab
In [1]: plt.plot([4])
segmentation fault  ipython -pylab 

By default I have Qt4Agg as backend but it doesn't work with all
backends 

     _______________
____/   try 2 TkAgg \_____

phil@Numokh ~ % ipython -pylab

In [1]: plt.rcParams['backend']='TkAgg'

In [2]: plt.get_backend()
Out[2]: 'TkAgg'

In [3]: plt.plot([4])
segmentation fault  ipython -pylab


     ____________________________
____/   try 3 Qt4Agg + backtrace \_____


I made a backtrace with gdb
phil@Numokh ~ % gdb python 
GNU gdb (Gentoo 7.2 p1) 7.2
Copyright (C) 2010 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
<http://gnu.org/licenses/gpl.html> This is free software: you are free
to change and redistribute it. There is NO WARRANTY, to the extent
permitted by law.  Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-pc-linux-gnu".
For bug reporting instructions, please see:
<http://bugs.gentoo.org/>...
Reading symbols from /usr/bin/python...(no debugging symbols
found)...done. (gdb) r /usr/bin/ipython -pylab
Starting program: /usr/bin/python /usr/bin/ipython -pylab
process 4149 is executing new program: /usr/bin/python2.7
[Thread debugging using libthread_db enabled]
process 4149 is executing new program: /usr/bin/python2.7
[Thread debugging using libthread_db enabled]

In [1]: plt.plot([4])

Program received signal SIGSEGV, Segmentation fault.
0x00007fffe82d5ce7 in __cxa_allocate_exception ()
   from /usr/lib/gcc/x86_64-pc-linux-gnu/4.4.4/libstdc++.so.6
(gdb) bt
#0  0x00007fffe82d5ce7 in __cxa_allocate_exception ()
   from /usr/lib/gcc/x86_64-pc-linux-gnu/4.4.4/libstdc++.so.6
#1  0x00007fffe4d1f8a4 in py_to_agg_transformation_matrix(_object*,
bool) () from /usr/lib64/python2.7/site-packages/matplotlib/_path.so
#2  0x00007fffe4d2a42b in _path_module::update_path_extents(Py::Tuple
const&) () from /usr/lib64/python2.7/site-packages/matplotlib/_path.so
#3  0x00007fffe4d31108 in
Py::ExtensionModule<_path_module>::invoke_method_varargs(void*,
Py::Tuple const&) ()
from /usr/lib64/python2.7/site-packages/matplotlib/_path.so #4
0x00007fffe4d1acbd in method_varargs_call_handler ()
from /usr/lib64/python2.7/site-packages/matplotlib/_path.so #5
0x00007ffff7b09263 in PyEval_EvalFrameEx ()
from /usr/lib/libpython2.7.so.1.0 #6  0x00007ffff7b0ab50 in
PyEval_EvalCodeEx () from /usr/lib/libpython2.7.so.1.0 #7
0x00007ffff7b09337 in PyEval_EvalFrameEx ()
from /usr/lib/libpython2.7.so.1.0 #8  0x00007ffff7b0ab50 in
PyEval_EvalCodeEx () from /usr/lib/libpython2.7.so.1.0
#9  0x00007ffff7b09337 in PyEval_EvalFrameEx ()
   from /usr/lib/libpython2.7.so.1.0
#10 0x00007ffff7b0ab50 in PyEval_EvalCodeEx ()
   from /usr/lib/libpython2.7.so.1.0
---Type <return> to continue, or q <return> to quit---
#11 0x00007ffff7b09337 in PyEval_EvalFrameEx ()
   from /usr/lib/libpython2.7.so.1.0
#12 0x00007ffff7b0ab50 in PyEval_EvalCodeEx ()
   from /usr/lib/libpython2.7.so.1.0
#13 0x00007ffff7a95f26 in ?? () from /usr/lib/libpython2.7.so.1.0
#14 0x00007ffff7a6d542 in PyObject_Call ()
from /usr/lib/libpython2.7.so.1.0 #15 0x00007ffff7b07a27 in
PyEval_EvalFrameEx () from /usr/lib/libpython2.7.so.1.0
#16 0x00007ffff7b0ab50 in PyEval_EvalCodeEx ()
   from /usr/lib/libpython2.7.so.1.0
#17 0x00007ffff7b09337 in PyEval_EvalFrameEx ()
   from /usr/lib/libpython2.7.so.1.0
#18 0x00007ffff7b0ab50 in PyEval_EvalCodeEx ()
   from /usr/lib/libpython2.7.so.1.0
#19 0x00007ffff7b0ac62 in PyEval_EvalCode ()
from /usr/lib/libpython2.7.so.1.0 #20 0x00007ffff7b0a155 in
PyEval_EvalFrameEx () from /usr/lib/libpython2.7.so.1.0
#21 0x00007ffff7b0ab50 in PyEval_EvalCodeEx ()
   from /usr/lib/libpython2.7.so.1.0
#22 0x00007ffff7b09337 in PyEval_EvalFrameEx ()
   from /usr/lib/libpython2.7.so.1.0
#23 0x00007ffff7b0ab50 in PyEval_EvalCodeEx ()
   from /usr/lib/libpython2.7.so.1.0
---Type <return> to continue, or q <return> to quit---
#24 0x00007ffff7b09337 in PyEval_EvalFrameEx ()
   from /usr/lib/libpython2.7.so.1.0
#25 0x00007ffff7b09464 in PyEval_EvalFrameEx ()
   from /usr/lib/libpython2.7.so.1.0
#26 0x00007ffff7b0ab50 in PyEval_EvalCodeEx ()
   from /usr/lib/libpython2.7.so.1.0
#27 0x00007ffff7b09337 in PyEval_EvalFrameEx ()
   from /usr/lib/libpython2.7.so.1.0
#28 0x00007ffff7b0ab50 in PyEval_EvalCodeEx ()
   from /usr/lib/libpython2.7.so.1.0
#29 0x00007ffff7b09337 in PyEval_EvalFrameEx ()
   from /usr/lib/libpython2.7.so.1.0
#30 0x00007ffff7b0ab50 in PyEval_EvalCodeEx ()
   from /usr/lib/libpython2.7.so.1.0
#31 0x00007ffff7b09337 in PyEval_EvalFrameEx ()
   from /usr/lib/libpython2.7.so.1.0
#32 0x00007ffff7b0ab50 in PyEval_EvalCodeEx ()
   from /usr/lib/libpython2.7.so.1.0
#33 0x00007ffff7b0ac62 in PyEval_EvalCode ()
from /usr/lib/libpython2.7.so.1.0 #34 0x00007ffff7b24e8c in ?? ()
from /usr/lib/libpython2.7.so.1.0 #35 0x00007ffff7b24f62 in
PyRun_FileExFlags () from /usr/lib/libpython2.7.so.1.0
#36 0x00007ffff7b2649c in PyRun_SimpleFileExFlags ()
---Type <return> to continue, or q <return> to quit---
   from /usr/lib/libpython2.7.so.1.0
#37 0x00007ffff7b37619 in Py_Main () from /usr/lib/libpython2.7.so.1.0
#38 0x00007ffff74cebbd in __libc_start_main () from /lib/libc.so.6
#39 0x00000000004008c9 in _start ()

     ___________________________
____/   try 4 Qt4Agg + q4thread \_____

With a ipython -pylab -q4thread 
everything seems to work except the autoindent feature


     ___________________
____/   try 5 python -i \_____

with python -i no pb at all

phil@Numokh ~ % python -i
Python 2.7.1 (r271:86832, Feb  8 2011, 00:36:24) 
[GCC 4.4.4] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> from pylab import *
>>> plot([4])  
[<matplotlib.lines.Line2D object at 0x17c0ed0>]
>>> show()
>>>   

     _____________________
____/   try 6 ipython git \_____

I tried with ipython from git 
phil@Numokh ipython % python ipython.py --pylab
Python 2.7.1 (r271:86832, Feb  8 2011, 00:36:24) 
Type "copyright", "credits" or "license" for more information.

IPython 0.11.dev -- An enhanced Interactive Python.
?         -> Introduction and overview of IPython's features.
%quickref -> Quick reference.
help      -> Python's own help system.
object?   -> Details about 'object', use 'object??' for extra details.

Welcome to pylab, a matplotlib-based Python environment [backend:
Qt4Agg]. For more information, type 'help(pylab)'.

In [1]: plot([4])
Out[1]: [<matplotlib.lines.Line2D object at 0x1f8e5d0>]

but in this case I have issues with unicode pb ...
In [2]: xlabel('température')
UnicodeEncodeError: 'ascii' codec can't encode character u'\xe9' in
position 12: ordinal not in range(128) 


     _________
____/   specs \_____

here is my python package :
- dev-lang/python-2.7.1
- dev-python/numpy-1.5.1
- sci-libs/scipy-0.8.1
- dev-python/matplotlib-1.0.1 (with the USEFLAGS cairo examples excel
  gtk latex qt4 tk traits wxwidgets -doc -fltk)
- dev-python/ipython-0.10.1 (with the USEFLAGS doc examples readline
  smp wxwidgets -emacs -gnuplot -test)


At this point I'm lost !!! any idea 

Philippe Baucour

Hello,

Matplotlib is so cool. I wish I had spent time learning it earlier.
Better late than never. Thanks so much to all who have worked on
developing it.

I had a question on histograms. Instead of the bars in case of
histograms, is there a way to get circle markers, where each marker
represents one observation in that bin. For example, if there are 5
observations in a bin, then instead of a bar of height 5, I want 5
circles stacked on top of each other. The same for other bins. Is
there a built-in command or property to do this?

Thanks for your help.



On Tue, Feb 8, 2011 at 5:25 AM, sanders <sa...@kn...> wrote:
> Hi,
>
> I want to update the number of columns in my legend. How should I do that?
>
> I'm looking for something like:
>
> fig = plt.figure()
> ax = fig.add_subplot(111)
> my_own_plot_function(ax, data)    # gives, for example, one column legend by
> default
> legend = ax.get_legend()
> legend.set_ncol(2)          # something like this
>
>
> However, ncol is not in the legend.properties() list for properties to be
> set through legend.set.
>
>
> Thanks for any help,
> Bram
>
>
> ------------------------------------------------------------------------------
> The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
> Pinpoint memory and threading errors before they happen.
> Find and fix more than 250 security defects in the development cycle.
> Locate bottlenecks in serial and parallel code that limit performance.
> http://p.sf.net/sfu/intel-dev2devfeb
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
>
>

On 08.02.2011 13:01, Thomas Lecocq wrote:
>
> this could work ;
>
> img.set_extent([0,200,0,200])

Yes, this works. Thank you.

So now I use
ax.relim()
ax.autoscale_view()
img.set_extent([0, 200, 0, 200])

 From my point of view it is strange, that one has to call 
img.set_extent explicitely which requires knowing the exact limits, 
although I want to :autoscale_.

And I find the documentation of the 'extent' keyword for Axes.imshow() 
<http://matplotlib.sourceforge.net/api/axes_api.html#matplotlib.axes.Axes.imshow> 
not clear in this respect:

extent: [ None | scalars (left, right, bottom, top) ]
     Data limits for the axes. The default assigns zero-based row, 
column indices to the x, y centers of the pixels.

...whatever that exactly means :-)

Christoph

Christoph,

this could work ;

img.set_extent([0,200,0,200])

HTH


Thom

**********************
Thomas Lecocq

Geologist
Ph.D.Student (Seismology)
Royal Observatory of Belgium
**********************



> Date: Tue, 8 Feb 2011 12:56:21 +0100
> From: us...@be...
> To: thl...@ms...
> CC: mat...@li...
> Subject: Re: [Matplotlib-users] Autoscale AxesImage after using set_data()
> 
> On 08.02.2011 10:23, Thomas Lecocq wrote:
> > I would suggest calling requet_redraw() ...
> 
> I could not find such a method, nor any similar one: request_redraw() or 
> *_redraw(). I grepped through the version 1.0.1 source code.
> 
> Christoph
 		 	   		  

On 08.02.2011 10:23, Thomas Lecocq wrote:
> I would suggest calling requet_redraw() ...

I could not find such a method, nor any similar one: request_redraw() or 
*_redraw(). I grepped through the version 1.0.1 source code.

Christoph

Bram,
 
 
fig = plt.figure()
ax = fig.add_subplot(111)
plot1 = plot.plot(X,Y,label='1')
plot2 = plot.plot(X,Y,label='2')
...
plotN = plot.plot(X,Y,label='N')
 
legend = plt.legend(ncol=2)
 
should work...
 
so, for your "own_plot_function", you have to return the legend and set it accordingly...
 
Thomas
 


**********************
Thomas Lecocq 
Geologist
Ph.D.Student (Seismology)
Royal Observatory of Belgium
**********************


 


Date: Tue, 8 Feb 2011 11:25:58 +0100
From: sa...@kn...
To: mat...@li...
Subject: [Matplotlib-users] set ncol for legend


Hi, 

I want to update the number of columns in my legend. How should I do that?

I'm looking for something like:

fig = plt.figure()
ax = fig.add_subplot(111)
my_own_plot_function(ax, data)    # gives, for example, one column legend by default
legend = ax.get_legend()
legend.set_ncol(2)          # something like this 


However, ncol is not in the legend.properties() list for properties to be set through legend.set.


Thanks for any help, 
Bram 


------------------------------------------------------------------------------ The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb
_______________________________________________ Matplotlib-users mailing list Mat...@li... https://lists.sourceforge.net/lists/listinfo/matplotlib-users 		 	   		  

 Hi,

I want to update the number of columns in my legend. How should I do that?

I'm looking for something like:

fig = plt.figure()
ax = fig.add_subplot(111)
my_own_plot_function(ax, data)    # gives, for example, one column
legend by default
legend = ax.get_legend()
/legend.set_ncol(2)/          # something like this


However, /ncol/ is not in the legend.properties() list for properties to
be set through legend.set.


Thanks for any help,
Bram

Hi,

I'm trying to autoscale an AxesImage after having set new data with 
set_data(). I thought, the way to do it is to use Axes.relim() followed 
by Axes.autoscale_view(). Unfortunately, this does not work properly 
both with version 0.99.3 and 1.0.1.
Consider the following example (adapted from the example 
<http://matplotlib.sourceforge.net/examples/animation/simple_anim_gtk.html>):

import time
import numpy as np
import matplotlib
matplotlib.use('GTKAgg')

import matplotlib.pyplot as plt

fig = plt.figure()
ax = fig.add_subplot(111)
x, y = np.mgrid[0:100, 0:100]
img = ax.imshow(np.sin(0.05 * y))

def animate():
      time.sleep(3)
      x, y = np.mgrid[0:200, 0:200]
      img.set_data(np.sin(0.05 * x))
      # set_*lim works with v 0.99.3
      ax.set_xlim(0, 200)
      ax.set_ylim(0, 200)
      # ax.relim()
      # ax.autoscale_view()
      fig.canvas.draw()
      return False

import gobject
gobject.idle_add(animate)
plt.show()


I want the plot to show the 200x200 image after the update, with the 
correct ticks showing. But what I get is the following:

Using set_xlim() and set_ylim() works, but only for version 0.99.3.
With version 1.0.1 the axes show a range of 200x200, and the new image 
data is used, but the new 200x200 image is shrunk to a 100x100 region.

Using relim() and autoscale_view(), which is what I thought the correct 
way to do it, also does not work:
With version 0.99.3 it does nothing, it does no autoscaling at all. With 
version 1.0.1 the new image is shown completely, but the axes ticks 
still show 0..100 instead of 0..200

Thanks for you help,
Christoph

2011/2/8 Benjamin Root <ben...@ou...>

>
>
> Hmm, interesting observation.  There is very little in mpl that limits your
> ability to produce elements for plotting (which is probably why you were
> getting shrugs from the mailing list...).  However, ipython has various
> "tricks" for caching mpl elements, and can sometimes be a bit excessive in
> memory usage.  This could lead to some issues.
>
> Now that you have identified ipython as the culprit, I would suggest taking
> this to the ipython list and seeing if they can better identify the problem
> for you.
>
> Ben Root
>
>
Thanks, I was thinking of doing that myself.

jorges

On Mon, Feb 7, 2011 at 7:09 PM, Jorge Scandaliaris
<jor...@ya...>wrote:

> Jorge Scandaliaris <jorgesmbox-ml@...> writes:
>
> < snip >
> > So, I modified the lasso_demo, increasing progressively the number
> polygons
> > drawn. When I reached 100000 polygons, I was able to reproduce the
> problem.
> > It's
> > true that this a rather large number, but in my code it happens well
> below this
> > number, maybe because I assign a different color and size to each
> polygon. So
> > my
> > previous observation that setting different sizes triggered the problem
> might
> > not be the real picture. It seems as if I was hitting some sort of limit.
> >
> > Anyone would have a clue about what could be happening, or how can I try
> to
> > debug this?
> >
>
> Well, I am bit desperate. The event problem definitely is related to the
> number
> of polygons, circles, ellipses I draw, as well as to using different colors
> and
> sizes. I don't even know how to start debugging this.
>
> One step forward, though, is that I checked running the script directly
> from
> python, instead of within ipython, and it is running as it should. This is
> with
> more than 300 thousand ellipses, whereas within ipython it stops working
> with as
> little as 2 thousand ellipses.
>
> I am running both matplotlib and ipython development trees.
>
> Any expert on how events work out there? And mpl-inpython interaction?
>
> Thanks for any hints/suggestions.
>
> jorges
>
>
>
Hmm, interesting observation.  There is very little in mpl that limits your
ability to produce elements for plotting (which is probably why you were
getting shrugs from the mailing list...).  However, ipython has various
"tricks" for caching mpl elements, and can sometimes be a bit excessive in
memory usage.  This could lead to some issues.

Now that you have identified ipython as the culprit, I would suggest taking
this to the ipython list and seeing if they can better identify the problem
for you.

Ben Root

Jorge Scandaliaris <jorgesmbox-ml@...> writes:

< snip >
> So, I modified the lasso_demo, increasing progressively the number polygons
> drawn. When I reached 100000 polygons, I was able to reproduce the problem. 
> It's
> true that this a rather large number, but in my code it happens well below this
> number, maybe because I assign a different color and size to each polygon. So 
> my
> previous observation that setting different sizes triggered the problem might
> not be the real picture. It seems as if I was hitting some sort of limit.
> 
> Anyone would have a clue about what could be happening, or how can I try to
> debug this?
> 

Well, I am bit desperate. The event problem definitely is related to the number
of polygons, circles, ellipses I draw, as well as to using different colors and
sizes. I don't even know how to start debugging this. 

One step forward, though, is that I checked running the script directly from
python, instead of within ipython, and it is running as it should. This is with
more than 300 thousand ellipses, whereas within ipython it stops working with as
little as 2 thousand ellipses.

I am running both matplotlib and ipython development trees. 

Any expert on how events work out there? And mpl-inpython interaction?

Thanks for any hints/suggestions.

jorges

> 
>   Can you get us a gdb backtrace?
> 
> Type "gdb python" at the prompt, then at the gdb prompt, type "r 
> /usr/bin/ipython -pylab".  After it segfaults, type "bt" to get a 
> backtrace, and send the output to this list.
> 
> Mike
> 
> On 10/01/2010 07:04 AM, Eric Emsellem wrote:
> > Hi
> >
> > I just upgraded to opensuse 11.3.
> >
> > And I get now:
> >
> > ipython -pylab:
> >
> > matplotlib version 1.0.0
> > verbose.level helpful
> > platform is  linux2
> > *Segmentation fault*
> >
> >
> > Any clue?
> >
> > I am using IPython 0.10, Python 2.6.5
> >
> > Eric
> >
> >
> > 


Hello,
here is one:

Program received signal SIGSEGV, Segmentation fault.
0x0000000000000000 in ?? ()
(gdb) bt
#0  0x0000000000000000 in ?? ()
#1  0x00007ffff0911651 in init_path () from
/usr/lib64/python2.6/site-packages/matplotlib/_path.so
#2  0x00007ffff7b352c6 in _PyImport_LoadDynamicModule () from
/usr/lib64/libpython2.6.so.1.0
#3  0x00007ffff7b344e1 in ?? () from /usr/lib64/libpython2.6.so.1.0
#4  0x00007ffff7b3475a in ?? () from /usr/lib64/libpython2.6.so.1.0
#5  0x00007ffff7b34bf1 in ?? () from /usr/lib64/libpython2.6.so.1.0
#6  0x00007ffff7b351d4 in PyImport_ImportModuleLevel () from
/usr/lib64/libpython2.6.so.1.0
#7  0x00007ffff7b1f81b in ?? () from /usr/lib64/libpython2.6.so.1.0
#8  0x00007ffff7ae7cb2 in PyObject_Call () from /usr/lib64/libpython2.6.so.1.0
#9  0x00007ffff7b1fd26 in PyEval_CallObjectWithKeywords () from
/usr/lib64/libpython2.6.so.1.0
#10 0x00007ffff7b21b1e in PyEval_EvalFrameEx () from /usr/lib64
/libpython2.6.so.1.0
#11 0x00007ffff7b26431 in PyEval_EvalCodeEx () from /usr/lib64
/libpython2.6.so.1.0
#12 0x00007ffff7b1fa22 in PyEval_EvalCode () from /usr/lib64/libpython2.6.so.1.0
#13 0x00007ffff7b33145 in PyImport_ExecCodeModuleEx () from
/usr/lib64/libpython2.6.so.1.0
#14 0x00007ffff7b33384 in ?? () from /usr/lib64/libpython2.6.so.1.0
#15 0x00007ffff7b344e1 in ?? () from /usr/lib64/libpython2.6.so.1.0
#16 0x00007ffff7b3475a in ?? () from /usr/lib64/libpython2.6.so.1.0
#17 0x00007ffff7b34b35 in ?? () from /usr/lib64/libpython2.6.so.1.0
#18 0x00007ffff7b351d4 in PyImport_ImportModuleLevel () from
/usr/lib64/libpython2.6.so.1.0
#19 0x00007ffff7b1f81b in ?? () from /usr/lib64/libpython2.6.so.1.0
#20 0x00007ffff7ae7cb2 in PyObject_Call () from /usr/lib64/libpython2.6.so.1.0
#21 0x00007ffff7b1fd26 in PyEval_CallObjectWithKeywords () from
/usr/lib64/libpython2.6.so.1.0
#22 0x00007ffff7b21b1e in PyEval_EvalFrameEx () from /usr/lib64
/libpython2.6.so.1.0
#23 0x00007ffff7b26431 in PyEval_EvalCodeEx () from /usr/lib64
/libpython2.6.so.1.0
#24 0x00007ffff7b1fa22 in PyEval_EvalCode () from /usr/lib64/libpython2.6.so.1.0
#25 0x00007ffff7b33145 in PyImport_ExecCodeModuleEx () from
/usr/lib64/libpython2.6.so.1.0
#26 0x00007ffff7b33384 in ?? () from /usr/lib64/libpython2.6.so.1.0
#27 0x00007ffff7b344e1 in ?? () from /usr/lib64/libpython2.6.so.1.0
#28 0x00007ffff7b33c4b in ?? () from /usr/lib64/libpython2.6.so.1.0
#29 0x00007ffff7b34c5a in ?? () from /usr/lib64/libpython2.6.so.1.0
#30 0x00007ffff7b351d4 in PyImport_ImportModuleLevel () from
/usr/lib64/libpython2.6.so.1.0
#31 0x00007ffff7b1f81b in ?? () from /usr/lib64/libpython2.6.so.1.0
#32 0x00007ffff7ae7cb2 in PyObject_Call () from /usr/lib64/libpython2.6.so.1.0
#33 0x00007ffff7b1fd26 in PyEval_CallObjectWithKeywords () from
/usr/lib64/libpython2.6.so.1.0
#34 0x00007ffff7b21b1e in PyEval_EvalFrameEx () from /usr/lib64
/libpython2.6.so.1.0
#35 0x00007ffff7b26431 in PyEval_EvalCodeEx () from /usr/lib64
/libpython2.6.so.1.0
#36 0x00007ffff7b1fa22 in PyEval_EvalCode () from /usr/lib64/libpython2.6.so.1.0
#37 0x00007ffff7b33145 in PyImport_ExecCodeModuleEx () from
/usr/lib64/libpython2.6.so.1.0
#38 0x00007ffff7b33384 in ?? () from /usr/lib64/libpython2.6.so.1.0
#39 0x00007ffff7b344e1 in ?? () from /usr/lib64/libpython2.6.so.1.0
#40 0x00007ffff7b33c4b in ?? () from /usr/lib64/libpython2.6.so.1.0
#41 0x00007ffff7b34c5a in ?? () from /usr/lib64/libpython2.6.so.1.0
#42 0x00007ffff7b351d4 in PyImport_ImportModuleLevel () from
/usr/lib64/libpython2.6.so.1.0
#43 0x00007ffff7b1f81b in ?? () from /usr/lib64/libpython2.6.so.1.0
#44 0x00007ffff7ae7cb2 in PyObject_Call () from /usr/lib64/libpython2.6.so.1.0
#45 0x00007ffff7b1fd26 in PyEval_CallObjectWithKeywords () from
/usr/lib64/libpython2.6.so.1.0
#46 0x00007ffff7b21b1e in PyEval_EvalFrameEx () from /usr/lib64
/libpython2.6.so.1.0
#47 0x00007ffff7b26431 in PyEval_EvalCodeEx () from /usr/lib64
/libpython2.6.so.1.0
#48 0x00007ffff7b1fa22 in PyEval_EvalCode () from /usr/lib64/libpython2.6.so.1.0
#49 0x00007ffff7b33145 in PyImport_ExecCodeModuleEx () from
/usr/lib64/libpython2.6.so.1.0
#50 0x00007ffff7b33384 in ?? () from /usr/lib64/libpython2.6.so.1.0
#51 0x00007ffff7b344e1 in ?? () from /usr/lib64/libpython2.6.so.1.0
#52 0x00007ffff7b3475a in ?? () from /usr/lib64/libpython2.6.so.1.0
#53 0x00007ffff7b34bf1 in ?? () from /usr/lib64/libpython2.6.so.1.0
#54 0x00007ffff7b351d4 in PyImport_ImportModuleLevel () from
/usr/lib64/libpython2.6.so.1.0
#55 0x00007ffff7b1f81b in ?? () from /usr/lib64/libpython2.6.so.1.0
#56 0x00007ffff7ae7cb2 in PyObject_Call () from /usr/lib64/libpython2.6.so.1.0
#57 0x00007ffff7b1fd26 in PyEval_CallObjectWithKeywords () from
/usr/lib64/libpython2.6.so.1.0
#58 0x00007ffff7b21b1e in PyEval_EvalFrameEx () from /usr/lib64
/libpython2.6.so.1.0
#59 0x00007ffff7b26431 in PyEval_EvalCodeEx () from /usr/lib64
/libpython2.6.so.1.0
#60 0x00007ffff7b1fa22 in PyEval_EvalCode () from /usr/lib64/libpython2.6.so.1.0
#61 0x00007ffff7b33145 in PyImport_ExecCodeModuleEx () from
/usr/lib64/libpython2.6.so.1.0
#62 0x00007ffff7b33384 in ?? () from /usr/lib64/libpython2.6.so.1.0
#63 0x00007ffff7b344e1 in ?? () from /usr/lib64/libpython2.6.so.1.0
#64 0x00007ffff7b3475a in ?? () from /usr/lib64/libpython2.6.so.1.0
#65 0x00007ffff7b350c3 in ?? () from /usr/lib64/libpython2.6.so.1.0
#66 0x00007ffff7b351d4 in PyImport_ImportModuleLevel () from
/usr/lib64/libpython2.6.so.1.0
#67 0x00007ffff7b1f81b in ?? () from /usr/lib64/libpython2.6.so.1.0
#68 0x00007ffff7ae7cb2 in PyObject_Call () from /usr/lib64/libpython2.6.so.1.0
#69 0x00007ffff7b1fd26 in PyEval_CallObjectWithKeywords () from
/usr/lib64/libpython2.6.so.1.0
#70 0x00007ffff7b21b1e in PyEval_EvalFrameEx () from /usr/lib64
/libpython2.6.so.1.0
#71 0x00007ffff7b26431 in PyEval_EvalCodeEx () from /usr/lib64
/libpython2.6.so.1.0
#72 0x00007ffff7b1fa22 in PyEval_EvalCode () from /usr/lib64/libpython2.6.so.1.0
#73 0x00007ffff7b3a791 in ?? () from /usr/lib64/libpython2.6.so.1.0
#74 0x00007ffff7ad46f0 in PyRun_InteractiveOneFlags () from
/usr/lib64/libpython2.6.so.1.0
#75 0x00007ffff7ad4811 in PyRun_InteractiveLoopFlags () from
/usr/lib64/libpython2.6.so.1.0
#76 0x00007ffff7b3b876 in PyRun_AnyFileExFlags () from
/usr/lib64/libpython2.6.so.1.0
#77 0x00007ffff7b42628 in Py_Main () from /usr/lib64/libpython2.6.so.1.0
#78 0x00007ffff6e8eb7d in __libc_start_main () from /lib64/libc.so.6
#79 0x00000000004006e9 in _start () at ../sysdeps/x86_64/elf/start.S:113
(gdb) 

openSUSE 11.3
# rpm -qa python python-matplotlib
python-matplotlib-1.0.1-17.1.x86_64
python-2.6.5-3.3.1.x86_64
# uname -a
Linux kiss 2.6.34.7-0.7-default #1 SMP 2010-12-13 11:13:53 +0100 x86_64 x86_64
x86_64 GNU/Linux

BR,
Attila

Thanks a lot Thomas,

besides that it should be

fig.colorbar(im)
instead of
ax.colorbar(im)

the example works great!

Best regards,
Daniel


2011/2/7 Eric Firing

> On 02/07/2011 10:48 AM, Daniel Mader wrote:
> > Hi,
> >
> > I am trying to add a (configurable) colorbar to a an array which I
> > simply plot with imshow().
> >
> > Could anyone please help me how to enhance it with a colorbar?
>
> Check out the gallery; several examples there use a colorbar.
> http://matplotlib.sourceforge.net/gallery.html
>
> Then look for relevant sections in the docs, such as
> http://matplotlib.sourceforge.net/users/image_tutorial.html
>
> http://matplotlib.sourceforge.net/api/pyplot_api.html#matplotlib.pyplot.colorbar
> etc.
>
> Eric
>
> >
> > import scipy,pylab
> > import matplotlib.cm <http://matplotlib.cm> as cm # colormaps
> > import matplotlib.colors as col # colormaps
> >
> > dat = scipy.array([[1,2,3,4],[5,6,7,8]])
> >
> > fig = pylab.figure()
> > ax = pylab.gca()
> > ax.set_title('the title')
> >
> > ## here's chaos :)
> > #cmap = cm.get_cmap('rainbow', 20) # 10 discrete colors
> > #ax.imshow(dat, cmap=cmap, interpolation='nearest')
> > #fig.colorbar(dat)
> > #min,max = dat.min(),dat.max()
> >
> > ax.imshow(dat,interpolation='nearest')
> > pylab.show()
> >
> > Thanks a lot in advance,
> > Daniel
> >
>

On 02/07/2011 10:48 AM, Daniel Mader wrote:
> Hi,
>
> I am trying to add a (configurable) colorbar to a an array which I
> simply plot with imshow().
>
> Could anyone please help me how to enhance it with a colorbar?

Check out the gallery; several examples there use a colorbar. 
http://matplotlib.sourceforge.net/gallery.html

Then look for relevant sections in the docs, such as
http://matplotlib.sourceforge.net/users/image_tutorial.html
http://matplotlib.sourceforge.net/api/pyplot_api.html#matplotlib.pyplot.colorbar
etc.

Eric

>
> import scipy,pylab
> import matplotlib.cm <http://matplotlib.cm> as cm # colormaps
> import matplotlib.colors as col # colormaps
>
> dat = scipy.array([[1,2,3,4],[5,6,7,8]])
>
> fig = pylab.figure()
> ax = pylab.gca()
> ax.set_title('the title')
>
> ## here's chaos :)
> #cmap = cm.get_cmap('rainbow', 20) # 10 discrete colors
> #ax.imshow(dat, cmap=cmap, interpolation='nearest')
> #fig.colorbar(dat)
> #min,max = dat.min(),dat.max()
>
> ax.imshow(dat,interpolation='nearest')
> pylab.show()
>
> Thanks a lot in advance,
> Daniel
>
>
>
> ------------------------------------------------------------------------------
> The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
> Pinpoint memory and threading errors before they happen.
> Find and fix more than 250 security defects in the development cycle.
> Locate bottlenecks in serial and parallel code that limit performance.
> http://p.sf.net/sfu/intel-dev2devfeb
>
>
>
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users

Hi,

I am trying to add a (configurable) colorbar to a an array which I simply
plot with imshow().

Could anyone please help me how to enhance it with a colorbar?

import scipy,pylab
import matplotlib.cm as cm # colormaps
import matplotlib.colors as col # colormaps

dat = scipy.array([[1,2,3,4],[5,6,7,8]])

fig = pylab.figure()
ax = pylab.gca()
ax.set_title('the title')

## here's chaos :)
#cmap = cm.get_cmap('rainbow', 20) # 10 discrete colors
#ax.imshow(dat, cmap=cmap, interpolation='nearest')
#fig.colorbar(dat)
#min,max = dat.min(),dat.max()

ax.imshow(dat,interpolation='nearest')
pylab.show()

Thanks a lot in advance,
Daniel

Jorge Scandaliaris <jorgesmbox-ml@...> writes:

< snip >
> I couldn't come up with a simple example showing the problem. My attempts so 
> far
> ended in working examples. I did find a change in my code that triggers the
> problem: My code uses a modified version of the lasso_demo example, contains 
> two
> axes, where I draw an image with imshow and a collection of circles with
> scatter. Originally scatter was called with a fixed size for all points, and I
> just changed it so each points gets a different size. 
> 
> Just don't ask me why this seemingly innocent change affects (breaks) the 
> event
> handling. I hope somebody can give me some hints. I'll keep checking the code 
> to

Because I couldn't reproduce the problem on simple examples, and also because I
have time constraints related to my work, I decided to go on ignoring this
problem (I can always avoid resizing windows...). This afternoon, I realized
that the problem had not appeared during the whole day, but then realized that
because I was debugging some changes introduced in my code, I had been using
very small images. After switching back to normal sizes, the problem came back. 

So, I modified the lasso_demo, increasing progressively the number polygons
drawn. When I reached 100000 polygons, I was able to reproduce the problem. It's
true that this a rather large number, but in my code it happens well below this
number, maybe because I assign a different color and size to each polygon. So my
previous observation that setting different sizes triggered the problem might
not be the real picture. It seems as if I was hitting some sort of limit.

Anyone would have a clue about what could be happening, or how can I try to
debug this?

Thanks,

jorges

On 02/07/2011 11:58 AM, Jouni K. Seppänen wrote:
> Jouni Seppänen <jk...@ik...> writes:
> 
>> In the meantime, I will commit a quick workaround that just disables
>> the fonts we can't handle instead of aborting with an assert.
> 
> Now committed in revision 8955 (1.0 maintenance branch) and 8956
> (svn trunk). Please test on your system.

The workaround fixes the error I was receiving.  Thank you very much!

-- 
Michael Anselmi
Class of 2011
Mathematics (B.S.)
University of Rochester
508.507.9738

On 02/07/2011 05:47 AM, Carlos Grohmann wrote:
> Hello all,
>
> I'm developing a software for Geology, using wxpython for the GUI.
> When I want to export any graphics, clicking on the
> "save" button on the MPL toolbar, I get a dialog to save the file
> (with a default "image.png" filename) and where I
> can choose between some file formats. When I select any format from
> the drop-down list, I expected it to change the extension
> of the file on the dialog, but it doesn't. So I have to set it up
> manually. Is this a bug?

Yes.  It works correctly with gtk, but it looks like there are problems 
with wx and qt4.

Eric

>
> thanks
>

On 02/07/2011 05:21 AM, Carlos Grohmann wrote:
> Hello there
>
> Is there support for exporting graphics as EMF files?
>
>> From what I've seen it seems to be discontinued.
>
> best
>
> Carlos
>
>
>

Carlos,

There is still a backend_emf.py, but I don't think it was ever complete 
(for example, it does not handle images).  It has no regular maintainer. 
  I don't know to what extent it still works.  It requires pyemf, which 
was last released in 2006.

Eric

Jouni Seppänen <jk...@ik...> writes:

>In the meantime, I will commit a quick workaround that just disables
>the fonts we can't handle instead of aborting with an assert.

Now committed in revision 8955 (1.0 maintenance branch) and 8956
(svn trunk). Please test on your system.

On 07.02.2011 17:17, Jouni K. Seppänen wrote:
> Jouni Seppänen<jk...@ik...>  writes:
>
>> I filed this in the bug tracker: https://sourceforge.net/tracker/?func=detail&aid=3175113&group_id=80706&atid=560720
>
> I installed TeX Live 2010 on my Mac in order to test this, but
> mysteriously, the pdftex.map file does not have a line for pbkdo8y. The
> closest match is
>
> pbkdo8r URWBookmanL-DemiBold ".167 SlantFont TeXBase1Encoding ReEncodeFont"<8r.enc<ubkd8a.pfb
>
> which is the same font but with another encoding. I wonder if this
> indicates a problem in the way Ubuntu sets up TeX Live?
>

Hi Jouni,

currently Ubuntu still uses Texlive 2009. I also got the same bug 
(http://article.gmane.org/gmane.comp.python.matplotlib.general/26110) 
with Texlive 2010 installed directly from tug.org.
I think it is unlikely that this is an Ubuntu specific problem, but I 
don't know for sure whether this file gets generated during the 
installation or is unmodified from the Texlive distribution.

Greetings
Alexander

Jouni Seppänen <jk...@ik...> writes:

> I filed this in the bug tracker: https://sourceforge.net/tracker/?func=detail&aid=3175113&group_id=80706&atid=560720

I installed TeX Live 2010 on my Mac in order to test this, but
mysteriously, the pdftex.map file does not have a line for pbkdo8y. The
closest match is

pbkdo8r URWBookmanL-DemiBold ".167 SlantFont TeXBase1Encoding ReEncodeFont" <8r.enc <ubkd8a.pfb

which is the same font but with another encoding. I wonder if this
indicates a problem in the way Ubuntu sets up TeX Live?

-- 
Jouni K. Seppänen
http://www.iki.fi/jks