[scikit-image] Refactoring ndimage

[Egor Panfilov]

Hi Jaime,

Very nice to hear that there is a major improvement to `scipy` on its way
:).

Regarding your questions:
- Typically, our `master` branch is pretty stable, and we're fixing the
arising bugs as fast as possible, so you might rely on our CI to be green.
>From my point of view, `skimage` could be a good place to host more or less
domain-specific tests, although I'm not really sure what does specificity
mean in case of `ndimage`: convolutions, rescaling, interpolation, basic
filtering are pretty generic;
- Please, also notice that we've recently switched from `nose` to `pytest`
(thanks to Nelle ;)), and any new tests should not have `nose` dependency;
- Not sure that I'll find enough time to contribute to the code by myself,
but it won't harm if you could provide to the public some directions on
where to start with `scipy.ndimage` C-code.

Keep up the great work, and best of luck! :)

Regards,
Egor Panfilov

2017-06-26 12:30 GMT+03:00 Jaime Fernández del Río <jaime.frio at gmail.com>:

> Hi all,
>
> I have started working on an ambitious refactor of scipy.ndimage. Some
> more context on what I would like to achieve can be found here
> <https://mail.python.org/pipermail/scipy-dev/2017-June/021986.html>.
>
> scikit-image is probably the biggest "customer" of ndimage, so even though
> the API and performance are not expected to change, you may want to have a
> say.
>
> Assuming there is no major concern with the overall plan, I would also
> like to poke this community for help with:
>
>    - figuring out a sensible test strategy: Ralf Gommers points out that
>    we should probably use scikit-image's test suite regularly to complement
>    the relatively few tests currently in ndimage: is the development version
>    of scikit-image stable enough for this purpose or do you suggest using a
>    specific stable release? Any other ideas?
>    - PR reviewing. The idea is to make this refactor as incremental as
>    possible. That means many smaller interdependent PRs. Even if you don't
>    have commit rights to the scipy repository you are probably better versed
>    than most of us in image processing algorithms, so if anyone can keep an
>    eye on ndimage PRs
>    <https://github.com/scipy/scipy/pulls?q=is%3Apr+is%3Aopen+label%3Ascipy.ndimage>
>    and provide occasional reviews it would be greatly appreciated.
>    - expert consulting: some of the code in ndimage is pretty hard to
>    understand, e.g. I struggle with spline interpolation. If anyone with the
>    proper academic knowledge is willing to answer stupid questions, please let
>    me know.
>    - the refactoring itself: if anyone would like to be a part of this,
>    it would be my pleasure! A basic command of the C language is needed, but
>    I'm more than willing to mentor beginners.
>
> Thanks!
>
> Jaime
>
> --
> (\__/)
> ( O.o)
> ( > <) Este es Conejo. Copia a Conejo en tu firma y ayúdale en sus planes
> de dominación mundial.
>
> _______________________________________________
> scikit-image mailing list
> scikit-image at python.org
> https://mail.python.org/mailman/listinfo/scikit-image
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/scikit-image/attachments/20170627/070d4737/attachment-0001.html>