Helge, Helge Avlesen wrote: > On 6/9/06, Eric Firing <[EMAIL PROTECTED]> wrote: > >>Suggestions for improvements in the API or other aspects are welcome. > > > Hi, > an option for quiver to quickly draw thousands of simple monocolor > arrows each constructed from e.g. 3 line segments would be useful for > someone(like me) that uses matplotlib > for browsing vector plots of large fields (e.g. 800x600). currently > this is not practical > with any of the quiver variants, as it takes minutes to render. I > already use linecollections > to draw high res coastlines, so a faster quiver should be feasible.
I have made some changes to facilitate this, but I have not tried to implement it yet. It should be possible with only a little bit more code than is in quiver.py at present, but it may require figuring out a trick or two. I don't want to work on it quite yet, but it does seem like a good idea--provided rendering LineCollections really is much faster than rendering PolyCollections. > > another optimization could be perhaps be to arrange for numpy arrays > to be passed directly to the drawing methods instead of the all the > zipping and loops that currently are necessary? > Quite some time ago I asked John about this, and the answer was that all this conversion overhead is probably not a large part of the total plotting time, so optimizing it may not be worth the trouble. But I agree--it would seem much more natural to pass X and Y arrays around than to have to zip them into sequences of (x,y) tuples. Eric _______________________________________________ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
