Documentation/4.0/Modules/EMSegmenter

Introduction and Acknowledgements

This work was funded by the ARRA Supplement to the Neuroimage Analysis Center (NAC), funded by the National Institutes of Health. Information on NAC can be obtained from the NAC website. Author: Kilian Pohl, UPenn Contributor1: Daniel Haehn, UPENN Contact: Kilian Pohl, <email>pohl.kilian@gmail.com</email>

University of Pennsylvania   Surgical Planning Laboratory

Module Description

Hierarchical Model of the EMSegmenter

This module is designed for users who perform atlas based medical image segmentation. The module can be operated in two modes:
An advanced mode (Button: Adjust Parameters) that allows users to parameterize the tool to specific segmentation tasks and a simple mode (Button: Use Existing Setting) which is designed for users who would like to apply the predefined parameterization to new data with a minimal amount of user interaction. One can also apply the parameterization to medical scans via the command-line executable EMSegmentCommandLine. The remainder of this sections describes the work flow of the two modes in further detail:

Use Cases

The purpose of the module is to configure the algorithm to automatically segment anatomical structures in medical images. First the user has to specify parameters defining the image protocol and the anatomical structures of interests. This process results in a template that the module uses to automatically segment large data sets. The template is composed of atlas data and a non-trivial collection of parameters for the EMSegment algorithm.

Once the parameters are specified, the target images are segmented using the EM Segmentation algorithm (Pohl et al. TMI 2007). If the results are satisfactory, the template is saved and can be used later to segment new images (via the GUI or batch processing). If the results are unsatisfactory, the parameters can be modified and the segmentation re-run.

One important aspect of the project is the workflow wizard. This wizard simplifies the module by dividing the complicated template specification task into a number of smaller, intuitive steps. The wizard allows to create tasks and to use them to analyze data sets.

There are multiple predefined tasks which are ready to use.

Tutorials

• EMSegmenter Tutorial for 3D Slicer 3.6.2
  • Simple Mode - Tutorial Data
  • Advanced Mode - Tutorial Data

• EMSegmenter Tutorial for 3D Slicer 3.6.3
  • Simple Mode - Tutorial Data
  • Advanced Mode - Tutorial Data

• A full Tutorial for the two EMSegment modules

These slides and data describe the Slicer3 implementation of the two EMSegment GUI and command-line modules and demonstrate their use.

Tutorial Slides - Tutorial Data

• Another detailed training tutorial on EMSegment algorithm and the Slicer3 EMSegment module.

Tutorial Slides - Training Data

Panels and their use

Simple Mode

The work flow is defined by only two steps.

Step 1: Define Task

Select an already existing task and click on the "Use Existing Settings" button to use for the simple mode in the pop up window. A MRML file defining parameters of the algorithm specific to the task as well atlas data are automatically downloaded for existing Tasks.

Step 2: Define Input Channels

In this step the user specifies the scans to be segmented as well as the check list associated with the preprocessing. A click on the 'Segment' button is enough to start the pre-processing and the subsequent segmentation.

Advanced Mode

Unlike the Simple mode, the advanced mode is defined by nine steps which one can navigate via the "Back", "Next", or "Segment" button. The Segment button jumps right away to the last step of the work flow and segments the medical scans into the structures of interests.

Step 1: Define Task

Select an already existing task or define a new one. Click on the button "Adjust Parameters" for the advanced mode in the pop up window. A MRML file defining parameters of the algorithm specific to the task as well atlas data are automatically downloaded for existing Tasks.

Step 2: Define Input Channel

Define the number of input channels as well as the name of each channel and the corresponding scan associated with the channel. If using multiple input channel(scans) which are not aligned with each other then check on the check-box button "Align input scans".

Step 3: Define Anatomical Tree

The user specifies the hierarchical relationship between the anatomical structures. The tree will refine the complex segmentation task into a set of easier segmentation problems. A sub-classes is added to an existing structure by right-clicking on the structure and selecting "Add sub-class". The name, label, and color of a structure are modified by selecting the structure in the tree and then defining these attributes in the panel below.

Step 4: Define Atlas

In this step, the user links the probabilistic atlases to the anatomical structures in the tree by first highlighting the structure and then selecting the volume representing the probability map of that structure in the panel below. We note that the probabilistic atlas of structures with sub-structures is defined by the atlases of the sub-structures and thus is not explicitly defined.

Step 5: Edit Registration Parameters

The atlas is in general not aligned to the specific patient scans defined in Step 2. The user assigns in this step the scans of the atlas corresponding to the input channels in Step 2 as well as the type of registration (Affine / Deformable) and the interpolation.

Step 6: Define Preprocessing

Graph showing intensity distributions of a set of anatomical structures

This step is defined via a task specific Tcl file that configures the preprocessing pipeline of the input scans and the atlas. Complete the step by going through the task specific check list, clicking on the 'Next' button, and clicking on the 'Yes' button of the pop up window. One can define a new preprocessing pipeline by specifying the pipeline via a Tcl file, placing the file in Slicer3-build/share/Slicer3/Modules/EMSegment/Tasks and listing the file name in the task specific MRML file.

Step 7: Specify Intensity Distribution

Refining the intensity distribution for each structure of interest is often a critical step in the parameterization of the segmentation algorithm. Slicer 3.6 includes an overview window that shows the distribution in a 1D and 2D graph (press "Plot Distributions" to view the graph). By placing the mouse cursor in the 2D viewers the corresponding intensity value is shown in the graph.

Step 8: Edit Node-based Parameters

Users specify the relative to weight of a node in the tree with respect to other structures which are children of the same parent node. The first tab also specifies the weight of the input channels as well as the atlases. The value 'Alpha' specifies the smoothing applied to the structure (via MRFs). The second tab (Stopping Condition) lists the number of iterations associated with the segmentation task. By default, the Bias iteration is set to -1 which means that it is performed each iteration. If the value is greater -1 then the inhomogeneity computation is stopped after n iterations. The third tab specifies printing out intermediate results, which are saved in the working directory specified in the next step

Step 9: Define Miscellaneous Parameters

This panels lists the general parameters necessary for segmenting images. Users can specify a region of interest to speed up the segmentation algorithm. Pressing the 'Segment' button creates a label map of the anatomical structures.

Similar Modules

• Please see

References

• Wells III W.M., Grimson W.E.L., Kikinis R., Jolesz F.A. Adaptive segmentation of MRI data. IEEE Trans Med Imaging. 1996; 15(4):429-442.

• Pohl K.M., Fisher III J.W., Grimson W.E.L., Kikinis R., Wells III W.M. A Bayesian model for joint segmentation and registration. Neuroimage. 2006 May 15;31(1):228-39.

• Pohl K, Bouix S, Nakamura M, Rohlfing T, McCarley R, Kikinis R, Grimson W, Shenton M, Wells W. A Hierarchical Algorithm for MR Brain Image Parcellation. IEEE Transactions on Medical Imaging. 2007 Sept;26(9):1201-1212. [bib]

The section above is generated using the following wiki code:

{{documentation/{{documentation/version}}/module-section|Information for Developers}}
{{documentation/{{documentation/version}}/module-developerinfo|ModuleTemplate|type=Interactive|category=Example}}

If you are documenting a CLI, the category should be extracted from the corresponding XML description. This could be done automatically using the following wiki template:

{{documentation/{{documentation/version}}/module-category|xmlurl=http://path/to/YOURMODULENAME.xml }}

If your module is available in Slicer repository, the following template could be useful to obtain the corresponding URL:

{{documentation/{{documentation/version}}/module-cli-xmlurl|{{documentation/modulename}}|SVNREVISION}}

Using this later template, the final syntax would be:

{{documentation/{{documentation/version}}/module-category|xmlurl={{documentation/{{documentation/version}}/module-cli-xmlurl|{{documentation/modulename}}|SVNREVISION}} }}