matplotlib-users Mailing List for matplotlib

hi folks !
I'm working now quite a while with the matplotlib, also in the animated case
of plot_date and imshow charts.
Now I should use a vertical line (fixed to a plot_date plot, not to the
axis!) 
and I thought about using vlines as before.
But I have troubles to use the set_array method after the vlines are
created.
Does anybody know the exact array shape and content ?
After I pass any possible combination to the set_array method, the
esablished lines turn gray (from green like they were construgted). They
also don't change the location as desired (they stay fix)
It isn't a problem of canvas redrawing, also autoscale() doesn't help (as it
helped me with animated imshow).
Does anyone have experiance with animated vlines ? eg a working code example
?
Thank you in advance, 
Cheers
-- 
View this message in context: http://www.nabble.com/vlines-animation-problem-tp20672134p20672134.html
Sent from the matplotlib - users mailing list archive at Nabble.com.

Can you be more specific about what you would like to know? I'm happy 
to help.
Mike
Ron Brennan wrote:
> Hello,
>
> Does anyone know where I can find some histogram examples. The ones 
> with the documentation are not as self-explanatory as I would have liked.
>
> I'm not a mathematician and I am struggling to understand the math 
> behind the magic.
>
> Can anyone help?
>
> Thanks,
> Ron
> ------------------------------------------------------------------------
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
> Build the coolest Linux based applications with Moblin SDK & win great prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> ------------------------------------------------------------------------
>
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
> 
-- 
Michael Droettboom
Science Software Branch
Operations and Engineering Division
Space Telescope Science Institute
Operated by AURA for NASA

>
> What if I wanted one legend with both entries in it, rather than two
> separate legends with a different entry in each? Is that possible? That's
> more desirable than two separate legends.
>
Check
http://www.nabble.com/displaying-a-legend-from-a-different-subplot-td18447966.html#a18447966
The legend() function lets you explicitly set what items you want to
show, regardless which axes they are from.
-JJ

On 2008年11月23日 16:48:59 -0800
Zane Selvans <za...@id...> wrote:
> Incidentally, when you do it with ax.plot() instead you can see more 
> easily that the corners where the two sinusoidal functions intersect 
> are getting kind of chopped off by the polygon filling. Don't know if 
> there's an easy way to fix that - maybe by forcing the list of polygon 
> vertices to always explicitly include the points of intersection 
> between the functions being filled_between? Or maybe just by 
> increasing the number of vertices, though I assume that would slow 
> things down.
Some time back, I wrote code to generate a fairly complex polyfill in
a plot in R, 
http://www.oplnk.net/~ajackson/weather/Temperature_2000.png
The key bit of code to find the intersections between all the curves
to fill the corners correctly is here (note that this is "R" code):
intersect <- function(a, b, c, d) {
 # test two line segments for intersection.
 # modified from segseg in "Computational Geometry in C" 
 # by Joseph O'Rourke
 p = c(0,0)
 denom = a[1] * ( d[2] - c[2] ) +
 b[1] * ( c[2] - d[2] ) +
 d[1] * ( b[2] - a[2] ) +
 c[1] * ( a[2] - b[2] );
 # If denom is zero, then segments are parallel: handle separately. 
 if (abs(denom) <= 1.0e-10) {
 return (c(p,0)) 
 }
 num = a[1] * ( d[2] - c[2] ) +
 c[1] * ( a[2] - d[2] ) +
 d[1] * ( c[2] - a[2] );
 if ( (num == 0.0) || (num == denom) ) code = 0;
 s = num / denom;
 num = -( a[1] * ( c[2] - b[2] ) +
 b[1] * ( a[2] - c[2] ) +
 c[1] * ( b[2] - a[2] ) );
 if ( (num == 0.0) || (num == denom) ) code = 0;
 t = num / denom;
 if ( (0.0 < s) && (s < 1.0) &&
 (0.0 < t) && (t < 1.0) ) {
 code = 1;
 }
 else if ( (0.0 > s) || (s > 1.0) ||
 (0.0 > t) || (t > 1.0) ) {
 code = 0;
 }
 p[1] = a[1] + s * ( b[1] - a[1] );
 p[2] = a[2] + s * ( b[2] - a[2] );
 c(p,code);
}
# Intersect two lines defined by a series of segments. Assume the
# lines have common x-values and differ only in y
# intersect is array of (x,y) values
intersect.lines <- function (y1,y2,x) {
 intersect = array(data = NA, dim = c(2,0), dimnames = NULL)
 for (i in 2:length(x)) {
 a = c(x[i-1], y1[i-1])
 b = c(x[i], y1[i])
 c = c(x[i-1], y2[i-1])
 d = c(x[i], y2[i])
 foo = intersect(a,b,c,d)
 if (foo[3]) {
 intersect = cbind(intersect, foo[1:2])
 }
 }
 intersect
}
-- 
-----------------------------------------------------------------------
| 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 |
-----------------------------------------------------------------------

Jeff Whitaker wrote:
> 
> Jeremy Conlin wrote:
>>
>>
>> Thanks for that information, that is what I needed. But now I come up 
>> with a separate problem. I have the following in my code:
>>
>> pylab.plot(n, S, 'b.', label='x')
>> pylab.legend()
>> ax2 = pylab.twinx()
>> pylab.plot(n, mean, 'r',label="mean")
>> ax2.yaxis.tick_right()
>> pylab.legend()
>>
>> Both plots are shown with the appropriate axes, but only the second 
>> plot is listed in the legend. If I only have the first, then only the 
>> first plot will be listed. Please help.
>>
>> Jeremy 
> Jeremy: The problem is that the legends are plotting on top of each 
> other. Try using 'loc=1' for the first one and 'loc=2' for the second
> one.
> 
What if I wanted one legend with both entries in it, rather than two
separate legends with a different entry in each? Is that possible? That's
more desirable than two separate legends.
JDO
-- 
View this message in context: http://www.nabble.com/Two-questions-regarding-axis-scaling-tp19463338p20654006.html
Sent from the matplotlib - users mailing list archive at Nabble.com.

> Either way, it's
> pretty straightforward; just change one line in the Python Makefile
> and matplotlib will install with a simple "sudo python setup.py
> install"
Huh, well there was a make target for Leopard that had that fixed 
CFLAGS that you suggested, and it seemed to build and install without 
any major complaints. If I rename the Matplotlib directory that was 
installed by the SciPy superpack, and try to fire up ipython -pylab, 
it seems to work! Woo hoo!
It looks like there's a tiny doc bug here: http://matplotlib.sourceforge.net/examples/pylab_examples/fill_between.html
ax = fig.add_subplot(111)
ax1.plot(x, y1, x, y2, color='black')
ax.fill_between(x, y1, y2, where=y2>y1, facecolor='green')
ax.fill_between(x, y1, y2, where=y2<=y1, facecolor='red')
ax.set_title('fill between where')
It should be calling ax.plot() not ax1.plot()
Incidentally, when you do it with ax.plot() instead you can see more 
easily that the corners where the two sinusoidal functions intersect 
are getting kind of chopped off by the polygon filling. Don't know if 
there's an easy way to fix that - maybe by forcing the list of polygon 
vertices to always explicitly include the points of intersection 
between the functions being filled_between? Or maybe just by 
increasing the number of vertices, though I assume that would slow 
things down.
--
Zane Selvans
Amateur Earthling
za...@id...
303/815-6866
http://zaneselvans.org
PGP Key: 55E0815F