User:Davisb/EMSegmentModule

Project Summary

The goal of this project is to implement a Slicer3 module which creates templates that will be used in segmentation tasks. A template is composed of atlas data and a non-trivial collection of parameters for the EM segmentation algorithm. The template, which is written as an XML file, can be used later to segment new images. The target audience for this module is someone familiar with brain atlases and tissue labels, not a computer scientist.

This module will be demonstrated at the NAMIC All-Hands meeting in January 2007.

Contacts

• MIT: Polina Golland, Kilian Pohl (pohl@csail.mit.edu)
• Kitware: Brad Davis (brad.davis@kitware.com), Will Schroeder (will.schroeder@kitware.com)

General Module Description

The purpose of the module is to build a template that can be used later to segment new images. The template is composed of atlas data and a non-trivial collection of parameters for the EM segmentation algorithm. It is the user's job to specify the parameters so that the template is effective for segmenting a particular target image pair (T1 and T2, for example, from a particular scanner). Once the parameters are specified, the target images are segmented using the EM segmentation algorithm. If the results are satisfactory, the template is saved and can be used to segment new target images. If the results are not satisfactory, the parameters can be modified and the segmentation re-run.

The template building process is divided in to a sequence of steps in order to simplify template specification for the non-expert user.

What are the steps in the template building process?

1. Anatomical Structure Hierarchy: Define a hierarchy of anatomical structures.
2. Spatial Priors: Assign uniform priors or probability images for each leaf node of the hierarchy.
3. Intensity Images: Assign atlas and target intensity images.
4. Intensity Distributions: Define an intensity distribution for each leaf node of the hierarchy.
5. Node-based Parameters: Specify node-based segmentation parameters.
6. Global Parameters: Specify global segmentation parameters.
7. Registration Parameters: Specify atlas-to-template registration parameters.
8. Segmentation: Apply EM algorithm to segment target image pair.

How will the template be used?

The user will (1) load the template, (2) load a new, unsegmented set of input images, (3) tweak parameters from the template if desired, and (4) start the segmentation process. If the input images are not aligned, they will be aligned prior to the segmentation process---this will be specified by the user.

Alternately, the template can be used by a batch process to segment a collection of images.

Will this process (applying the template) require any parameters that are not included in the template?

Yes. Parameters pertaining to the target images are not stored in the template. Specifically, the template does not store the (1) target volume IDs and (2) whether or not the target images must be aligned. All other parameters should be specified in the template.

Will the template building module contain parameters that are not included in the template?

Yes. The template will not contain information regarding the target images. Also, the template will not contain intermediate data used to compute parameters for the template (e.g., intensity samples used to compute mean and covariance).

Detailed Description of Wizard Steps

Step 1: Anatomical Structure Hierarchy

Build and edit a tree anatomical structures:

• add new structure (specify name & color)
• rename node, change associated color
• remove a node
• reorganize a node (e.g., specify a new parent for this node)

Step 2: Spatial Priors

For each leaf node specify a spatial prior by one of:

• Specify a uniform prior (double in [0,1])
• Specify a prior probability map (volume node reference)
• Number of training samples for prior probability map (int)

Step 3: Intensity Images

• Specify atlas intensity input volumes
• Specify target input volumes

Step 4: Intensity Distributions

For each leaf node specify mean and covariance of multivariate Gaussian distribution:

• parameters may be entered and edited manually
• parameters can be learned by clicking on a representative sample of voxels in the target intensity volumes (~8 clicks)
  • the target images must be aligned together for this method to make sense
  • the user may erase a particular sample or all samples
• A display will be available to visualize the intensity distributions
  • plot of distributions for input channels separately (marginal distributions, intensity vs. probability)
  • 2D image visualization of probabilities for input1xinput2 intensity combinations (input1 intensity vs. input2 intensity)
    • saturation is proportional to probability
  • In all plots, color is based on tissue type (color selected for leaf node in tree)
  • The user can choose which two input channels are displayed
  • The user can toggle the display of each tissue type on and off
  • When the user mouses over the MR image, the intensity under the mouse is plotted on each graph

Step 5: Node-Based Parameters

For all nodes

• Class Probability---double
• Local Prior Weight---double
• Input Channel Weights---double for each input channel, final representation is char*
• Print flags
  • Weights

For leaf nodes only

• Intensity mean and covariance: this is specified in previous step
• Print flags
  • PCA
  • Quality
    • Requires specification of reference standard volume

For parent nodes only

• Frequency---int---used by some of the print flags
• Print flags
  • Registration Parameters
  • Registration Similarity Measure
  • Bias---uses Frequency
  • Label-map---uses Frequency
  • Shape Similarity Measure
  • EMLabelMapConvergence
  • EMWeightsConvergence
  • MFALabelMapConvergence
  • MFAWeightsConvergence
• Stopping Condition Parameters
  • EM Type---int
  • EM Value---double
  • EM Max Iterations---int
  • MFA Type---int
  • MFA Value---double
  • MFA Max Iterations---int
  • Bias Calculation---int
• Miscellaneous Parameters
  • Local Prior Name---char*
  • Registration Translation---double[3]
  • Registration Rotation---double[3]
  • Registration Scale---double[3]
  • Registration Covariance---double[9]
  • Registration Class Specific Registration Flag
  • Exclude From Incomplete E-Step Flag
  • Registration Type---int
  • Generate Background Probability Flag
  • PCA Shape Model Type---int
  • Registration Independent Sub-class Flag
• Class Interaction Matrices
  • 6 matrices: North, South, East, West, Up, Down; choose from list
  • Each matrix is of size (number of subclasses) by (number of subclasses)
  • Each element is a double
  • The final representation for each matrix is char*

Step 6: Global Parameters

• Alpha---double
• Smoothing Kernel Width---int
• Smoothing Kernel Sigma---double
• Multi-threading Enabled---on/off
• Working Directory---char*
• SegmentationBoundaryMax--int[3]
• SegmentationBoundaryMin--int[3]

Non-template options:

• Run Remotely---on/off
• Remote Server---char*---should be something like davisb@swan.cs.unc.edu

Step 7: Registration Parameters

What type of registration should be run: a pull down list.

• Affine
  • MI
  • ....
  • disabled
• non rigid
  • Bspline
  • AG
  • ....
  • disabled
• joint registration & segmentation

Choose interpolation type from pull down list:

• Linear
• Cubic
• Nearest-neighbor

Alignment of input channels on/off (shouldn't this should occur before intensity sampling?---bcd)

Step 8: Segmentation

• The user can save the template before or after running the algorithm
• Run Algorithm
• Progress bar
• User can interrupt execution
• At completion the user can
  • visualize segmentations as overlays on the loaded image volumes
  • press button to remove small islands
  • press button to generate 3D modeles

Description of MRML Nodes

Overview

By writing out a template we just mean writing the MRML tree.

The template will include atlas data (i.e. specification of image files), anatomical structure hierarchy information, algorithm parameters, and display parameters (e.g., the graph color for a particular structure). The data, hierarchy, parameter, and display information will be defined in separate nodes. Dependencies and hierarchical structure will be maintained by references: for example, a leaf node will contain a reference to the ID of its parent node. This is the idiom that is used, for example, to nest transforms and associate image volumes with volume display parameters in Slicer3.

The following graph shows dependency information for all of the nodeem types proposed for this file format. An arrow pointing from node A to node B indicates that (1) the XML tag for each node of type A contains a reference to the ID of a node of type B, and (2) the MRML node class representing an A node contains a pointer to a MRML B node class. Note that parent nodes in the anatomical structure hierarchy are a special case: they do not contain references to their child nodes in the XML tags. However, they do contain pointers to their child nodes in their MRML classes. Also, the prefix EMS in the graph will be expanded to EMSegment.

Template Builder (A)

Template Applyer

Template Applyer Expanded

Template Builder (B)

g5

Example Template File

#
# NB: Only the keys are included, not the values.
#

#
# atlas data (intensity and probabiliy maps) are stored in volume nodes
#
<VolumeArchetypeStorage id name>
<VolumeDisplay id name>
<Volume id name storageNodeRef displayNodeRef>
[more Volume nodes...]

#
# Main EMSegment node
#
<EMSegment
  id name
  globalDisplayNodeRef
  globalParametersNodeRef
  treeNodeRef>

#
# Global display parameters
#
<EMSegmentGlobalDisplay
  id name
  [graph display parameters...]
  [toggle display of advanced parameters...]>

#
# Global algorithm parameters
#
<EMSegmentGlobalParameters
  id name
  [list of atlas input volume references...]
  [global algorithm parameters...]>

#
# Hierarchy of anatomical structures
#
<EMSegmentTree
  id name
  parentNodeRef
  parametersNodeRef
  parametersLeafNodeRef
  parametersParentNodeRef
  displayNodeRef>
[more Tree nodes...]

  pcaParametersLeafNodeRef
  inhomogeneityParametersParentNodeRef

#
# node-specific parameters
#
<EMSegmentTreeParameters
  id name
  parametersRegistrationNodeRef
  [generic node-based algorithm parameters...]>
[more TreeParameters nodes...]

<EMSegmentTreeParametersParent
  id name
  parametersParentRegistrationNodeRef
  parametersParentPCANodeRef
  parametersParaentInhomogeneityNodeRef
  [class interactions matrix node refs...]
  [volume refs (not typically used)...]
  [parent-node specific algorithm parameters...]>
[more TreeParametersParent nodes...]

<EMSegmentTreeParametersLeaf
  id name
  parametersLeafPCANodeRef
  localPriorNodeRef
  [leaf-node specific algorithm parameters...]>
[more TreeParametersLeaf nodes...]

<EMSegmentTreeDisplay
  id name
  [node-specific display parametters...]>
[more TreeDisplay nodes...]

<EMSegmentCIM
  id name
  matrix>
[more CIM nodes...]

<EMSegmentTreeParametersNodeRegistration
  id name
  [generic node-based registration parmeters...]>
[more TreeParametersNodeRegistration nodes...]

<EMSegmentTreeParametersParentRegistration
  id name
  [parent-node specific registration parmeters...]>
[more TreeParametersParentRegistration nodes...]

<EMSegmentTreeParametersParentPCA
  id name
  [parent-node specific PCA parmeters...]>
[more TreeParametersParentPCA nodes...]

<EMSegmentTreeParametersLeafPCA
  id name
  [leaf-node specific PCA parmeters...]>
[more TreeParametersLeafPCA nodes...]

<EMSegmentTreeParametersParentInhomogeneity
  id name
  [parent-node specific inhomogeneity parmeters...]>
[more TreeParametersParentInhomogeneity nodes...]

Detailed Description

The following list contains all possible template parameters; not all parameters will be tunable by the user during the template building process. Currently, the variables in itatlic have low priority.

Atlas Data

• Atlas intensity images; specified via MRML Volume nodes.
• Spatial prior probability images that are aligned with the atlas intensity images; specified via MRML Volume nodes.

Main EM Segment Template Node

The template contains references to global algorithm and display parameters as well as the class hierarchy.

<EMSegment
  id name
  globalDisplayNodeRef
  globalParametersNodeRef
  atlasNodeRef
  targetNodeRef
  treeNodeRef>

• Core attributes
  • GlobalDisplayNodeRef--char*
  • GlobalParametersNodeRef--char*
  • AtlasNodeRef--char*
  • TargetNodeRef--char*
  • TreeNodeRef--char*

Global EM Algorithm Parameters

Global EM algorithm parameters are stored in a single node.

<EMSegmentGlobalParameters
  id name
  [list of atlas input volume references...]
  [global algorithm parameters...]>

• MRML node attributes
  • Name
  • ID

• Core attributes
  • Alpha--double (should this be node specific?)
  • AlreadyRead--int (internal state variable that should not be included?)
  • DisableMultiThreading--int
  • NumberOfInputChannels--int--MaxInputChannelDef
  • NumberOfTrainingSamples--int (Kilian : Should be moved to atlas node; Brad: moved)
  • SegmentationBoundaryMax--int[3]
  • SegmentationBoundaryMin--int[3]
  • WorkingDirectory--char*--PrintDir

• Additional core attributes (added by Brad and edited by Kilian)
  • List of Input channels
  • AlignInput - int (nonzero=>target input channels will be aligned to each other prior to segmentation???)
  • RegistratonType--int (none, Joint, Sequential)
    • The following inputs are only relevant if RegistratonType != none
      • RegistratonInterpolationType--int (linear, nn, cubic )
    • The following inputs are only relevant if RegistratonType = Sequential
      • RegistrationInputRef--char* (which of the input channels should be used for aligning the atlas)
      • RegistrationAtlasImageRef--char* (Image representing the coordinate system of the atlas)
      • RegistratonAffine--int (MI,..., disabled)
      • RegistratonNonRigid--int (AG,BSpline, ..., disabled)

Global EM Display Parameters [not used]

Global EM display parameters are stored in a single node.

<EMSegmentGlobalDisplay
  id name
  [graph display parameters...]
  [toggle display of advanced parameters...]>

• MRML node attributes
  • Name
  • ID

• Core attributes
  • (Graph display parameters...)
  • (I expect this to grow as the GUI develops)

Hierarchy of Anatomical Structures

The hierarchy of anatomical structures is defined by a sequence of nodes. The nodes that define the hierarchy are separate from nodes that contain algorithm or display parameters.

<EMSegmentTree
  id name
  parentNodeRef
  parametersNodeRef
  parametersLeafNodeRef
  parametersParentNodeRef
  displayNodeRef>

• MRML node attributes
  • Name
  • ID

• Core attributes
  • DisplayNodeRef--char* (for example color in graph)
  • ParametersLeafNodeRef--char* (leaf-node specific algorithm parameters)
  • ParametersNodeRef--char* (generic node-based algorithm parameters)
  • ParametersParentNodeRef--char* (parent-node specific algorithm parameters)
  • ParentNodeRef--char*--null in case of root node

Node-based Display Parameters [moved to tree node]

<EMSegmentTreeDisplay
  id name
  [node-specific display parameters...]>

• MRML node attributes
  • Name
  • ID

• Core attributes
  • Color--char*--color associated with this anatomical structure
  • (I expect that more will be added here as the GUI develops)

Generic Node-based EM Algorithm Parameters

These attributes are applicable to both super-class and leaf-class MRML nodes.

<EMSegmentTreeParameters
  id name
  parametersRegistrationNodeRef
  [generic node-based algorithm parameters...]>

• MRML node attributes
  • Name
  • ID

• Core attributes
  • InputChannelWeights--char*
  • LocalPriorNodeRef--char*--LocalPriorName
  • LocalPriorWeight--double
  • PrintWeights--int
  • ClassProbability--double (need more descriptive name)
  • ParemetersRegistrationNodeRef--char*

• Experimental attributes
  • ExcludeFromIncompleteEStep--int--ExcludeFromIncompleteEStepFlag

Parent-node Specific EM Algorithm Parameters

Parent-node specific algorithm parameters are stored in a MRML node.

<EMSegmentTreeParametersParent
  id name
  parametersParentRegistrationNodeRef
  parametersParentPCANodeRef
  parametersParentInhomogeneityNodeRef
  [class interactions matrix node refs...]
  [volume refs (not typically used)...]
  [parent-node specific algorithm parameters...]>

• MRML node attributes
  • Name
  • ID

• Core attributes
  • ParametersParentRegistrationNodeRef [not implemented]--char*
  • ParametersParentPCANodeRef [not implemented]--char*
  • NumClasses--int
  • PredefinedLabelMapPrefix [not implemented]--char* (change to mrml node ID? yes)
  • PrintFrequency--int
  • PrintLabelMap--int
  • StopEMMaxIteration--int--StopEMMaxIter
  • StopEMType--int
  • StopEMValue--double
  • StopMFAMaxIteration--int--StopMFAMaxIter
  • StopMFAType--int
  • StopMFAValue--double

• Aditional core attributes (added by Brad)
  • CIMMatrixNorthNodeRef [not implemented]--char*
  • CIMMatrixSouthNodeRef [not implemented]--char*
  • CIMMatrixEastNodeRef [not implemented]--char*
  • CIMMatrixWestNodeRef [not implemented]--char*
  • CIMMatrixUpNodeRef [not implemented]--char*
  • CIMMatrixDownNodeRef [not implemented]--char*

• Experimental attributes
  • GenerateBackgroundProbability--int
  • ParameterInitSubClass [not implemented]--int
  • ParameterSaveToFile [not implemented]--int
  • ParameterSetFromFile [not implemented]--int
  • PredefinedLabelID [not implemented]--int (how does this differ from prefix above? - this assigns the class with a certain internal id specified by the user. In the prefix above we would assign the prefix of the volume)
  • PrintEMLabelMapConvergence--int
  • PrintEMWeightsConvergence--int
  • PrintMFALabelMapConvergence--int
  • PrintMFAWeightsConvergence--int

Leaf-node specific EM Algorithm Parameters

Leaf-node specific algorithm parameters are stored in a MRML node.

<EMSegmentTreeParametersLeaf
  id name
  parametersLeafPCANodeRef
  localPriorNodeRef
  [leaf-node specific algorithm parameters...]>

• MRML node attributes
  • Name
  • ID

• Core attributes
  • ParametersLeafPCANodeRef [not implemented]--char*
  • Label--int
  • LocalPriorWeight--double
  • LogCovariance--char*
  • LogMean--char*
  • PrintQuality--int
  • ReferenceStandardFilename [not implemented]--char* (change to mrml node ID? yes again this is case specific - should be defined through through target input node)

• Experimental attributes
  • SamplingLogMean--char* (REMOVE)
  • SamplingLogCovaraince--char* (REMOVE)

Class Interaction Matrix [not implemented]

Six class interaction matrices (CIMs) are included for each parent node in the template. These matrices are named North, South, East, West, Up, and Down. These names correspond to positive and negative cardinal directions within the target image space. The element at row i and column j of the North CIM describes the probability that a voxel with class label i will be found North of a voxel with class label j.

CIMs are represented in the template by EMSegmentCIM nodes.

<EMSegmentCIM id name [matrix entries]>

• MRML node attributes
  • Name
  • ID
• Core attributes
  • Matrix--char*

Generic node-based registration parameters [not implemented]

<EMSegmentTreeParametersNodeRegistration
  id name
  [generic node-based registration parmeters...]>

• MRML node attributes
  • Name
  • ID

• Core attributes
  • PrintRegistrationParameters--int
  • PrintRegistrationSimilarityMeasure--int
  • EmployClassSpecificRegistration--int--RegistrationClassSpecificRegistrationFlag
  • RegistrationCovariance--double[9]
  • RegistrationRotation--double[3]
  • RegistrationScale--double[3]
  • RegistrationTranslation--double[3]

Parent-node specific registration parameters [not implemented]

<EMSegmentTreeParametersParentRegistration
  id name
  [parent-node specific registration parmeters...]>

• MRML node attributes
  • Name
  • ID

• Core attributes
  • RegistrationIndependentSubclassFlag--int (need different name? )
  • RegistrationType--int

Parent-node specific PCA parameters [not implemented]

<EMSegmentTreeParametersParentPCA
  id name
  [parent-node specific PCA parmeters...]>

• MRML node attributes
  • Name
  • ID

• Core attributes
  • PCAShapeModelType--int (change to hapeModelType)
  • PCAPrintShapeSimilarityMeasure--int (change to PrintShapeSimilarityMeasure)

Leaf-node specific PCA parameters [not implemented]

<EMSegmentTreeParametersLeafPCA
  id name
  [leaf-node specific PCA parmeters...]>

• MRML node attributes
  • Name
  • ID

• Core attributes
  • PCALogisticBoundary--double
  • PCALogisticMax--double
  • PCALogisticMin--double
  • PCALogisticSlope--double
  • PCAMeanName--char* (a filename? change to atlas id)
  • PrintPCA--int

Parent-node specific Inhomogeneity parameters [currently implemented in parent node]

<EMSegmentTreeParametersParentInhomogeneiry
  id name
  [parent-node specific inhomegeneity parmeters...]>

• MRML node attributes
  • Name
  • ID

• Core attributes
  • PrintBias--int
  • StopBiasCalculation--int
  • SmoothingKernelSigma--double--SmSigma
  • SmoothingKernelWidth--int--SmWidth
  • InhomogeneityNodeRef--char* [not implemented] (change to mrml node ID? This is actually case specific - yes it makes sense to change it to id should be defined by atlas id !)