Measure and graph subpackages

[Tony Yu]

On Sun, Dec 11, 2011 at 12:46 PM, Zachary Pincus <zachary.pincus at yale.edu>wrote:

> Stéfan may be able to amplify, but IIRC he has some other code to put into
> measure that should more clearly differentiate the two sub-modules. Right
> now it's correct that both the content in 'measure' (marching-squares
> contour-finding) and in 'graph' (Dijkstra's algorithm on a lattice) are
> both about tracing paths through pixel arrays, albeit in very different
> contexts. So it might not be bad to re-organize.
>
> But contour-finding is not a graph operation, so such a re-org should be
> more than putting that code in the 'graph' package.
>
> Zach
>

Oh, I meant the other way around: getting the minimum-cost path seems like
something you measure in an image. (Sort of.) That was under the assumption
that nothing else was planned for the graph package.

-Tony
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/scikit-image/attachments/20111211/d10b5935/attachment.html>