On 31 January 2014 19:51, Eric Firing <efir...@hawaii.edu> wrote:
> Would the new code be substantially simpler if the blocky capability were
> omitted from it? If so, then it seems like it would makes sense to leave
> the blocky form to the old code.
>
Simpler, yes, but not substantially so. I would prefer to keep both blocky
and corner-cutting algorithms together so that there is only one extension
to maintain when we eventually remove the old code.
One thing to keep in mind is the desire for a cleaner separation between
> the generation of the contours and their plotting. Sometimes one actually
> wants the polygons themselves; for example, topographic contours can be
> used to define boundaries for internal wave flux calculations. A student
> here at UH is doing exactly this.
>
That is certainly desirable, but not part of the work I am doing. I am
rewriting the C/C++ code that calculates the contours, but the interface
between that and the python contour code remains the same, apart from some
trivial changes of course.
Ian
------------------------------------------------------------------------------
Managing the Performance of Cloud-Based Applications
Take advantage of what the Cloud has to offer - Avoid Common Pitfalls.
Read the Whitepaper.
http://pubads.g.doubleclick.net/gampad/clk?id=121051231&iu=/4140/ostg.clktrk
_______________________________________________
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
