Hi, Isn't it a bad idea that for some functions we should go for scipy, for some other functions we go for skimage. Actually what I felt from user-point-of-view is to decrease maximum dependency in the project. So it is always better to bring all image processing stuffs in python under one library. Installation of one library should serve all our purpose. Abid K. opencvpython.blogspot.com On Wed, Apr 24, 2013 at 3:49 AM, Stéfan van der Walt <stefan@sun.ac.za>wrote:

On Tue, Apr 23, 2013 at 11:49 PM, Emmanuelle Gouillart <emmanuelle.gouillart@nsup.org> wrote:

...

I can see only a small number of scipy.ndimage functions that are concerned, like gaussian_filter, distance_transform_edt, binary_fill_holes, but I now think that it'd be worth having a wrapper for these functions in skimage, for the sake of users not well aware of scipy.ndimage. We already depend on scipy anyway.

I'd be happy to put wrappers to those functions in skimage, as long as we do a thorough review of the API of each. That turns out to be one of skimage's strongest benefits, and we shouldn't rely on ndimage to have considered it very carefully. I think it would help if we had some practical use cases of each of these, to guide us in the right direction.

But yes, I can see how this would confuse beginners...

Stéfan

-- You received this message because you are subscribed to the Google Groups "scikit-image" group. To unsubscribe from this group and stop receiving emails from it, send an email to scikit-image+unsubscribe@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.