matplotlib-users Mailing List for matplotlib (Page 2)

On Thu, 2005年09月29日 at 09:01 -0500, Charlie Moad wrote:
> Shouldn't quiver be able to handle zero length vectors?
> 
The way I handle this is to add an extremely small value to one of the
vectors.
i.e. 
quiver(x+1e-15,x)
This should provide a workaround.
I think the issue lies in this snippet of code in the quiver function:
around line 855 or so in axes.py
N = sqrt( U**2+V**2 )
if do_scale:
	Nmax = maximum.reduce(maximum.reduce(N))
	U *= (S/Nmax)
	V *= (S/Nmax)
	N /= Nmax
No provision is made for the case where N is the zero vector. 
Hope it helps.
John
--
John Byrnes (by...@bu...)
Graduate Student
Electrical Engineering
Boston University
The best way to cheer yourself is to try to cheer someone else up.
		-- Mark Twain

I thought this was fixed about 2 months ago.
Do you have the latest version?
Mark
From: Yannick Copin <yan...@la...>
Hi,
I have a bug when I want to turn off the tick labels on subplots where
upper limits reaches 10000: the "magnitude" string (x1e4) doesn't get
erased. Example:

Hello everyone,
Hello John,
I'm thinking about this fastplot-routine for a while now. Before hacking all
the lines.py-code I wanted to ask you about your thoughts. Just to repeate a
bit:
I changed the previously sent fastplot.py (I'll call it 'plot_points()' from
now on) a bit: Now it is possible to draw multiple markers with one call.
But all at all it looks like the version sent before.
What you John asked for, was a unification with lines.py. Taking for example
triangle_down in lines.py one can read:
 def _draw_triangle_down(self, renderer, gc, xt, yt):
 offset = 0.5*renderer.points_to_pixels(self._markersize)
 rgbFace = self._get_rgb_face()
 if self._newstyle:
 path = agg.path_storage()
 path.move_to(-offset, offset)
 path.line_to(offset, offset)
 path.line_to(0, -offset)
 path.end_poly()
 renderer.draw_markers(gc, path, rgbFace, xt, yt, self._transform)
 else:
 for (x,y) in zip(xt, yt):
 verts = ( (x-offset, y+offset),
 (x+offset, y+offset),
 (x, y-offset))
 renderer.draw_polygon(gc, rgbFace, verts)
I would like to ask you (right before I'll mess everything up ;) if all this
at least could work: 
What I would try for unification is writing the dictionary 'markerd' in
lines.py (I'd prefer it right in front of 'class Line2D' as global - but
there it isn't readable for a program later, isn't it?) and change the
functions a bit like:
 def _make_triangle_down(size):
 return reshape([[0, -size, size],
 [1, size, size],
 [1, 0, -size]], (3,3))
 def _make_x(size):
 return reshape([[0, -size, -size],
 [1, size, size],
 [0, 0, 0],
 [1, size, -size],
 [1, -size, size],
 [0, 0, 0]], (6,3))
 
and so on ...
Then I would try to let the newstyle & oldstyle ploting-method use those
functions by writing a (for all markers usable) function:
def _draw_marker(self, marker, renderer, gc, xt, yt):
 func = markerd[marker]
 verts = func(1.0*renderer.points_to_pixels(int(msize)))
 rgbFace = self._get_rgb_face()
 if self._newstyle:
 path = agg.path_storage()
 for v in verts.tolist():
 if v[0]:
 path.line_to(v[1], v[2])
 if else:
 path.move_to(v[1], v[2])
 path.end_poly()
 renderer.draw_markers(gc, path, rgbFace, xt, yt, self._transform)
 else:
 for (x,y) in zip(xt, yt):
 vertices = []
 for v in verts:
 vertices.append((x+v[1], y+v[2]))
 renderer.draw_polygon(gc, rgbFace, tuple(vertices))
 # notice: some markers are partially drawn double (e.g x)
Then the plot_points-routine would contain a differing line:
 verts = func(1.0*renderer.points_to_pixels(int(msize)))[:,1:3]
All this I already tried a bit but somehow failed (I quess mainly due to
variables not beeing defined). A way out of this would be knitting those
functions into the class Line2D (it would be pretty easy to define
everything there). But than I could have used Line2D from the beginning,
couldn't I? So - to cut the long story short - where would you (if ever) add
those new lines to the code?
Another question would be: Are those new for-loops in _draw_marker() too
annoying (in the sense of speed)? (I quess they are vital for the
_make_triangle_down()-like functions to keep their simple form so that they
can be used by plot and plot_points together.)
Best regards,
Martin
-- 
Lust, ein paar Euro nebenbei zu verdienen? Ohne Kosten, ohne Risiko!
Satte Provisionen für GMX Partner: http://www.gmx.net/de/go/partner

Shouldn't quiver be able to handle zero length vectors?
x =3D zeros((2,2),typecode=3D'f')
quiver(x,x)
This yields a ZeroDivisionError.
Also, is there an easy way to do a flipy for imshow?
Thanks,
 Charlie

>>>>> "Jonathan" == Jonathan Taylor <jon...@st...> writes:
 Jonathan> hi all, figured out the answer to my last post after
 Jonathan> all. apologies.
Please share :-) Even though you may now think it is obvious, it is
still not obvious to many people. A post or a wiki entry would be
much obliged.
Thanks,
JDH

hi all,
figured out the answer to my last post after all. apologies.
jonathan
-- 
Jonathan Taylor Tel: 650.723.9230
Dept. of Statistics Fax: 650.725.8977
Sequoia Hall, 137 www-stat.stanford.edu/~jtaylo
390 Serra Mall
Stanford, CA 94305 

hi all,
i have an application for which i want to use imshow to display an image
that is not very square (91x109 aspect ratio). one way to do it would be
to place it as close to the middle as possible (having different border
widths in x and y scale), but i prefer to put an even border around the
entire image. i can't seem to figure out how to automatically resize the
plotting window.
any suggestions?
thanks,
jonathan 
-- 
Jonathan Taylor Tel: 650.723.9230
Dept. of Statistics Fax: 650.725.8977
Sequoia Hall, 137 www-stat.stanford.edu/~jtaylo
390 Serra Mall
Stanford, CA 94305 

I am on my computer at home and can't recreate my problem. I don't know 
what I did wrong last night. I could still use help though on the 
legend refresh stuff in my other message.
Ryan Krauss wrote:
> This morning on my office computer I don't seem to have the same 
> problem. (I will see if I can recreate my problem on my laptop at home 
> later.)
> 
> I do have one new problem though. After adding the second plot, I need 
> to refresh the legend of the first plot because the plot on twinx wrote 
> over it. Any calls to legend seem to be working with the lines that are 
> drawn on twinx. I could avoid this problem and make a slightly nicer 
> looking plot if I could first draw on the twinx axis (with the y-axis 
> ticks on the right) and then draw on the "normal" axis (with the y-axis 
> ticks and label on the left). Is this possible?
> 
> And can I make one legend that includes the plots from both axes?
> 
> Thanks for your help John. I think I am getting close to a really nice 
> graph with a lot of useful information on it.
> 
> Ryan
> 
> 
> 
> John Hunter wrote:
> 
>>>>>>> "Ryan" == Ryan Krauss <rya...@co...> writes:
>>
>>
>>
>>
>> Ryan> It appears that this feature is available through the
>> Ryan> twinx() function according to:
>>
>> Right -- see also examples/two_scales.py
>>
>> Ryan> It seems like once I called the twinx function, the x-axis
>> Ryan> settings that where on the original axis are ignored and I
>> Ryan> can't seem to change the axis settings.
>> Ryan> pylab.axes([0.1,30,0,1]) returned an error: RuntimeError:
>> Ryan> Transformation is not invertible
>>
>> Please post a free-standing, complete example which replicates the
>> bug.
>>
>> Thanks,
>> JDH
>>
>>
>> -------------------------------------------------------
>> This SF.Net email is sponsored by:
>> Power Architecture Resource Center: Free content, downloads, discussions,
>> and more. http://solutions.newsforge.com/ibmarch.tmpl
>> _______________________________________________
>> Matplotlib-users mailing list
>> Mat...@li...
>> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
>>
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by:
> Power Architecture Resource Center: Free content, downloads, discussions,
> and more. http://solutions.newsforge.com/ibmarch.tmpl
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
> 

This morning on my office computer I don't seem to have the same 
problem. (I will see if I can recreate my problem on my laptop at home 
later.)
I do have one new problem though. After adding the second plot, I need 
to refresh the legend of the first plot because the plot on twinx wrote 
over it. Any calls to legend seem to be working with the lines that are 
drawn on twinx. I could avoid this problem and make a slightly nicer 
looking plot if I could first draw on the twinx axis (with the y-axis 
ticks on the right) and then draw on the "normal" axis (with the y-axis 
ticks and label on the left). Is this possible?
And can I make one legend that includes the plots from both axes?
Thanks for your help John. I think I am getting close to a really nice 
graph with a lot of useful information on it.
Ryan
John Hunter wrote:
>>>>>>"Ryan" == Ryan Krauss <rya...@co...> writes:
> 
> 
> 
> Ryan> It appears that this feature is available through the
> Ryan> twinx() function according to:
> 
> Right -- see also examples/two_scales.py
> 
> Ryan> It seems like once I called the twinx function, the x-axis
> Ryan> settings that where on the original axis are ignored and I
> Ryan> can't seem to change the axis settings.
> Ryan> pylab.axes([0.1,30,0,1]) returned an error: RuntimeError:
> Ryan> Transformation is not invertible
> 
> Please post a free-standing, complete example which replicates the
> bug.
> 
> Thanks,
> JDH
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by:
> Power Architecture Resource Center: Free content, downloads, discussions,
> and more. http://solutions.newsforge.com/ibmarch.tmpl
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
> 

Hello Jeff,
we had exactly the same problem and Doug Swesty had the right answer (BTW
thanks for this!) to it:
http://sourceforge.net/mailarchive/message.php?msg_id=12999739
According to this post all you have to do is:
plot1 = gca()
setp(plot1.get_xticklines() + plot1.get_yticklines() , mew=2.0, mec='g')
Bye,
Martin
-- 
Lust, ein paar Euro nebenbei zu verdienen? Ohne Kosten, ohne Risiko!
Satte Provisionen für GMX Partner: http://www.gmx.net/de/go/partner

Hi all,
after upgrading matplotlib to 0.84 (with python 2.4.1) I get the 
following warning message:
> /sw/lib/python2.4/site-packages/matplotlib/backends/backend_gtk.py: 
> 998: GtkWarning: Could not find the icon 'gnome-fs-home'. The 
> 'hicolor' theme
> was not found either, perhaps you need to install it.
> You can get a copy from:
> http://freedesktop.org/Software/icon-theme/releases
> buttons)
AFAICU the message is related to the gnome icons, but I've checked 
and the last avaible version of the gnome icons package is installed 
on my system. Anyone here can help me in fixing this?
Thanks,
 Andrea.

Hi,
I just started to use matplotlib for a small project involving graph 
generation. I'd like you to help me to solve a simple problem: I assign 
to axes values that range from 0 to 100 bilion. The library approximate 
the values to fit correctly the layout, an it places the exponent that 
should be used to retrieve the right value on top of the axes. I need to 
change this behaviour, and I'd like matplotlib to show the full exponent 
(1000 instead of x1e3 for example).
How can I do that?
bye,
Gabriele

>>>>> "Ryan" == Ryan Krauss <rya...@co...> writes:
 Ryan> It appears that this feature is available through the
 Ryan> twinx() function according to:
Right -- see also examples/two_scales.py
 Ryan> It seems like once I called the twinx function, the x-axis
 Ryan> settings that where on the original axis are ignored and I
 Ryan> can't seem to change the axis settings.
 Ryan> pylab.axes([0.1,30,0,1]) returned an error: RuntimeError:
 Ryan> Transformation is not invertible
Please post a free-standing, complete example which replicates the
bug.
Thanks,
JDH

It appears that this feature is available through the twinx() function 
according to:
http://matplotlib.sourceforge.net/faq.html#TWOSCALES
(the link on this page is broken, but I have the file in some examples I 
downloaded from somewhere else on the matplotlib page.)
I created the second plot using:
figure(1)
subplot(211)
ax2=pylab.twinx()
pylab.semilogx(freq,iobode.coh,'k')
It seems like once I called the twinx function, the x-axis settings that 
 where on the original axis are ignored and I can't seem to change the 
axis settings. pylab.axes([0.1,30,0,1]) returned an error: 
RuntimeError: Transformation is not invertible
I tried calling the ax2.set_xlim((0.1,30)) function but it doesn't seem 
to do anything.
Ryan
Ryan Krauss wrote:
> If it helps clarify what I mean, attached is a plot I made in excel (I
> really don't want to use excel). The y-xis on the left goes from -60 to
> 80. The one on the right goes from 0-1.
> 
> Ryan
> 
> Ryan Krauss wrote:
> 
>> Is it possible to overlay two plots with different y-axis limit? I 
>> think excel calls this plotting a data set with a secondary y-axis. I 
>> want to overlay a bode plot with its coherence and the y-axis limits 
>> for the two will be very different. I don't want to plot one above 
>> the other with a subplot, but actually overlay them on the same plot.
>> (and I want to do it on a semilogx).
>>
>> Thanks,
>>
>> Ryan
>>
>>
>> -------------------------------------------------------
>> This SF.Net email is sponsored by:
>> Power Architecture Resource Center: Free content, downloads, discussions,
>> and more. http://solutions.newsforge.com/ibmarch.tmpl
>> _______________________________________________
>> Matplotlib-users mailing list
>> Mat...@li...
>> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
>>
> 
> 
> ------------------------------------------------------------------------
> 

If it helps clarify what I mean, attached is a plot I made in excel (I
really don't want to use excel). The y-xis on the left goes from -60 to
80. The one on the right goes from 0-1.
Ryan
Ryan Krauss wrote:
> Is it possible to overlay two plots with different y-axis limit? I 
> think excel calls this plotting a data set with a secondary y-axis. I 
> want to overlay a bode plot with its coherence and the y-axis limits for 
> the two will be very different. I don't want to plot one above the 
> other with a subplot, but actually overlay them on the same plot.
> (and I want to do it on a semilogx).
> 
> Thanks,
> 
> Ryan
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by:
> Power Architecture Resource Center: Free content, downloads, discussions,
> and more. http://solutions.newsforge.com/ibmarch.tmpl
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
> 

Is it possible to overlay two plots with different y-axis limit? I 
think excel calls this plotting a data set with a secondary y-axis. I 
want to overlay a bode plot with its coherence and the y-axis limits for 
the two will be very different. I don't want to plot one above the 
other with a subplot, but actually overlay them on the same plot.
(and I want to do it on a semilogx).
Thanks,
Ryan

>>>>> "Jeff" == Jeff Peery <jef...@se...> writes:
 Jeff> Is there something for plot() that rotates the axes. I know
 Jeff> I can simply switch the variables like so: plot(x,y) and
 Jeff> plot(y,x), but I have a 1D array and I don't want to add a
 Jeff> second array for the element number. Is there a keyword like
 Jeff> rotate=90 as there is for text? Thanks.
There is no built-in support for rotating axes. If you are averse to
defining your own x array, I suggest writing a helper function
def plot90(y, **kwargs):
 x = arange(len(y), typecode=Float)
 return plot(y, x, **kwargs)
JDH

Is there a reason that anti-aliasing it disabled by default on quiver?
Line 893 of axes.py =3D=3D "antialiaseds =3D (0,),"
quiver looks SO much better when this is enabled. If there is no
opposition I would like to make this default in cvs.
Thanks,
 Charlie

Chris Fonnesbeck wrote:
> I have successfully built and installed wxPython, so that I can use the
> WXAgg backend for matplotlib. Now, trying to build matplotlib, I get the
> following error:
> 
> /usr/bin/g++ -bundle -undefined dynamic_lookup build/temp.darwin-
> 8.2.0-Power_Macintosh-2.4/src/_na_transforms.o
> build/temp.darwin-8.2.0-Power_Macintosh-2.4/src/mplutils.o
> build/temp.darwin-8.2.0-Power_Macintosh-2.4/CXX/cxx_extensions.o
> build/temp.darwin-8.2.0-Power_Macintosh-2.4/CXX/cxxsupport.o
> build/temp.darwin-8.2.0-Power_Macintosh-2.4/CXX/IndirectPythonInterface.o
> build/temp.darwin-8.2.0-Power_Macintosh-2.4/CXX/cxxextensions.o
> -L/usr/local/lib -L/usr/lib -lstdc++ -lm -o
> build/lib.darwin-8.2.0-Power_Macintosh-2.4/matplotlib/_na_transforms.so
> ld: build/temp.darwin-8.2.0-Power_Macintosh-2.4/src/_na_transforms.o
> illegal reference for -dynamic code (section difference reference from
> section (__TEXT,__eh_frame) relocation entry (20) to symbol:
> __ZSt21_Rb_tree_rotate_rightPSt18_Rb_tree_node_baseRS0_ defined in
> dylib: /usr/local/lib/libstdc++.dylib)
> ld: build/temp.darwin-8.2.0-Power_Macintosh-2.4/src/_na_transforms.o
> illegal reference for -dynamic code (section difference reference from
> section (__TEXT,__eh_frame) relocation entry (24) to symbol:
> __ZSt20_Rb_tree_rotate_leftPSt18_Rb_tree_node_baseRS0_ defined in dylib:
> /usr/local/lib/libstdc++.dylib)
> error: command '/usr/bin/g++' failed with exit status 1
> 
> I am using gcc 3.3, and ActivePython 2.4.1.
> 
> Any ideas as to what is going wrong?
Try removing /usr/local/lib from your link path or get rid of
/usr/local/lib/libstdc++.* .
-- 
Robert Kern
rk...@uc...
"In the fields of hell where the grass grows high
 Are the graves of dreams allowed to die."
 -- Richard Harter

Hello, I am trying to change the size and color of tick marks but I'm
having trouble.
 
Here's how I do it:
#tickmark attributes
 
setAttr(axes.xaxis.get_major_ticks(), size=2, color='g', visible=True)
 
 
I get an error indicating that size and color are not keywords. How can
I fix this? Thanks!
 
Jeff
 
 _____ 
Jeffrey Thomas Peery
SeaMetrics, Inc.
Mechanical Engineer 
Jef...@Se...
253.872.0285 (fax)
253.872.0284 (phone)
 _____ 
 

Chris Barker wrote:
> However, what doesn't seem to have any effect is changing the dpi of the 
> Figure. What's up John? shouldn't Figure.set_dpi effect the dpi of the 
> resulting PNG? I'm using MPL 0.83.1 on Linux. I'll go upgrade now, so if 
> this has been fixed, I guess you can ignore it.
FWIW, I just upgraded to 0.84, with exactly the same results.
-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...

Nm, I misread you question. You can get the transform object and
possibly apply a rotation. (e.g. line2d.get_transform() from example).
 I don't know how to manipulate this from the top of my head though.
On 9/27/05, Charlie Moad <cw...@gm...> wrote:
> A pylab approach:
>
> line2d =3D plot(rand(10))[0]
>
> def swap(xdata, ydata):
> line2d.set_xdata(ydata)
> line2d.set_ydata(xdata)
> draw()
>
> swap(line2d.get_xdata(), line2d.get_ydata())
>
>
> On 9/27/05, Jeff Peery <jef...@se...> wrote:
> > Is there something for plot() that rotates the axes. I know I can
> > simply switch the variables like so: plot(x,y) and plot(y,x), but I
> > have a 1D array and I don't want to add a second array for the element
> > number. Is there a keyword like rotate=3D90 as there is for text? Thank=
s.
> >
> > Jeff
> >
> >
> >
> > -------------------------------------------------------
> > This SF.Net email is sponsored by:
> > Power Architecture Resource Center: Free content, downloads, discussion=
s,
> > and more. http://solutions.newsforge.com/ibmarch.tmpl
> > _______________________________________________
> > Matplotlib-users mailing list
> > Mat...@li...
> >
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
> >
>
>

John Hunter wrote:
>>>>>>"Yaroslav" == Yaroslav Bulatov <yar...@gm...> writes:
> Yaroslav> The only unresolved issue is how to make a large image
> Yaroslav> without also make all the lines thick. IE, if I do
> Yaroslav> savefig(dpi=400), I get a large image, but all the lines
> Yaroslav> are extremely thick.
> 
> Hmm, this should not make a difference. Eg, in the following example
> 
> >>> plot([1,2,3])
> >>> savefig('test100', dpi=100)
> >>> savefig('test600', dpi=600)
> 
> The relative linewidths look comparable.
I'm guessing the OP wanted to get an image with more pixels, but NOT 
have the lines be more pixels wide. I think this might help:
There are three parameters define an image size (this is not MPL specific):
Size in length units (inches, cm, pt, etc): i.e. 5"x7"
Size in pixels: i.e. 800x600 pixels
Dots per Inch (dpi) i.e. 100 dpi
Only two of these are independent, so if you define two of them, the 
third can be calculated from the others.
When displaying on a computer screen (or saved to a PNG), the size in 
length units is irrelevant, the pixels are simply displayed. When 
printed, or saved to PS, EPS or PDF (all designed to support printing), 
then the Size or dpi is used to determine how to scale the image.
Now I'm getting into how I think MPL works, but it turns out I'm wrong 
here. See the example below for a test. Note, this John, please correct 
this!
1) The size of a figure is defined in length units (inches), and can be 
set by:
Figure.set_figsize_inches( (w,h) )
2b) The layout of the figure is defined in "figure units" so it can be 
scaled by changing the figure size.
2) Size of text, width of lines, etc is defined in terms of length units 
(points?).
3) When displaying to the screen, or creating an image (PNG) the pixel 
size of text and line widths, etc is determined by the dpi setting, 
which is set by:
Figure.set_dpi( val )
The trick here is that when printing, it's natural to think in terms of 
inches, but when creating an image (for a web page, for instance), it 
is natural to think in terms of pixel size. However, AFAIK, MPL does not 
have a way to set the pixel size directly (remember that you can only 
set two of the three size parameters, the third must be calculated from 
the other two).
So, in the OPs case, I think what is wanted to create a large image in 
terms of pixel size, but not change hoe many pixels wide a line is. In 
theory, you could accomplish that by using:
Figure.set_figsize_inches( (w,h) )
Without changing the dpi. I've done a test case, and this works. 
However, what doesn't seem to have any effect is changing the dpi of the 
Figure. What's up John? shouldn't Figure.set_dpi effect the dpi of the 
resulting PNG? I'm using MPL 0.83.1 on Linux. I'll go upgrade now, so if 
this has been fixed, I guess you can ignore it.
-Chris
Enclosed is a sample script, and below are the results:
using MPL version: 0.83.1
DPI: 80.0
Size in Inches (7.9749999999999996, 5.6624999999999996)
Which should result in a 638 x 453 Image
DPI: 160.0
Size in Inches (7.9749999999999996, 5.6624999999999996)
Which should result in a 1276 x 906 Image
DPI: 160.0
Size in Inches (16.0, 12.0)
Which should result in a 2560 x 1920 Image
DPI: 80.0
Size in Inches (16.0, 12.0)
-- 
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...

A pylab approach:
line2d =3D plot(rand(10))[0]
def swap(xdata, ydata):
line2d.set_xdata(ydata)
line2d.set_ydata(xdata)
draw()
swap(line2d.get_xdata(), line2d.get_ydata())
On 9/27/05, Jeff Peery <jef...@se...> wrote:
>
> Is there something for plot() that rotates the axes. I know I can
> simply switch the variables like so: plot(x,y) and plot(y,x), but I
> have a 1D array and I don't want to add a second array for the element
> number. Is there a keyword like rotate=3D90 as there is for text? Thanks.
>
> Jeff
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by:
> Power Architecture Resource Center: Free content, downloads, discussions,
> and more. http://solutions.newsforge.com/ibmarch.tmpl
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
>

Thanks. Will that work for the WXAgg backend?
 
-----Original Message-----
From: Charlie Moad [mailto:cw...@gm...] 
Sent: Tuesday, September 27, 2005 9:34 AM
To: Jeff Peery
Cc: mat...@li...
Subject: Re: [Matplotlib-users] rotating a plot using 'rotate' keyword?
 
A pylab approach:
line2d = plot(rand(10))[0]
def swap(xdata, ydata):
 line2d.set_xdata(ydata)
 line2d.set_ydata(xdata)
 draw()
swap(line2d.get_xdata(), line2d.get_ydata())
On 9/27/05, Jeff Peery <jef...@se...> wrote: 
Is there something for plot() that rotates the axes. I know I can
simply switch the variables like so: plot(x,y) and plot(y,x), but I 
have a 1D array and I don't want to add a second array for the element
number. Is there a keyword like rotate=90 as there is for text? Thanks.
Jeff
------------------------------------------------------- 
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads,
discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl 
_______________________________________________
Matplotlib-users mailing list
Mat...@li...
https://lists.sourceforge.net/lists/listinfo/matplotlib-users