Documentation/4.2/Modules/EMSegment Command-line

From SlicerWiki
Jump to: navigation, search
Home < Documentation < 4.2 < Modules < EMSegment Command-line

For the latest Slicer documentation, visit the 4.6 page.

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,

University of Pennsylvania  
Surgical Planning Laboratory  

Module Description

Use Cases

The primary function of the EMSegmenter module is to step the user through the process of calibrating, via algorithm parameters, the segmentation algorithm to a particular set of input data. However, once a successful collection of parameters is established, the user will commonly want to bypass this detailed calibration process when segmenting new images by using those parameters collected from the calibration process in EMSegmenter module. The EMSegment Command-line module which wraps the EMSegmentCommandLine executable provides this batch processing capability. The EMSegment Command-line module is automatic generated from the EMSegmentCommandLine executable using the --xml option.

This module is especially appropriate for segmenting large quantity of data by scripted/batch processing. It requires predefined parameter set, and new target/atlas images can be specified on command line. A list of predefined task is given here.


These slides and data describe the Slicer3 implementation of all three EMSegment modules and demonstrate their use.

Slides - Data

Panels and their use

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


     * '
       ** ': 


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.

Information for Developers