-
Notifications
You must be signed in to change notification settings - Fork 65
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[QST] cupyx.skimage.registration #181
Comments
As far as I know, there are no updates in terms of Windows support aside from what is discussed in that issue.
We will probably continue to slowly add things on a case-by-case basis. Much of these are more work to add as they rely on compiled C code that needs to be rewritten for CUDA. A couple of functions we would like to prioritize are We will also at some point update the API of the existing implementations to match the newly released scikit-image 0.19. |
Thanks for your reply @grlee77. My application uses image registration using phase cross correlation. For now I have just added a folder into my repo which users would install manually. Other option would be to add my own forked skimage repository with that module altered for the purposes of my application, but would be nicer to not have to do either of these things and have your package as a requirement. For reference, my docs can be found here. It is version 0.0.1, just getting it off the ground. |
I also need |
same here, distance_transform_edt would be very useful! :P |
Hi @srepmub and @fakedrake, This is now available in release 22.08 and newer via |
Hello, I recently hacked the phase_cross_correlation function in skimage.registration to enable cupy for my particular application.
After that, I found that @grlee77 did something similar but for many of skimage's functions on the cupyimg repo, and that the project had been ported here. Looks like I didn't have to do all that work....
I think it is great what you all are doing here, package looks really nice. Unfortunately, though, for my particular application, I don't want users to have to go through the windows installation process documented here. For the average user, installing cuda is difficult enough.
Are there plans to continue adding cupyx.scipy.ndimage support for the modules not currently on the PR upstream list here?
Thanks again,
Sam
The text was updated successfully, but these errors were encountered: