matplotlib-users Mailing List for matplotlib

On 6/30/06, Belkind, Ronnen <Ron...@ci...> wrote:
>
>
>
> I downlaoded matplotlib-0.87.3.tar.gz from sourceforge and am attempting to
> compile/install it on a RedHat linux installation source.  When I run setup
> I get the following error.
>
> $: python setup.py build
> Traceback (most recent call last):
>   File "setup.py", line 63, in ?
>     from setupext import build_agg, build_gtkagg, build_tkagg, build_wxagg,\
>   File "setupext.py", line 118, in ?
>     win32_compiler = get_win32_compiler()
>   File "setupext.py", line 115, in get_win32_compiler
>     if 'mingw32' in v:
> TypeError: 'in <string>' requires character as left operand
>
>
> I'm runing python 2.2.3.  libpng, zlib, freetype, and Numeric are all
> installed.
> Any suggestions are greatly appreciated.

This error is 2.2 specific:

littlewood[~]> python
Python 2.2.2 (#1, Feb 24 2003, 19:13:11)
[GCC 3.2.2 20030222 (Red Hat Linux 3.2.2-4)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> 'ab' in 'abcde'
Traceback (most recent call last):
  File "<stdin>", line 1, in ?
TypeError: 'in <string>' requires character as left operand


littlewood[~]> python2.3.5
Python 2.3.5 (#1, Jan 25 2006, 12:49:33)
[GCC 3.2.2 20030222 (Red Hat Linux 3.2.2-5)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> 'ab' in 'abcde'
True

I'm pretty sure that mpl requires python 2.3.  At this point, python
2.2 is old enough that many packages just don't support it anymore.
Your only solutions would be to either update your python
installation, or run an older version of matplotlib that was still
2.2-compatible (but I don't know what that would be).

Regards,

f

Jules,
>
> ff = P.Figure(figsize=(5,4), dpi=100)
> ss = P.subplot(222)
> pp = ss.plot(x,y,'.-')
>
> # some program resets x,y limits
> P.show()
> #-----

> Is there any way to
> - find the axes objects that count "ff" as their parent?

The `figure` associated with a subplot object `ss` is `ss.figure`
The list of axes objects associated with a figure `ff` is ff.axes.
So, you should be able to access the subplots as 
ss.figure.axes


> - access the x,y points as "children" of the axes object ss?
Try something like
pp.get_xdata(), pp.get_ydata()
where pp is the output of ss.plot


IMHO, it'd be easier to go:
ff = P.figure()
ss = ff.add_subplot(222)
pp = ss.plot(x,y,'.-')

You can check that id(ff.axes[0])==id(ss)

Now, if you have several subplots in the same figure, with one line per 
subplot, you should consider creating a list where you'd store the output of 
subplot.plot. That way, you'd just have to parse the list to recvoer the 
xdata and ydata
For example
ff = P.figure()
plotlines = []
ss = ff.add_subplot(222)
plotlines.append(ss.plot(x,y))

Hello all

My specific question is this:

Suppose I have a figure, with an axes object, and an XY plot:

#-------
import matplotlib
import pylab as P

t = P.arange(0.0,1.0,0.02)
x = P.sin(2*P.pi*t)
y = P.exp(-t*3.)*P.cos(3*P.pi*t)

ff = P.Figure(figsize=(5,4), dpi=100)
ss = P.subplot(222)
pp = ss.plot(x,y,'.-')

# some program resets x,y limits
P.show()
#-----

(Sorry for my matlab-tainted language):

I would like to use ff.gca() to get the handle of the
active axes object (which should be ss) and then
determine the indices into the original data (x,y)
which reflect the points showing in the current
axis limits (whatever they have been set to)

Is there any way to
- find the axes objects that count "ff" as their parent?
- access the x,y points as "children" of the axes object ss?

I may be approaching my larger goal the wrong way,
but I am still interested in this question.

Thanks,
Jules

Hi,
  I have some confusion about ion/ioff, draw() and show().  After
drawing a figure I need to make it show up on the screen without
calling show() and entering the main loop. Here's the code that works:
ion()
l = plot(arange(10),2.*arange(10))
draw()
raw_input('pause')

However, if I remove ion() or place ion() after the plot() or draw()
commands, no figure is shown on the screen. This sucks because any
operation after ion() will be significantly slowed down before a call
to ioff(). I'm not sure if it's a bug that draw() does not update the
screen in ioff() mode.

Any tips?
Zhang Le