Modules:RobustStatisticsSeg-Documentation-3.6

Return to Slicer 3.6 Documentation

Robust Statistics Segmentation

RSS module panel

RSS result for abdominal CT image

RSS result for Brain MR image

General Information

Module Type & Category

Type: CLI

Category: Segmentation

Authors, Collaborators & Contact

• Yi Gao (Author): Georgia Tech
• Allen Tannenbaum (Author): Georgia Tech
• Ron Kikinis (Author): BWH
• Contact: Yi Gao, yi.gao@gatech.edu

Module Description

This module is a general purpose segmentor. The target object is initialized by a label map. An active contour model then evolves to extract the desired boundary of the object.

Usage

---> --->

Use Cases, Examples

• Note use cases for which this module is especially appropriate, and/or link to examples.
• Link to examples of the module's use

Tutorials

• First run:

1. Give a rough estimate of the object volume and use the editing module to paint several non-zero labels, called seeds in the following, in the object.
2. Run the module using the default parameters.

• Note:

1. The Approximate volume is just a rough upper limit for the volume. It should be at least the size of the object. This is because when the volume reaches that, the program must stop. However, other criteria may stop the algorithm before the volume reaches this value.
2. The positions of the seeds have to be in the object, preferably close to center.

• Troubleshooting
  • Surface is too rough. Try:
    • Increase "Boundary smoothness"
  • Leakage into thin/narrow regions. Try:
    • Increase "Boundary smoothness"
  • leakage into similar (but still different) intensity regions (which is not necessarily thin), Try:
    • Increase "Intensity homogeneity"
  • Some regions are missed: Try (either one):
    • Increase "Max volume"
    • Decrease"Intensity homogeneity"
    • Decrease "Boundary smoothness"
  • Some regions are missed, at the same time leakages to some other regions. Try (either one)
    • Increase "Intensity homogeneity"
    • Add some other seeds

• Data Set 1

• Multiple-value label map handling

The parameter "Output Label Value"(OLV) is for user to assign the output label value. Moreover, it is also used in cases where the user provided label map contains more than one label value. In general, the module handles three cases:

1. user provided label map contains only one label value, L. In this case, the output label value will be set to OLV, not matter what value L takes.
2. user provided label map contains multiple label values, one of which matches OLV. Then only that label will be effective and all the others are discarded. The output will have label value OLV too.
3. user provided label map contains multiple label values, but none matches OLV. Then all the non-zero labels will be considered as a single label value and then come back to the case 1 above.

Quick Tour of Features and Use

A list panels in the interface, their features, what they mean, and how to use them. For instance:

Input panel: First input Second input Parameters panel: First parameter Second parameter Output panel: First output Second output Viewing panel:

User Interface

Development

Notes from the Developer(s)

Algorithms used, library classes depended upon, use cases, etc.

Dependencies

Other modules or packages that are required for this module's use.

Tests

On the Dashboard, these tests verify that the module is working on various platforms:

• MyModuleTest1 MyModuleTest1.cxx
• MyModuleTest2 MyModuleTest2.cxx

Known bugs

Links to known bugs in the Slicer3 bug tracker

• Bug 000: description

Usability issues

Follow this link to the Slicer3 bug tracker. Please select the usability issue category when browsing or contributing.

Source code & documentation

Links to the module's source code:

Source code:

• file.cxx
• file.h

Doxygen documentation:

• class1

More Information

Acknowledgment

This work was supported in part by grants from NSF, AFOSR, ARO, as well as by a grant from NIH (NAC P41 RR-13218) through Brigham and Women’s Hospital. An NSF Fellowship supported part of the work.