matplotlib-users Mailing List for matplotlib

How force certain plot items to be on top and others
to get covered?

(When you have multiple functions being plotted
it is not clear how to get certain ones on top.)

Chris

On Tue, 3 Jan 2006, James Boyle apparently wrote: 
> I usually use Tex to build my tables but I saw the table 
> demo in the examples and thought that this might be a more 
> automated method. 

http://docutils.sourceforge.net/docs/ref/rst/directives.html#tables
might be useful if basic tables are your sole need.

Cheers,
Alan Isaac

John,

Thanks very much for the reply and sample code - my request was 
actually a little different.
What I really want is a table with no axes/plot at all - just the table.
I had tried what your example suggested but could not get around 
drawing axes.
I usually use Tex to build my tables but I saw the table demo in the 
examples and thought that this might be a more automated method.

--Jim

On Dec 31, 2005, at 6:24 AM, John Hunter wrote:

>>>>>> "James" == James Boyle <bo...@ll...> writes:
>
>     James> Say I wanted to construct a table, just a table,
>     James> independent of any graph etc.  Just like the example
>     James> table_demo.py but without the bar chart.
>
> The bar chart is incidental to this example.  You can plot whatever
> you want in an axes and then issue the table command to generate the
> table below (or in some other place) around the axes.
>
> Eg, in the example below, I issue a plot command and remove the bar
> command from the table_demo in the examples dir (the "colours" module
> is also in the examples directory).
>
> JDH
>
> #!/usr/bin/env python
> import matplotlib
>
> from pylab import *
> from colours import get_colours
>
> axes([0.2, 0.2, 0.7, 0.6])   # leave room below the axes for the table
> plot([1,2,3])
>
>
> data = [[  66386,  174296,   75131,  577908,   32015],
>         [  58230,  381139,   78045,   99308,  160454],
>         [  89135,   80552,  152558,  497981,  603535],
>         [  78415,   81858,  150656,  193263,   69638],
>         [ 139361,  331509,  343164,  781380,   52269]]
>
> colLabels = ('Freeze', 'Wind', 'Flood', 'Quake', 'Hail')
> rowLabels = ['%d year' % x for x in (100, 50, 20, 10, 5)]
>
> # Get some pastel shades for the colours
> colours = get_colours(len(colLabels))
> colours.reverse()
> rows = len(data)
>
> ind = arange(len(colLabels)) + 0.3  # the x locations for the groups
> cellText = []
> width = 0.4     # the width of the bars
> yoff = array([0.0] * len(colLabels)) # the bottom values for stacked 
> bar chart
> for row in xrange(rows):
>     yoff = yoff + data[row]
>     cellText.append(['%1.1f' % (x/1000.0) for x in yoff])
>
> # Add a table at the bottom of the axes
> colours.reverse()
> cellText.reverse()
> the_table = table(cellText=cellText,
>                   rowLabels=rowLabels, rowColours=colours,
>                   colLabels=colLabels,
>                   loc='bottom')
> ylabel("Loss $1000's")
>
> xticks([])
> title('Loss by Disaster')
>
> show()
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep through log 
> files
> for problems?  Stop!  Download the new AJAX search engine that makes
> searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
> http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
>

lis...@ma... wrote:
> I realize I should know the answer to this question by now, but how  do 
> I avoid the markup that occurs when updating changed files by cvs?  For 
> example in lib/matplotlib/numerix/fft/__init__.py I get this line  
> following an update:
> 
>      <<<<<<< __init__.py
> 
> at the moment I am updating matplotlib via:
> 
> cvs -q up -Pd

cvs -q up -PCd

-C means get a Clean" copy:

Overwrite locally modified files with clean copies from  the repository 
(the modified file is saved in .#file.revision, however).

That's what you do if you just want whatever the current version in the 
repository is. However, that markup is a how cvs handles conflicts on 
merge. If you haven't changed your copy, you shouldn't be getting any of 
that.


-- 
Christopher Barker, Ph.D.
Oceanographer
                                     		
NOAA/OR&R/HAZMAT         (206) 526-6959   voice
7600 Sand Point Way NE   (206) 526-6329   fax
Seattle, WA  98115       (206) 526-6317   main reception

Chr...@no...

I realize I should know the answer to this question by now, but how  
do I avoid the markup that occurs when updating changed files by cvs?  
For example in lib/matplotlib/numerix/fft/__init__.py I get this line  
following an update:

      <<<<<<< __init__.py

at the moment I am updating matplotlib via:

cvs -q up -Pd

Thanks,
Chris

--
Christopher J. Fonnesbeck

Population Ecologist, Marine Mammal Section
Fish & Wildlife Research Institute (FWC)
St. Petersburg, FL

Adjunct Assistant Professor
Warnell School of Forest Resources
University of Georgia
Athens, GA

T: 727.235.5570
E: Chr...@My...

Clovis, John -

I also made a change in release_zoom for the case that x-axes are shared an=
d
one of the graphs has the aspect_ratio set to 'equal' or 'scaled'. This has
been submitted as a patch (John has the file), but I don't think it is in
CVS yet. It works great. Below is what I added at the end of the
release_zoom function, and the additional function def
fix_aspect_after_zoom(self,a), which I added.

Mark

        aspect =3D a.get_aspect()
        if aspect =3D=3D 'equal' or aspect =3D=3D 'scaled':
            self.fix_aspect_after_zoom(a)
        else:
            aspect_shared =3D ''
            if a._sharex !=3D None: aspect_shared =3D a._sharex.get_aspect(=
)
            if aspect_shared =3D=3D 'equal' or aspect_shared =3D=3D 'scaled=
':
                self.fix_aspect_after_zoom(a._sharex)

        self.draw()
        self._xypress =3D None
        self._button_pressed =3D=3D None

        self.push_current()
        self.release(event)

    def fix_aspect_after_zoom(self,a):
        lold,bold,wold,hold =3D a.get_position()
        aspect =3D a.get_aspect()
        a.set_aspect(aspect,True)
        l,b,w,h =3D a.get_position()
        if w !=3D wold:  # width of axes was changed
            ratio =3D w / wold
            for ax in a.get_figure().axes:  # see if any subplot shares thi=
s
axis
                if ax._sharex =3D=3D a:
                    lax,bax,wax,hax =3D ax.get_position()
                    wnew =3D ratio * wax
                    lnew =3D lax
                    if aspect =3D=3D 'equal': lnew =3D lax - 0.5 * ( wnew -=
 wax )
                    ax.set_position( [lnew, bax, wnew, hax] )