Difference between revisions of "DBP3:Utah:SlicerModuleCardiacRegistration"
m (Text replacement - "http://www.slicer.org/slicerWiki/index.php/" to "https://www.slicer.org/wiki/") |
|||
(13 intermediate revisions by one other user not shown) | |||
Line 1: | Line 1: | ||
__NOTOC__ | __NOTOC__ | ||
− | === | + | ===CMR Toolkit Cardiac Registration=== |
{| | {| | ||
− | |[[Image:Cardiac_mri_registration_module.jpg|thumb|280px|Registered image, fixed image, and moving image]] | + | |[[Image:Cardiac_mri_registration_module.jpg|thumb|280px|(L to R) Registered image, fixed image, and moving image]] |
|} | |} | ||
Line 17: | Line 17: | ||
Type: CLI | Type: CLI | ||
− | Category: | + | Category: Cardiac MRI Toolkit |
</div> | </div> | ||
Line 24: | Line 24: | ||
==Module Description== | ==Module Description== | ||
− | This module implements case-specific registration for cardiac LGE-MRI, MRA and CT images. | + | This module implements case-specific registration for cardiac LGE-MRI, MRA and CT images acquired at different time points or across different patients. The types of registration scenarios are described [[DBP3:Utah:RegCases|here]]. The inputs to this module are two image volumes: image volume one is the fixed volume, and image volume two is the moving volume. The goal of registration is to find a spatial mapping that will align the moving volume with the fixed volume. The user selects the imaging modalities based on the types of input image volumes. Registration parameters are tuned for the registration cases. Input image volumes that are cropped to the area around the left atrium can be used as well, which would improve the final registration result. Advanced registration parameters can be changed to check if the registration result shows improvement. |
</div> | </div> | ||
Line 33: | Line 33: | ||
===Examples, Use Cases & Tutorials=== | ===Examples, Use Cases & Tutorials=== | ||
+ | [[Media:Carma_Registration_Tutorial.pptx|CARMA Registration Tutorial]] | ||
− | + | The image volumes in this dataset: [http://hdl.handle.net/1926/1765 CARMA Registration Tutorial Data] can be used as inputs to the module. The dataset contains anonymized LGE-MRI, MRA and CT images. | |
===Quick Tour of Features and Use=== | ===Quick Tour of Features and Use=== | ||
Line 44: | Line 45: | ||
* Output Image Volume : The registration result | * Output Image Volume : The registration result | ||
* Imaging modality: The types of image volumes that are being registered (e.g LGE-MRI, MRA, CT, Acute Scar) | * Imaging modality: The types of image volumes that are being registered (e.g LGE-MRI, MRA, CT, Acute Scar) | ||
+ | |||
+ | ===Advanced Registration Parameters=== | ||
+ | The advanced registration parameters are: | ||
+ | * Registration Type | ||
+ | * Metric Type | ||
+ | * Initialization Type | ||
+ | * Interpolation Type | ||
+ | * Maximum Number of Iterations | ||
+ | * Sampling Ratio | ||
+ | * Sample from Fixed/Moving Image Overlap | ||
+ | The details about the advanced registration parameters can be found at https://www.slicer.org/wiki/Modules:RegisterImages-Documentation-3.6. | ||
</div> | </div> | ||
Line 50: | Line 62: | ||
<div style="margin: 20px;"> | <div style="margin: 20px;"> | ||
<div style="width: 27%; float: left; padding-right: 3%;"> | <div style="width: 27%; float: left; padding-right: 3%;"> | ||
+ | |||
== Development == | == Development == | ||
− | === | + | ===Source code & documentation=== |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | + | The source code for this module can be found at the [https://github.com/carma-center/carma_slicer_extension/ GitHub repository]. | |
− | |||
− | |||
</div> | </div> | ||
<div style="width: 27%; float: left; padding-right: 3%;"> | <div style="width: 27%; float: left; padding-right: 3%;"> | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− |
Latest revision as of 17:08, 10 July 2017
Home < DBP3:Utah:SlicerModuleCardiacRegistrationCMR Toolkit Cardiac Registration
Authors, Collaborators & Contact
- CARMA Center, University of Utah: Alan Morris, Greg Gardner, Salma Bengali, Josh Cates, Rob MacLeod
General Information
Module Type & Category
Type: CLI
Category: Cardiac MRI Toolkit
Module Description
This module implements case-specific registration for cardiac LGE-MRI, MRA and CT images acquired at different time points or across different patients. The types of registration scenarios are described here. The inputs to this module are two image volumes: image volume one is the fixed volume, and image volume two is the moving volume. The goal of registration is to find a spatial mapping that will align the moving volume with the fixed volume. The user selects the imaging modalities based on the types of input image volumes. Registration parameters are tuned for the registration cases. Input image volumes that are cropped to the area around the left atrium can be used as well, which would improve the final registration result. Advanced registration parameters can be changed to check if the registration result shows improvement.
Usage
Examples, Use Cases & Tutorials
The image volumes in this dataset: CARMA Registration Tutorial Data can be used as inputs to the module. The dataset contains anonymized LGE-MRI, MRA and CT images.
Quick Tour of Features and Use
The following are the inputs and outputs:
- Image Volume One (Fixed): Select the LGE-MRI, MRA or CT Image
- Image Volume Two (Moving): Select the LGE-MRI or MRA image
- Output Image Volume : The registration result
- Imaging modality: The types of image volumes that are being registered (e.g LGE-MRI, MRA, CT, Acute Scar)
Advanced Registration Parameters
The advanced registration parameters are:
- Registration Type
- Metric Type
- Initialization Type
- Interpolation Type
- Maximum Number of Iterations
- Sampling Ratio
- Sample from Fixed/Moving Image Overlap
The details about the advanced registration parameters can be found at https://www.slicer.org/wiki/Modules:RegisterImages-Documentation-3.6.
Development
Source code & documentation
The source code for this module can be found at the GitHub repository.