Difference between revisions of "Multi Label Segmentation"

From mitk.org
Jump to navigation Jump to search
(username removed)
Line 21: Line 21:
 
* what is not possible or cumbersome and should be changed?
 
* what is not possible or cumbersome and should be changed?
 
* what enhancements would help in which situations?
 
* what enhancements would help in which situations?
 +
* 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
 
* 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?
 
** how does I/O work?
 
** do we need a new data type for MITK (derived from [[BaseData]]?)
 
** do we need a new data type for MITK (derived from [[BaseData]]?)

Revision as of 11:28, 26 January 2011


Using multiple segmentations with the Segmentation bundle

#!wiki caution
This is really just a sketch. Move / change anything


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

Implications on the implementation

  • what parts of MITK would need to be changed?
  • what needs to be changed in the Segmentation view?