Hello again Alberto,
On 4 July Alberto Azevedo wrote:
> When I use the triplot function with 100-1000 points it works well. The
> problem is that in my work I often use grids with 30000-100000
> points. With those grids triplot takes a long time to compute (I never
> wait for the results, it takes really a long time).
>
Yes, it does indeed take a long time for large grids. The bottleneck is line
51 in lib/matplotlib/tri/triplot - I use the plot command which creates a
separate Line2D object for each edge in the triangulation, and there can be
a lot of edges. There is an obvious improvement of replacing this with a
single LineCollection object, but it would require some manipulation of the
line styles, colours, etc that the plot command does and I don't yet
understand it sufficiently.
The matlab triplot function takes just a few seconds, with the same
> grids).
It's bad etiquette to indicate that matlab is faster when addressing people
who give up their free time to improve matplotlib, and possibly
counter-productive.
And when I was using mpl_tri package, I never had this problem
> (the triplot function was faster!!!)
>
Not true, the final line in the now obsolete mpl_tri.triplot was exactly the
same plot() command.
I'll take a look at improving the performance, but it won't for a few days.
Ian
------------------------------------------------------------------------------
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
_______________________________________________
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
