functions of ndimage

[Nelle Varoquaux]

>
> I'm in the middle on this: I would suggest importing the relevant ndimage
> functions into the skimage namespace, but not touching the API, except
> perhaps in extremely egregious cases. Just as the lack of a Gaussian filter
> might confuse beginners, two divergent APIs will confuse advanced users.
>

I don't agree with this point: if you take the case of scikit-learn, there
are some methods from scipy wrapped in scikit-learn, where the API changed
to match the scikits (all classifiers are classes, with a fit method, a
predict method, etc). The API of methods in skimage should match skimage's
API, not scipy's.


>
> On Wed, Apr 24, 2013 at 11:41 AM, abid rahman <abidrahman2 at gmail.com>wrote:
>
>> 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 at sun.ac.za>wrote:
>>
>>> On Tue, Apr 23, 2013 at 11:49 PM, Emmanuelle Gouillart
>>> <emmanuelle.gouillart at 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 at googlegroups.com.
>>> For more options, visit https://groups.google.com/groups/opt_out.
>>>
>>>
>>>
>>  --
>> 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 at googlegroups.com.
>> For more options, visit https://groups.google.com/groups/opt_out.
>>
>>
>>
>
>  --
> 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 at googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/scikit-image/attachments/20130424/4476bdc3/attachment.html>