Multi Label Segmentation

From mitk.org
Revision as of 10:38, 29 January 2011 by (username removed)
Jump to navigation Jump to search


Using multiple segmentations with the Segmentation bundle

Following a proposal of Sebastian Ordas to support multi-label segmentations, this page will be used to sketch future changes to the Segmentation bundle and the related framework.

Shortcomings of the current implementation

  • 8-bit images are used for segmentations by default, wasting 7 of 8 bits, occupying far more memory than technically necessary

Wishlist

  • what is not possible or cumbersome and should be changed?
    • multiple labels on the same segmentation image: have 8-bit images with 0 value as background and the remaining 255 values as labeled objects.
  • what enhancements would help in which situations?
    • have label "lock"/"editable" boolean property
    • "stick" label boundaries to neighboring labels: e.g. if the label is smoothed or dilated, so will be its neighbors. If the label is eroded, the "sticked" neighbors will grow into the space left by the eroded label.
    • "background" label should be created by default, and should also be possible to lock

it

Implications on the implementation

  • what parts of MITK would need to be changed?
  • what needs to be changed in the Segmentation view?
    • new controls:
      • label manager widget ( e.g. have a QmitkDataStorageTable): should easily allow to (multiple) select labels for visualization or editing/locking toggling, change their representation (filled or border line), enable volume render feedback, etc.
  • avoid connection with Data Manager for data selection (IMHO: the current working/reference node selection approach via the DataManager is not user friendly, because the segmentation bundle requires a lot of data (multiple) selection and deselection)

Proposed working plan

  • Stage 1: add lock/edit feature to the current approach
  • For every mitk::Tool, upon finish editing (e.g. mouse release), correct the feedback image for every intersection with other editable/locked segmentations
    • The Segmentation Interpolation should also respect other locked and editable labels
  • Stage 2: do not use binary images any more
  • Stage 3: