Confusing behavior for histogram
- Dominant language
- Java
- Stars
- 94
- Forks
- 44
- PR merge metrics
- No merged PRs in 30d
Description
Regarding [`HistogramCreate`](https://github.com/imagej/imagej-ops/blob/1edfda8cb625ddf56192be0f65fb480f438caec1/src/main/java/net/imagej/ops/image/histogram/HistogramCreate.java)
See this issue on the forum:
https://forum.image.sc/t/histogram1d-not-returning-bin-frequencies-in-order-for-some-images/37918/
1) Add parameters for the min and max.
2) Ensure bin width >= 1 for integer types.
3) Consider default min/max of [0,255] for `UnsignedByteType`
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with src/main/java/net/imagej/ops/image/histogram/HistogramCreate.java and reproduce the cases described in the linked forum issue. Review how histogram bounds and bin widths are currently chosen, then verify each requested behavior: configurable min/max, integer bin widths of at least 1, and the proposed UnsignedByteType defaults. Done means the confusing frequency ordering is addressed and the changed behavior is covered by verification for the affected image types.
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
- Mostly clear
- Newbie friendliness
- 35/100