Difference between revisions of "Multi Label Segmentation"
Jump to navigation
Jump to search
(username removed) |
(username removed) |
||
| Line 14: | Line 14: | ||
* what is not possible or cumbersome and should be changed? | * 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? | * 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, so will be its neighbors | ||
| + | ** "background" label should be created by default, and should also be possible to lock it | ||
* useful resources: | * useful resources: | ||
** vtkEdge paintbrush classes e.g. http://www.vtkedge.org/doc/nightly/html/classvtkKWEPaintbrushMergeSketches.html#_details | ** vtkEdge paintbrush classes e.g. http://www.vtkedge.org/doc/nightly/html/classvtkKWEPaintbrushMergeSketches.html#_details | ||
Revision as of 11:36, 26 January 2011
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 byts, 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, so will be its neighbors
- "background" label should be created by default, and should also be possible to lock it
- useful resources:
- vtkEdge paintbrush classes e.g. http://www.vtkedge.org/doc/nightly/html/classvtkKWEPaintbrushMergeSketches.html#_details
- itkSnap http://www.itksnap.org/pmwiki/pmwiki.php
- to support multi-label images, ITK's label object classes (http://www.insight-journal.org/browse/publication/176) could be useful
- Segmentation module in Amira (as it used to be in v3.1)http://www.amira.com/images/stories/pdf/31/Amira31-manual.pdf (see Sec. 2.5)
- how does I/O work?
- do we need a new data type for MITK (derived from BaseData?)
- how could these be mapped types for rendering?
Implications on the implementation
- what parts of MITK would need to be changed?
- what needs to be changed in the Segmentation view?