Difference between revisions of "Projects:RegistrationLibrary:RegLib C05"

From NAMIC Wiki
Jump to: navigation, search
m (Text replacement - "http://www.slicer.org/slicerWiki/index.php/" to "https://www.slicer.org/wiki/")
 
(14 intermediate revisions by one other user not shown)
Line 3: Line 3:
 
[[Projects:RegistrationDocumentation:UseCaseInventory|Back to Registration Use-case Inventory]] <br>
 
[[Projects:RegistrationDocumentation:UseCaseInventory|Back to Registration Use-case Inventory]] <br>
  
==Slicer Registration Use Case Exampe #5: Inter-subject Knee MRI ==
 
  
{| style="color:#bbbbbb; background-color:#333333;" cellpadding="10" cellspacing="0" border="0"
+
= <small>v3.6.1</small> [[Image:Slicer3-6Announcement-v1.png‎|150px]]  Slicer Registration Library Case 05: <br>  Inter-subject Knee MRI  =
|[[Image:RegLib C05 KneeMRI1.png|200px|lleft|this is the fixed reference image. All images are aligned into this space]]  
+
=== Input ===
|[[Image:Arrow_left_gray.jpg|100px|lleft]]  
+
{| style="color:#bbbbbb; " cellpadding="10" cellspacing="0" border="0"
|[[Image:RegLib C05 KneeMRI2.png|200px|lleft|this is the moving image. The transform is calculated by matching this to the reference image]]
+
|[[Image:RegLib C05 KneeMRI1.png|150px|lleft|this is the main fixed reference image. All images are ev. aligned into this space]]  
|align="left"|LEGEND<br>
+
|[[Image:RegArrow_Affine.png|70px|lleft]]  
[[Image:Button_red_fixed.jpg|20px|lleft]]  this indicates the reference image that is fixed and does not move. All other images are aligned into this space and resolution<br>
+
|[[Image:RegLib C05 KneeMRI2.png|150px|lleft|this is the moving image]]  
[[Image:Button_green_moving.jpg|20px|lleft]]  this indicates the moving image that determines the registration transform.  <br>
 
 
|-
 
|-
|[[Image:Button_red_fixed.jpg|40px|lleft]]  T1 SPGR
+
|subject 1
 
|
 
|
|[[Image:Button_green_moving.jpg|40px|lleft]] T1 SPGR
+
|subject 1
|-
 
|0.9375 x 0.9375 x 1.4 mm<br> 256 x 256 x 112<br>RAS
 
|
 
|0.9375 x 0.9375 x 1.2 mm<br> 256 x 256 x 130<br>RAS
 
 
|}
 
|}
 +
 +
=== Modules ===
 +
*'''Slicer 3.6.1 recommended modules:  [https://www.slicer.org/wiki/Modules:PythonSurfaceICPRegistration-Documentation-3.6 Surface Registration]
 +
 
===Objective / Background ===
 
===Objective / Background ===
The final goal is to align a segmentation prior model to aid in cartilage segmentation.
+
The final goal is to align a segmentation prior model/atlas to aid in cartilage segmentation.
 +
 
 
=== Keywords ===
 
=== Keywords ===
 
MRI, knee, inter-subject, segmentation
 
MRI, knee, inter-subject, segmentation
  
 
===Input Data===
 
===Input Data===
*[[Image:Button_red_fixed_white.jpg|20px]]reference/fixed : T1 SPGR , 0.9375 x 0.9375 x 1.4 mm voxel size, axial, RAS orientation.  
+
*fixed: T1 SPGR , 0.9375 x 0.9375 x 1.4 mm voxel size, axial.  + surface model from femur & tibia segmentation.
*[[Image:Button_green_moving_white.jpg|20px]] moving: T1 SPGR , 0.9375 x 0.9375 x 1.2 mm voxel size, sagittal, RAS orientation.
+
*moving: T1 SPGR , 0.9375 x 0.9375 x 1.2 mm voxel size, sagittal. + surface model from femur & tibia segmentation.
*Content preview: Have a quick look before downloading: Does your data look like this?  [[Media:RegUC2_lightbox.png]]
+
=== Procedure / Pipeline ===
*download dataset to load into slicer (~17 MB zip archive)
+
#Open case scene file or import image data + surface models
 
+
#Open ''Registration / Surface Registration'' module
 +
##Input Surface: S02_femur
 +
##Target Surface: S01_femur
 +
##Output Transform: create new transform, rename to "Xf1_surf_S2-S1"
 +
##Select/check ''Mean distance mode: RMS''
 +
##Leave defaults: iterations: 50, landmarks: 200
 +
##Select/check ''Start by matching centroids''
 +
##Select/check ''Check mean distance''
 +
##Click: ''Apply''; process duration: ~ seconds
 +
#Go to the ''Data'' module
 +
##find the newly created transform node "Xf1_surf_S2-S1" and drag the "S02_femur" model node (and all other S02 entities) inside the transform.
 +
##for the 3D viewer turn on the visibility of the surface models (should be on already)
 +
##the surfaces for the two femur models should now align in basic position and orientation
 +
#for additional details see tutorial downloads below
 +
 
=== Registration Results===
 
=== Registration Results===
{| style="color:#bbbbbb; background-color:#333333;" cellpadding="10" cellspacing="0" border="0"
+
[[Image:RegLib C05 AGif reg.gif|200px|femur surface models before/after registration]]
|}
 
  
 
===Download ===
 
===Download ===
*'''[[Media:RegLib_Case_01_TumorGrowth.zip‎|download entire package  <small> (Data,Presets,Tutorial, Solution, zip file 33.7 MB) </small>]]'''
+
*Data
 
+
**[[Media:RegLib_C05_Data.zip‎|'''RegLib_C05_Data''': Example Dataset <small> (MRI images, surface models,Presets, Solution, zip file 9.5 MB) </small>]]
<!--
+
*Presets
comment
+
**[[Media:RegLib_C05_Presets.mrml‎|'''RegLib_C05_Presets.mrml''': registration parameter presets<small> (.mrml text file 12 kB) </small>]]
-->
+
*[[Projects:RegistrationDocumentation:ParameterPresetsTutorial|Link to User Guide: How to Load/Save Registration Parameter Presets]]
 
+
*Documentation
 
+
**[[Media:RegLib_C05_Tutorial.ppt|'''RegLib_C05_Tutorial''': Powerpoint file <small> (.ppt file 1 MB) </small>]]
=== Discussion: Registration Challenges ===
+
**[[Media:RegLib_C05_Tutorial.ppt|'''RegLib_C05_Tutorial''': PDF file <small> (.pdf file 0.5 MB) </small>]]
*accuracy is the critical criterion here. We need the registration error (residual misalignment) to be smaller than the change we want to measure/detect. Agreement on what constitutes good alignment can therefore vary greatly.
 
*the two images have strong differences in coil inhomogeneity. This affects less the registration quality but hampers evaluation. Most of the difference does not become apparent until after registration in direct juxtaposition. Bias field correction beforehand is recommended.
 
*we have slightly different voxel sizes
 
*if the pathology change is substantial it might affect the registration.
 
  
=== Discussion: Key Strategies ===
+
=== Acknowledgments ===
*the two images have identical contrast, hence we consider "sharper" cost functions, such as NormCorr or MeanSqrd
 
*general practice is to register the follow-up to the baseline. However here the follow-up has slightly higher resolution. From an image quality/data perspective it would be better to use the highest resolution image as your fixed/reference. But here follow the most common convention, i.e. fixed image is the baseline.
 
*because we seek to assess/quantify regional size change, we must use a rigid (6DOF) scheme, i.e. we must exclude scaling.
 
*if the pathology change is soo large that it might affect the registration, we should mask it out. The simplest way to do this is to build a box ROI from the ROItool and feed it as input to the registration. Remember that masking does not mean that masked areas aren't matched, they just do not contribute to the cost function driving the registration, but move along passively.  Next more involved level would be to outline the tumor. If a segmentation is available, you can use that.
 
*these two images are not too far apart initially, so we reduce the default of expected translational misalignment
 
*because accuracy is more important than speed here, we increase the sampling rate from the default 2% to 15%.
 
*we also expect minimal differences in scale & distortion: so we can either set the expected values to 0 or run a rigid registration
 
*we test the result in areas with good anatomical detail and contrast, far away from the pathology. With rigid body motion a local measure of registration accuracy is representative and can give us a valid limit of detectable change.
 

Latest revision as of 17:06, 10 July 2017

Home < Projects:RegistrationLibrary:RegLib C05

Back to ARRA main page
Back to Registration main page
Back to Registration Use-case Inventory


v3.6.1 Slicer3-6Announcement-v1.png Slicer Registration Library Case 05:
Inter-subject Knee MRI

Input

this is the main fixed reference image. All images are ev. aligned into this space lleft this is the moving image
subject 1 subject 1

Modules

Objective / Background

The final goal is to align a segmentation prior model/atlas to aid in cartilage segmentation.

Keywords

MRI, knee, inter-subject, segmentation

Input Data

  • fixed: T1 SPGR , 0.9375 x 0.9375 x 1.4 mm voxel size, axial. + surface model from femur & tibia segmentation.
  • moving: T1 SPGR , 0.9375 x 0.9375 x 1.2 mm voxel size, sagittal. + surface model from femur & tibia segmentation.

Procedure / Pipeline

  1. Open case scene file or import image data + surface models
  2. Open Registration / Surface Registration module
    1. Input Surface: S02_femur
    2. Target Surface: S01_femur
    3. Output Transform: create new transform, rename to "Xf1_surf_S2-S1"
    4. Select/check Mean distance mode: RMS
    5. Leave defaults: iterations: 50, landmarks: 200
    6. Select/check Start by matching centroids
    7. Select/check Check mean distance
    8. Click: Apply; process duration: ~ seconds
  3. Go to the Data module
    1. find the newly created transform node "Xf1_surf_S2-S1" and drag the "S02_femur" model node (and all other S02 entities) inside the transform.
    2. for the 3D viewer turn on the visibility of the surface models (should be on already)
    3. the surfaces for the two femur models should now align in basic position and orientation
  4. for additional details see tutorial downloads below

Registration Results

femur surface models before/after registration

Download

Acknowledgments