On a float image, commencing binary threshold segmentation leads to a band-pass segmentation other than the expected binary thresholding. Example image attached.
Description
Description
| Status | Assigned | Task | ||
|---|---|---|---|---|
| Resolved | None | T19250 Binary threshold tool produces unexpected results on float images. | ||
| Resolved | None | T14652 Level window is nearly unusable if the image range is very small |
Event Timeline
Comment Actions
The segmentation result appears to be valid, but the preview is faulty in the given case. This seems to be strongly related to T14652, as a very small level window range is being set in the binary threshold tool on threshold changes.
Comment Actions
I don't think that this bug is related to T14652. Although 14652 helped to detect this bug, it contains rather cosmetic changes and does not influence the rendering behaviour.
I still leave the block, because this bug will be easier to fix and i will merge the solution for 14652 soon.
Comment Actions
For both bugs, small level window ranges are problematic. Dependency can be upheld until there is further clarity on 14652.
Comment Actions
Tobi what is the status of this bug. Is it possible to fix it for the upcoming release?
Comment Actions
[0561cb]: Merge branch 'bug-19250-BinaryThresholdFloatImages'
Merged commits:
2016-02-10 17:02:37 Stefan Kislinskiy [08a0da]
Increased level window range for binary threshold preview
Comment Actions
Kind of fixed this bug by increasing the level window range for the binary threshold preview. Might not work anymore for images with lots of different values in between a really tiny range [0, 0.1].