Page MenuHomePhabricator

LevelWindow Option "use whole Image grayvalues" doesn't behave as expected
Closed, ResolvedPublic

Description

This can be observed when an Image with very few grayvalues (ramp.tif for example). The Option "use whole Image grayvalues" sets the levelwindow minimun over the lowest value of the image, and the maximum under the highest grayvalue.

Event Timeline

If this behavior is intentional, we can set the bug to invalid. Otherwise, we can discuss it.

This behavior is very uncomfortable when visualizing an image with only a few different values, for example an otsu segmentation with >1 thresholds.

I would like to fix it, but I still need confirmation if this is intentional or not.

I suggest two new options for the context menu of the level window:

  1. "Use whole image grey values" which uses the minimum and the maximum value of the image to set the level window
  1. "contrast maximization" which uses quantiles to calculate the window, just like it does now for the "default level window"

Current release is finished. Resetting target milestone

User kolbch has pushed new remote branch:

bug-13970-AddLevelWindowOptionToUseWholeImageRange

mitkLevelWindow:

  • added method SetToImageRange which sets the levelwindow to the min/max greyvalue of an image.

added context menue item for the QmitkLevelWindow "Use optimized levelwindow" which calls the old SetAuto method.
The old menue item "Use whole image grey values" calls SetToImageRange.

Not sure if this should still go into the release- > Core + , Release ?

I do not see it breaking anything and it would result in stuff behaving as expected, so I'd vote for yes.

[0e2d35]: Merge branch 'bug-13970-AddLevelWindowOptionToUseWholeImageRange'

Merged commits:

2015-04-07 20:40:03 Christoph Kolb [f5bd35]
add contextmenue item "Use optimized levelwindow"
add function for acutally using whole image value range