Hi Devin,

On Fri, 05 Jul 2019 10:53:50 -0400, Devin Crowley wrote:
> The second thing is that our method does not require ITK, a large and
> difficult codebase.  All substantial computations are either interpolation
> or FFT.
> Because of this, we don't rely on any functionality from pytorch other than
> FFT and interpolation, which are both available in scipy.  Pytorch is only
> used because it makes GPU easy.
>
> We'd like to contribute, and we may have a small team of undergraduate
> biomedical engineering students who can contribute starting in the Fall.
> Would reaching out to Juan directly be the best way to get started?

Fantastic!  As others mentioned, we are very interested in this
functionality, and would enjoy working with your team to integrate your
contribution.

You can read more about contributing to scikit-image here:
https://scikit-image.org/docs/stable/contribute.html

The long and short of it is that you can proceed by making one or more
pull requests to the repository, where it will be reviewed by the
development team.  It sometimes takes a while of iterative development
and conversation to get everything into shape, but hopefully since you
already have working code this won't take too long.

Please take a look at the references given by Juan also: we would
appreciate feedback on the registration interfaces proposed.

Best regards,
Stéfan
_______________________________________________
scikit-image mailing list -- scikit-image@python.org
To unsubscribe send an email to scikit-image-leave@python.org