matplotlib-users Mailing List for matplotlib

>>>>> "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()

>>>>> "Christian" == Christian Seberino <seb...@sp...> writes:
 Christian> How set grid line properties like solid lines for
 Christian> regular plot?
You can set the defaults in your rc file with the foloowing properties
 grid.color : black # grid color
 grid.linestyle : : # dotted
 grid.linewidth : 0.5 # in points
or you can set the properties in a script by getting a list of the x
and y grid lines
 glines = ax.get_xgridlines() + ax.get_ygridlines()
 setp(glines, linestyle='-', color=0.5, linewidth=1)
JDH

Upon first creation you can set the figure size:
figure(figsize=3D(3,6)) for example gives you a tall figure.
But you cannot resize the figure with a command afterwards yet (if I am not
mistaken).
In interactive mode you can stretch the figure on the screen by dragging th=
e
window.
M.

How make plot TALLER keeping same y-min and y-max?? (i.e. stretch it)
for PNG and on screen??
chris

How set grid line properties like solid lines for regular plot?

Hello all,
I installed the latest matplot lib last night on my powerbook running 
Mac OS 10.4. Overall the installation went well, but there were a 
few hitches. I was able to solve some of the simple problems, but 
other remain. I wanted to document my experience and also see if 
anyone has solutions to the other problems.
Here is what I did:
1. Latest Numeric
2. Bob Ippolito's python 2.4.1 (with the Tiger fix)
3. IPython 0.7.0rc1
4. wxPython 2.6.1.0 unicode binary from the wxpython site
5. libpng and freetype from I-Installer
6. CVS matplotlib as of late 12/29/05
I then did
cd matplotlib
python setup.py build
sudo python setup.py install
I then copied the default matplotlib into the ~/.matplotlib directory 
and changed the backend.
BACKEND ISSUES
Out of the box, the WX and TkAgg and CocoaAgg backends worked. I did 
have problems with WXAgg (which I have solved) and with PS (which I 
have not solved).
WXAgg:
When the WXAgg backend was used I got an exception (MemoryError) when 
I plotted things. I traced it back to the wxconfig command not being 
in my PATH variable.
When I moved wxconfig from /usr/local/lib/wxPython-unicode-2.6.1.0/ 
bin to /usr/local/bin and rebuilt everything, the WXAgg backend 
worked fine.
While the wxconfig PATH issue is documented in the source code 
(setupext.py I think) I didn't see anything in the INSTALL file about 
it. A brief note should be added to the INSTALL file.
PS:
When the PS backend is used, the .ps and .eps files produced are 
somewhat problematic. Here is what I observed:
- PS backend, savefig("test.ps")
	The .ps file cannot be opened by preview: "Couldn't convert the 
PostScript file to a PDF file."
	But running ps2pdf on it produced a pdf file.
- PS backend, savefig("test.eps")
	This does produce a nice eps file that preview can read.
I get the same behavior when using the WXAgg backend and trying to 
save the figure as a .ps or .eps file.
I know it is a minor issue, but Is there a way to get a raw .ps file 
that Preview can display?
Thanks in advance
Brian

On Dec 28, 2005, at 6:29 PM, Christopher Barker wrote:
> I just compiled Matplotlib 0.85 with the WXAgg back end.
>
> It seems to work fine, but when I run it, I get:
<errors snipped>
> This happens with pylab.show(), or if I use wxmpl.PlotPanel in an 
> App of my own.
This looks like another weird wxPython/wxWidgets/Gnome/CUPS problem, 
similar to the one Ryan Krauss had in October. Given that you're 
getting very different error messages, I'm not sure that his solution 
is applicable:
On Oct 20, 2005, at 5:12 PM, Ryan Krauss wrote:
> So, it appears this is a problem with CUPS and wxPython. I had never
> plugged a printer into this fairly new installation of ubuntu. After
> doing so and making sure that cups is running, the IPP error went
> away.
>
> On 10/20/05, Ken McIvor <mc...@ii...> wrote:
>> Based on the strace output, I believe that the warning is getting 
>> generated
>> when trying to start up CUPS (`/etc/cups/client.conf' is opened at 
>> line
>> 10484), from within lincups, which is loaded by libgnomeprintcups, 
>> which is
>> loaded by libgnomeprint, which is loaded by wxWidgets, which is 
>> loaded by
>> wxPython (whee!). Do you have a working CUPS installation on your 
>> computer?
>> If that's not the solution, then I don't know what is; try 
>> emailing the
>> wxPython-users list.
On Dec 28, 2005, at 6:29 PM, Christopher Barker wrote:
> I haven't noticed this in any other wxPython apps. I have no idea 
> how to debug this, as it's not an error at the Python level.
I had Ryan send me some strace output:
	$ strace python -c short_wxagg_script.py > strace.txt 2>&1
You probably don't want to send it to the lists, but I'll be happy to 
take a look at it. I also have the strace output from October, if 
that would help the wxPython gurus better understand what's going on.
Another useful bit of information would be whether or not the 
wxPython demo's printing framework example causes the same errors 
when you run it. That might help us nail down the source of the 
problem (e.g. is it at the wxPython-level, or something WxAgg is 
doing to wxPython, or the inclusion of the printing framework?).
Ken

Hi all,
I just compiled Matplotlib 0.85 with the WXAgg back end.
It seems to work fine, but when I run it, I get:
** (python2.4:24617): WARNING **: failed request with status 200
(python2.4:24617): GnomePrintCupsPlugin-WARNING **: iconv does not 
support ppd character encoding: ISOLatin1, trying CSISOLatin1
** (python2.4:24617): WARNING **: failed request with status 200
This happens with pylab.show(), or if I use wxmpl.PlotPanel in an App of 
my own.
I haven't noticed this in any other wxPython apps. I have no idea how to 
debug this, as it's not an error at the Python level.
Linux Fedora Core4
Python 2.4.1
wxPython '2.6.1.0' (gtk2-unicode[
matplotlib 0.85
Anyone have any ideas?
-Chris
-- 
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...

This is just a heads up to those using the scipy backend for matplotlib, 
that CVS matplotlib contains the changes needed to coincide with the SVN 
version of scipy_core. This means that if you use CVS matplotlib, you 
will need a current version of scipy_core out of SVN to use scipy as a 
backend. The new scipy_core also has a scipy.base.mlab file to be 
completely backwards compatible (this simplifies the matplotlib.mlab 
file considerably).
A release of scipy_core with the new module structure for linear 
algebra, ffts, and random numbers will be made by the first of the year.
-Travis

Hi all (particularly John),
I just compiled mpl on Linux Fedora core 4 with wxAGG support. In doing 
so, I got tripped up, for a little bit, with wx-config.
Once I figured it out, I ended up re-arranging the build_wxagg function 
a bit, just so that more meaning full error messages are likely.
The big difference is that even if WXAgg is on auto, you still get the 
message about wx-config. Here's my version of build_wxagg, and I've 
enclosed the whole file if you want to diff it. Perhaps you'd like to 
role these changes in.
-Chris
def build_wxagg(ext_modules, packages, numerix, abortOnFailure):
 global BUILT_WXAGG
 if BUILT_WXAGG:
 return
 wxconfig = find_wx_config()
 # Avoid aborting the whole build process if `wx-config' can't be 
found and
 # BUILD_WXAGG in setup.py is set to "auto"
 if wxconfig is None:
 print """
WXAgg's accelerator requires `wx-config'.
The `wx-config\' executable could not be located in any directory of the
PATH environment variable. If you want to build WXAgg, and wx-config is
in some other location or has some other name, set the WX_CONFIG
environment variable to the full path of the executable like so:
export WX_CONFIG=/usr/lib/wxPython-2.6.1.0-gtk2-unicode/bin/wx-config
"""
 if not abortOnFailure:
 print """Building MPL without wxAgg"""
 BUILT_WXAGG = True
 return
 else:
 sys.exit(1)
 elif not check_wxpython_headers(wxconfig):
 print 'WXAgg\'s accelerator requires the wxPython headers.'
 if not abortOnFailure:
 BUILT_WXAGG = True
 return
 else:
 print """
The wxPython header files could not be located in any of the standard 
include
directories or include directories reported by `wx-config --cppflags'."""
 sys.exit(1)
 deps = ['src/_wxagg.cpp', 'src/mplutils.cpp', 'src/_transforms.cpp']
 deps.extend(glob.glob('CXX/*.cxx'))
 deps.extend(glob.glob('CXX/*.c'))
 module = Extension('matplotlib.backends._wxagg', deps)
 add_agg_flags(module)
 add_ft2font_flags(module)
 add_wx_flags(module, wxconfig)
 ext_modules.append(module)
 BUILT_WXAGG = True
-- 
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...

 Well, it is there and it works. There is no toolbar, and the
save image button is not implemented. I really haven't had access to
a mac in a while, so there hasn't been much development. I basically
figured out the hard part of how to do the agg buffer to NSImage
bridge. The rest of the perks should be pretty simple. The code is
in backend_cocoaagg.py and the nib files are in the backends folder.
- Charlie
On 12/27/05, Christopher Barker <Chr...@no...> wrote:
> Charlie,
>
> IIRC, you were working on a Cocoa back-end for MPL a while back. How's
> that coming?
>
> If it was someone else, please speak up!
>
> -Chris
>
>
>
>
> --
> 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...
>

Say I wanted to construct a table, just a table, independent of any 
graph etc.
Just like the example table_demo.py but without the bar chart.
What is the simplest ( i. e. easiest ) way to do this ?
 In the axes.py code it says to use the Tables class to gain more 
control but this involves some detail work that I am trying to avoid.
If there is no clever solution to which I am oblivious , I'll give the 
Table route a go.
--Jim

Charlie,
IIRC, you were working on a Cocoa back-end for MPL a while back. How's 
that coming?
If it was someone else, please speak up!
-Chris
-- 
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...

Dear Matplotlib users:
I was unable to download the PDF user's guide from the main Matplotlib =
page on Sourceforge.net. I tried both with Internet Explorer and Mozilla =
Firefox and the download simply stopped at less than halfway through, =
both times. I noticed a reference to a similar problem in the list =
earlier this year but the alternate site mentioned there does not seem =
to exist anymore. Any suggestions would be appreciated. Both browsers =
seem to work fine with all other files, including other PDF files. =
Thanks.
V.R.Anand

I believe the issue is still a bug. I have recently begun working with
pylab. With the latest release, I get the same error when I execute the
vertical_ticktabels.py example.
The error message is: "TypeError: list indices must be integers"=20
Brian Bowen

Charles R. Twardy wrote:
> OK, here 'goes. Verbose stacktrace and version info. Haven't tried
> other backends, won't tonight.
Thanks for the info. Nothing jumps at me, but I was mostly providing you with 
pointers on what kind of info may help John, who is the one who actually knows 
that code. I've only bumped into the problem (which he has never found on a 
machine he works on) and failed to produce any kind of solution. Let's hope 
some of this flips a switch for him.
Cheers,
f

I'm struggling with trying to learn python, QT, pyqt, and matplotlib
all at the same time...
It would be very helpful for me if someone could modify the 
embedding_in_qt.py to include NavigationToolbar2. I've
been trying to get this to work all day, and am just about
worn out...
Thanks!!
-- 
-----------------------------------------------------------------------
| Alan K. Jackson | To see a World in a Grain of Sand |
| al...@aj... | And a Heaven in a Wild Flower, |
| www.ajackson.org | Hold Infinity in the palm of your hand |
| Houston, Texas | And Eternity in an hour. - Blake |
-----------------------------------------------------------------------

OK, here 'goes. Verbose stacktrace and version info. Haven't tried
other backends, won't tonight.
I. STACKTRACE: 'xmode verbose'
-------------------------------------------------------
In [5]:a.plot_status_histograms('Personality')
---------------------------------------------------------------------------
exceptions.SystemError Traceback (most
recent call last)
/home/ctwardy/Projects/SARBayes/Data/Docs/Natsar Report/<console>
/home/ctwardy/Projects/SARBayes/Data/Docs/Natsar Report/sardata.py in
plot_status_histograms(self=3D<sardata.SarData instance>,
category=3D'Personality')
 788 colors =3D status_colors,
 789 x_bins =3D status_order,
--> 790 pies =3D True)
 global pies =3D undefined
 global True =3D undefined
 791
 792 def plot_histograms(self,
/home/ctwardy/Projects/SARBayes/Data/Docs/Natsar Report/sardata.py in
plot_histograms(self=3D<sardata.SarData instance>, varX=3D'Status',
category=3D'Personality', bigtitle=3D'Status by Personality', colors=3D['b'=
,
'g', 'r', 'k'], contin=3DFalse, grid=3DFalse, missing=3DFalse, numcols=3D2,
N_label=3D'N_S', pies=3DTrue, x_bins=3D['Unhurt', 'Injured', 'Fatality', 'N=
o
Trace'], x_label=3D'Status', x_ticks=3D[0.5, 1.5, 2.5, 3.5],
x_ticklabels=3D['Unhurt', 'Injured', 'Fatality', 'No Trace'],
y_prop=3DTrue)
 902 # Now begin the plotting proper
 903 plotnum =3D 0
--> 904 figtext(0.5, 0.95, bigtitle, font, fontsize=3D12)
 global figtext =3D <function figtext at 0x30806170>
 bigtitle =3D 'Status by Personality'
 font =3D {'color': 'k', 'fontweight': 'bold', 'fontname':
'Sans', 'verticalalignment': 'top', 'horizontalalignment': 'center'}
 global fontsize =3D undefined
 905 for value in values:
 906 plotnum +=3D 1
/usr/lib/python2.3/site-packages/matplotlib/pylab.py in
figtext(*args=3D(0.5, 0.94999999999999996, 'Status by Personality',
{'color': 'k', 'fontname': 'Sans', 'fontweight': 'bold',
'horizontalalignment': 'center', 'verticalalignment': 'top'}),
**kwargs=3D{'fontsize': 12})
 772 def figtext(*args, **kwargs):
 773
--> 774 ret =3D gcf().text(*args, **kwargs)
 ret =3D undefined
 global gcf.text =3D undefined
 args =3D (0.5, 0.94999999999999996, 'Status by Personality',
{'color': 'k', 'fontweight': 'bold', 'fontname': 'Sans',
'verticalalignment': 'top', 'horizontalalignment': 'center'})
 kwargs =3D {'fontsize': 12}
 775 draw_if_interactive()
 776 return ret
SystemError: ../Objects/moduleobject.c:48: bad argument to internal functio=
n
> /usr/lib/python2.3/site-packages/matplotlib/pylab.py(774)figtext()
-> ret =3D gcf().text(*args, **kwargs)
II. Versions
----------------------------------
> uname -a
Linux amelia 2.6.14-2-powerpc #1 Sat Nov 26 18:12:00 UTC 2005 ppc GNU/Linux
> python -V
Python 2.3.5
> ipython -V
0.6.15
>
>>> matplotlib.__version__
'0.85.1.cvs'
> gcc --version
gcc (GCC) 4.0.3 20051201 (prerelease) (Debian 4.0.2-5)
On 12/22/05, Fernando Perez <Fer...@co...> wrote:
> Mmh, this may be the tip of the thread to unravel a long-standing problem
> which has stumped both John and me several times. I've seen the message
>
> SystemError: ../Objects/moduleobject.c:48: bad argument to internal funct=
ion
>
> when using the GtkAgg backend, but the funny thing is that the issue woul=
dn't
> appear for John even when we were both running _as the same user, on the =
same
> box_. The only difference was that I was executing from the console and =
he
> was logged in remotely. However, in that case it would always silently
> segfault, so we never saw the traceback you are seeing, which made the pr=
oblem
> very hard to debug without really sinking time into it. But with your
> behavior, we may get more info.
>
> Some things to try which will help:
>
> 1. Version info, for everything (OS, python, ipython, mpl, gcc)
>
> 2. In ipython, type 'xmode verbose' before testing, and paste the entire
> ipython traceback. I don't care if it's big, for this problem anything c=
an help.
>
> 3. Backend info. Try cycling through all the backends, and see if the pr=
oblem
> appears with all or only with some.
>
>
> With more details, it may be possible to make some progress on this one..=
.
>
> Cheers,
>
> f
>
--
Charles R. Twardy

Charles R. Twardy wrote:
> For some reason, the FIRST time I try to plot something in an ipython
> session, I get:
> 
> SystemError: ../Objects/moduleobject.c:48: bad argument to internal function
> 
>>/usr/lib/python2.3/site-packages/matplotlib/pylab.py(774)figtext()
> 
> -> ret = gcf().text(*args, **kwargs)
> 
> The last entry in the stacktrace is:
> /usr/lib/python2.3/site-packages/matplotlib/pylab.py in figtext(*args,
> **kwargs) 772 def figtext(*args, **kwargs):
> 773
> --> 774 ret = gcf().text(*args, **kwargs)
> 775 draw_if_interactive()
> 776 return ret
> 
> After that everything works fine. This error is robust: every first
> plot in ipython. Haven't tried command-line yet.
Mmh, this may be the tip of the thread to unravel a long-standing problem 
which has stumped both John and me several times. I've seen the message
SystemError: ../Objects/moduleobject.c:48: bad argument to internal function
when using the GtkAgg backend, but the funny thing is that the issue wouldn't 
appear for John even when we were both running _as the same user, on the same 
box_. The only difference was that I was executing from the console and he 
was logged in remotely. However, in that case it would always silently 
segfault, so we never saw the traceback you are seeing, which made the problem 
very hard to debug without really sinking time into it. But with your 
behavior, we may get more info.
Some things to try which will help:
1. Version info, for everything (OS, python, ipython, mpl, gcc)
2. In ipython, type 'xmode verbose' before testing, and paste the entire 
ipython traceback. I don't care if it's big, for this problem anything can help.
3. Backend info. Try cycling through all the backends, and see if the problem 
appears with all or only with some.
With more details, it may be possible to make some progress on this one...
Cheers,
f

For some reason, the FIRST time I try to plot something in an ipython
session, I get:
SystemError: ../Objects/moduleobject.c:48: bad argument to internal functio=
n
> /usr/lib/python2.3/site-packages/matplotlib/pylab.py(774)figtext()
-> ret =3D gcf().text(*args, **kwargs)
The last entry in the stacktrace is:
/usr/lib/python2.3/site-packages/matplotlib/pylab.py in figtext(*args,
**kwargs) 772 def figtext(*args, **kwargs):
 773
--> 774 ret =3D gcf().text(*args, **kwargs)
 775 draw_if_interactive()
 776 return ret
After that everything works fine. This error is robust: every first
plot in ipython. Haven't tried command-line yet.
-C
--
Charles R. Twardy

Hi Folks,
Has anyone got any code for making a Wind Rose with MPL? (I'd like to hear 
about other pythonic methods too)
If you don't know what a Wind Rose is, you probably don't have code for making 
one, but just in case you're curious, it's essentially a histogram in polar 
coordinates. It can show you what fraction of the time the wind (or any 
directional phenomenon) is is blowing from what direction.
here's some examples:
http://www.enviroware.com/windrose.htm
Or google it yourself.
If you don't mind self contained, Windows only software!
Thanks
-Chris
PS: Jeff, I cc's you, because you seemed a very likely candidate for having 
something.
-- 
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...

Dear John,
Thanks for your support.
Pressing the X/Y key works fine in the pan menu! I tested it!
But my first suggestion would be an additional keyword in the subplot 
command, something like:
ax2 = subplot(312, sharex=ax1, freezey=True)
In fact, there would be necessary 2 additional keywords (freezex, 
freezey) that would disable
limit changes after the subplot creation. Obviouly, if freezey=False or 
None, the axis limits would
be free to be changed by the zooming tool.
Clovis
John Hunter wrote:
>>>>>>"Clovis" == Clovis Goldemberg <cl...@pe...> writes:
>>>>>> 
>>>>>>
>
> Clovis> When I use the zoom feature of the NavigationToolbar, the
> Clovis> xaxis is shared between all 3 graphs. But the yaxis
> Clovis> limits are free. Obviously, they could also be shared but
> Clovis> this is not want I want. I would like to "force" or
> Clovis> "freeze" the Y axis to a given value. Consequently, the
> Clovis> zoom feature would act only along the X axis.
>
>When using the right mouse zoom in pan/zoom mode, if you hold 'x' down
>the zoom will only be in the x direction. ditto for 'y'. It would be
>nice to support this for zoom to rect as well. On the todo list!
>
>JDH
>
>
>-------------------------------------------------------
>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
>
>
> 
>

>>>>> "Clovis" == Clovis Goldemberg <cl...@pe...> writes:
 Clovis> When I use the zoom feature of the NavigationToolbar, the
 Clovis> xaxis is shared between all 3 graphs. But the yaxis
 Clovis> limits are free. Obviously, they could also be shared but
 Clovis> this is not want I want. I would like to "force" or
 Clovis> "freeze" the Y axis to a given value. Consequently, the
 Clovis> zoom feature would act only along the X axis.
When using the right mouse zoom in pan/zoom mode, if you hold 'x' down
the zoom will only be in the x direction. ditto for 'y'. It would be
nice to support this for zoom to rect as well. On the todo list!
JDH

Consider the following code (adapted from shared_axis_demo.py):
from pylab import *
t = arange(0.01, 5.0, 0.01)
s1 = sin(2*pi*t)
s2 = sin(4*pi*t)
s3 = sin(6*pi*t)
ax1 = subplot(311)
plot(t,s1)
grid('True')
ax2 = subplot(312, sharex=ax1)
plot(t, s2)
grid('True')
ax3 = subplot(313, sharex=ax1)
plot(t, s3)
grid('True')
show()
When I use the zoom feature of the NavigationToolbar, the xaxis is 
shared between all 3 graphs.
But the yaxis limits are free. Obviously, they could also be shared but 
this is not want I want.
I would like to "force" or "freeze" the Y axis to a given value. 
Consequently, the zoom feature would act only
along the X axis.
Any ideas??
Clovis Goldemberg
University of Sao Paulo

Apologies for the double-post.
An update: installing scipy, then rebuilding and reinstalling 
matplotlib get things working using Numeric; numarray still fails. That 
fragility makes me worry something is still wrong, but I just got a 
basic test plot (1,2,3) to display using ipython, and that's good enough 
for me for now. Advice would still be welcome, but is no longer as 
desperate. =)
Also, I should have mentioned that the machine in question is Ubuntu 
5.10 PPC. Tomorrow I'll see if I can get matplotlib successfully 
installed on the MacOS X side...
Hoping this message helps someone else down the line (and that the list 
will forgive me asking and then answering my own question...),
Andrew Stout
Andrew Stout wrote:
> Hi--
> 
> I'm trying to get matplotlib installed on my laptop before my holiday 
> travels begin. I've acquired all the dependencies through synaptic and 
> built matplotlib from source, but when I attempt to import pylab I get 
> the following error:
> 
> andrew@idioteque:~/.matplotlib$ python
> Python 2.4.2 (#2, Sep 30 2005, 22:23:39)
> [GCC 4.0.2 20050808 (prerelease) (Ubuntu 4.0.1-4ubuntu8)] on linux2
> Type "help", "copyright", "credits" or "license" for more information.
> >>> import pylab
> /usr/lib/python2.4/site-packages/matplotlib/__init__.py:843: 
> UserWarning: Bad key "lines.data_clipping" on line 55 in 
> /home/andrew/.matplotlib/matplotlibrc
> warnings.warn('Bad key "%s" on line %d in %s' % (key, cnt, fname))
> /usr/lib/python2.4/site-packages/matplotlib/__init__.py:843: 
> UserWarning: Bad key "tick.major.size" on line 145 in 
> /home/andrew/.matplotlib/matplotlibrc
> warnings.warn('Bad key "%s" on line %d in %s' % (key, cnt, fname))
> /usr/lib/python2.4/site-packages/matplotlib/__init__.py:843: 
> UserWarning: Bad key "tick.minor.size" on line 146 in 
> /home/andrew/.matplotlib/matplotlibrc
> warnings.warn('Bad key "%s" on line %d in %s' % (key, cnt, fname))
> /usr/lib/python2.4/site-packages/matplotlib/__init__.py:843: 
> UserWarning: Bad key "tick.major.pad" on line 147 in 
> /home/andrew/.matplotlib/matplotlibrc
> warnings.warn('Bad key "%s" on line %d in %s' % (key, cnt, fname))
> /usr/lib/python2.4/site-packages/matplotlib/__init__.py:843: 
> UserWarning: Bad key "tick.minor.pad" on line 148 in 
> /home/andrew/.matplotlib/matplotlibrc
> warnings.warn('Bad key "%s" on line %d in %s' % (key, cnt, fname))
> /usr/lib/python2.4/site-packages/matplotlib/__init__.py:843: 
> UserWarning: Bad key "tick.color" on line 149 in 
> /home/andrew/.matplotlib/matplotlibrc
> warnings.warn('Bad key "%s" on line %d in %s' % (key, cnt, fname))
> /usr/lib/python2.4/site-packages/matplotlib/__init__.py:843: 
> UserWarning: Bad key "tick.labelsize" on line 150 in 
> /home/andrew/.matplotlib/matplotlibrc
> warnings.warn('Bad key "%s" on line %d in %s' % (key, cnt, fname))
> Traceback (most recent call last):
> File "<stdin>", line 1, in ?
> File "/usr/lib/python2.4/site-packages/pylab.py", line 1, in ?
> from matplotlib.pylab import *
> File "/usr/lib/python2.4/site-packages/matplotlib/pylab.py", line 194, 
> in ?
> import cm
> File "/usr/lib/python2.4/site-packages/matplotlib/cm.py", line 5, in ?
> import colors
> File "/usr/lib/python2.4/site-packages/matplotlib/colors.py", line 33, 
> in ?
> from numerix import array, arange, take, put, Float, Int, where, \
> File 
> "/usr/lib/python2.4/site-packages/matplotlib/numerix/__init__.py", line 
> 62, in ?
> from Matrix import Matrix
> ImportError: No module named Matrix
> >>>
> 
> This happens with Numeric specified in my matplotlibrc. If I specify 
> numarray, I get a different import error:
> 
> andrew@idioteque:~/.matplotlib$ python
> Python 2.4.2 (#2, Sep 30 2005, 22:23:39)
> [GCC 4.0.2 20050808 (prerelease) (Ubuntu 4.0.1-4ubuntu8)] on linux2
> Type "help", "copyright", "credits" or "license" for more information.
> >>> import pylab
> /usr/lib/python2.4/site-packages/matplotlib/__init__.py:843: 
> UserWarning: Bad key "lines.data_clipping" on line 55 in 
> /home/andrew/.matplotlib/matplotlibrc
> warnings.warn('Bad key "%s" on line %d in %s' % (key, cnt, fname))
> /usr/lib/python2.4/site-packages/matplotlib/__init__.py:843: 
> UserWarning: Bad key "tick.major.size" on line 145 in 
> /home/andrew/.matplotlib/matplotlibrc
> warnings.warn('Bad key "%s" on line %d in %s' % (key, cnt, fname))
> /usr/lib/python2.4/site-packages/matplotlib/__init__.py:843: 
> UserWarning: Bad key "tick.minor.size" on line 146 in 
> /home/andrew/.matplotlib/matplotlibrc
> warnings.warn('Bad key "%s" on line %d in %s' % (key, cnt, fname))
> /usr/lib/python2.4/site-packages/matplotlib/__init__.py:843: 
> UserWarning: Bad key "tick.major.pad" on line 147 in 
> /home/andrew/.matplotlib/matplotlibrc
> warnings.warn('Bad key "%s" on line %d in %s' % (key, cnt, fname))
> /usr/lib/python2.4/site-packages/matplotlib/__init__.py:843: 
> UserWarning: Bad key "tick.minor.pad" on line 148 in 
> /home/andrew/.matplotlib/matplotlibrc
> warnings.warn('Bad key "%s" on line %d in %s' % (key, cnt, fname))
> /usr/lib/python2.4/site-packages/matplotlib/__init__.py:843: 
> UserWarning: Bad key "tick.color" on line 149 in 
> /home/andrew/.matplotlib/matplotlibrc
> warnings.warn('Bad key "%s" on line %d in %s' % (key, cnt, fname))
> /usr/lib/python2.4/site-packages/matplotlib/__init__.py:843: 
> UserWarning: Bad key "tick.labelsize" on line 150 in 
> /home/andrew/.matplotlib/matplotlibrc
> warnings.warn('Bad key "%s" on line %d in %s' % (key, cnt, fname))
> Traceback (most recent call last):
> File "<stdin>", line 1, in ?
> File "/usr/lib/python2.4/site-packages/pylab.py", line 1, in ?
> from matplotlib.pylab import *
> File "/usr/lib/python2.4/site-packages/matplotlib/pylab.py", line 194, 
> in ?
> import cm
> File "/usr/lib/python2.4/site-packages/matplotlib/cm.py", line 5, in ?
> import colors
> File "/usr/lib/python2.4/site-packages/matplotlib/colors.py", line 33, 
> in ?
> from numerix import array, arange, take, put, Float, Int, where, \
> File 
> "/usr/lib/python2.4/site-packages/matplotlib/numerix/__init__.py", line 
> 53, in ?
> from numarray.convolve import cross_correlate, convolve
> ImportError: No module named convolve
> >>>
> 
> 
> So, I suspect something is wrong in Numerix, but I have no idea what, or 
> more importantly how to fix it. Could anyone help? It would be much 
> appreciated.
> 
> Please cc me; I am not subscrived to the list.
> 
> Thanks in advance,
> Andrew Stout
>