Sanitize Otsu threshold implementation
- Dominant language
- Java
- Stars
- 94
- Forks
- 44
- PR merge metrics
- No merged PRs in 30d
Description
The current implementation "in certain circumstances can cause an overflow".
See the comment by @landinig [here on the forum](https://forum.image.sc/t/otsus-threshold-method-delivers-different-results-in-scikit-image-and-imagej/24655/18?u=imagejan), and this commit: https://github.com/fiji/Auto_Threshold/commit/cd9684592ef0d7eebddcc118fa4a8a4387fdfe4f.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating the Otsu threshold implementation and reviewing the linked forum comment and Fiji Auto_Threshold commit. Reproduce the overflow scenario and compare the implementation's results with the referenced behavior. Done means the threshold calculation no longer overflows in those circumstances and existing behavior remains covered by tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- computer-vision
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100