-
Notifications
You must be signed in to change notification settings - Fork 150
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
Could regmax also work on float arrays? #47
Comments
You are right. There is no reason for this function to not work with |
I think the same issue affects |
Yes, you are right on watershed again. The implementation currently has Adapting the code is actually fairly trivial. Are you available for |
Not until the end of the month, but after that, yes. |
Hi, any news on that topic? I can help with testing now. |
There is no reason to restrict it to integers. The problem and code are well-defined for any ordered type. This was requested and discussed as issue #47 on github (not closing as that issue also refers to watershed).
Thanks for the ping. regmax/min now should work for FP images. Watershed is work-in-progress. |
I now added support for watershed too. I did some minimal (smoke) testing [included in unit tests], but I'd appreciate it if you gave it a thorough testing run. |
I looked at the current tests and the best I can think of is to change test_watershed and test_mix_types to also try float entries. Anything else you would suggest? |
If it seems to be working for your data, that's OK. If you do find any issue, just open a report. Thanks. |
Actually, the following seemingly reasonable patch to
|
The |
All's in the title...
regmax
is currently generated usingSAFE_SWITCH_ON_INTEGER_TYPES_OF
and checks for integer-ness of the input; is there any specific reason why it doesn't handle float types?By the way, the docstring of
regmax
doesn't mention this limitation.The text was updated successfully, but these errors were encountered: