Eric-

I had a chance to play around with the new quiver this morning.  Here  
are some thoughts:

1. I read that somebody thought it was a bit slow, but this is not my  
experience.  I tried to quiver my model data (128x128 with masking),  
and it rendered in a few seconds.  I tried to look at images with  
more arrows, but I could not actually see the arrows with so many  
points.  In my experience you can't put more than about O(100000)  
(i.e., about 100x100) arrows on a figure and have it make any sense  
anyways.

2.  It seems to handle masking fine.  I gave it masked arrays and  
arrays with nans (it complained a bit about the masked array, but  
rendered anyways).  This is key for me.

3.  It handles colors nicely, but there is no apparent way to set the  
color limits. Perhaps adding vmin and vmax as kwargs (matching  
pcolor) would make some sense.

4.  I *really* like how the arrows get gray (and don't try to render  
at a whole pixel) when they get small.  I agree with the other person  
that it might be nice to have a  small dot to indicate zero  
velocity.  No dot should be rendered *ever* for values masked or  
NaNed, however.

5. It's a bit of a pain to find values of scale and width that work  
well, and quiver doesn't seem to make very good choices by default.   
I don't think this is a big deal, but rather simply the price of the  
added functionality.  Making some more intelligent default choices  
might not be a bad idea, though.  In particular, smaller arrows when  
there are more arrows to be rendered would be a good place to start.

Some ideas for future work:

1. I'm pretty happy with the polygons, but it would be nice to have  
line collections instead.  This would also facilitate my next idea:

2. I would love to have a 'curly vector' tool.  However, I'm not sure  
how much to put into the curly_quiver package, and how much work must  
be done by the user.  I think that at a minimum, it would be nice to  
give curly lines (i.e., an additional dimension to u and v)that have  
arrows on the end of them, and leave it to the user to define what  
those lines are somehow.  If these lines could change color along  
their track, then it would be the best thing ever made!

-Rob.

-----
Rob Hetland, Assistant Professor
Dept of Oceanography, Texas A&M University
p: 979-458-0096, f: 979-845-6331
e: [EMAIL PROTECTED], w: http://pong.tamu.edu



_______________________________________________
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

Reply via email to