Difference between revisions of "Projects:RegistrationLibrary:RegLib C02"
Line 127: | Line 127: | ||
*download/view guided video tutorial | *download/view guided video tutorial | ||
*download power point tutorial | *download power point tutorial | ||
− | * | + | * |
− | |||
[[Projects:RegistrationDocumentation:ParameterPresetsTutorial|Link to User Guide: How to Load/Save Registration Parameter Presets]] | [[Projects:RegistrationDocumentation:ParameterPresetsTutorial|Link to User Guide: How to Load/Save Registration Parameter Presets]] |
Revision as of 19:14, 23 August 2010
Home < Projects:RegistrationLibrary:RegLib C02Back to ARRA main page
Back to Registration main page
Back to Registration Use-case Inventory
Contents
Slicer Registration Library Case #02: Intra-subject Brain MR FLAIR to MR T1
mask image | fixed image/target | moving image | |
resample | segmentation labelmap |
Modules
- Slicer 3.6 recommended modules: BrainsFit, Robust Multiresolution Affine
Objective / Background
This scenario occurs in many forms whenever we wish to align all the series from a single MRI exam/session into a common space. Alignment is necessary because the subject likely has moved in between series. As additional files we have a mask for the fixed/reference image and a labelmap for the moving image we need to move along .
Keywords
MRI, brain, head, intra-subject, FLAIR, T1, defacing, masking, labelmap, segmentation
Input Data
- reference/fixed : T1 SPGR , 1x1x1 mm voxel size, 256 x 256 x 146, sagittal,
- mask: skull stripping labelmap obtained from above SPGR
- moving: T2 FLAIR 1.2x1.2x1.2 mm voxel size, sagittal
- tag: segmentation labelmap obtained from above FLAIR, to be resampled with result transform
Registration Challenges
- the amount of misalignment is small. Subject did not leave the scanner in between the two acquisitions, but we have some head movement.
- we know the underlying structure/anatomy did not change, but the two distinct acquisition types may contain different amounts of distortion
- the T1 high-resolution had a "defacing" applied, i.e. part of the image containing facial features was removed to ensure anonymity. The FLAIR is lower resolution and contrast and did not need this. The sharp edges and missing information in part of the image may cause problems.
- we have a skull stripping label map of the fixed image (T1) that we can use to mask out the non-brain part of the image and prevent it from actively participating in the registration.
- we have one or more label-maps attached to the moving image that we also want to align.
- the different series have different dimensions, voxel size and field of view. Hence the choice of which image to choose as the reference becomes important. The additional image data present in one image but not the other may distract the algorithm and require masking.
- hi-resolution datasets may have defacing applied to one or both sets, and the defacing-masks may not be available
- the different series have different contrast. The T1 contains good contrast between white (WM) and gray matter (GM) , and pathology appears as hypointense. The FLAIR on the other hand shows barely any WM/GM contrast and the pathology appears very dominantly as hyperintense.
Key Strategies
- Slicer 3.6 recommended modules: BrainsFit, Robust Multiresolution Affine
- we use an affine transform with 12 DOF (rather than a rigid one) to address distortion differences between the two protocols
- we choose the SPGR as the anatomical reference. Unless there are overriding reasons, always use the highest resolution image as your fixed/reference, to avoid loosing data through the registration.
- the defacing of the SPGR image introduces sharp edges that can be detrimental. We apply a multiresolution scheme at least. If this fails we mask that area or better still the brain. As a general rulle, if you have the mask available, use it.
- because of the contrast differences and the defacing we use Mutual Information as the cost function.
- because of the combined effects of rotational misalignment, defacing, pathology and contrast differences, we use a multi-resolution approach (Register Images MultiRes).
Procedures
with BrainsFit:
- download example dataset
- load into 3DSlicer 3.6
- open Registration : BrainsFit module
- Input Parameters: set SPGR as fixed and FLAIR as moving image
- Registration Phases:
- select Initialize with CenterofHeadAlign
- select Include Rigid registration phase
- select "Include Affine registration phase"
- Output Settings: select "New Linear Transform" under Output Transform
- accept all other defaults & click apply
- program will automatically move FLAIR image under the result transform; also manually move the labelmap
- right click on either image and select Harden Transform to apply & resample
- save result images/scene
with MultiresolutionAffine:
- download example dataset
- load into 3DSlicer 3.6
- open Registration : RobustAffineMultiresolution module
- set SPGR as fixed and FLAIR as moving image
- accept all defaults & click apply
- go to Data module and move FLAIR and labelmap under the result transform
- right click on either image and select Harden Transform to apply & resample
- save result images/scene
for more details see the tutorial under Downloads
Registration Results
unregistered
Robust Multiresolution Registration Result: FLAIR + segmentation aligned with SPGR : registered w. Multiresolution affine
BrainsFit Result: FLAIR aligned with SPGR: registered w. BrainsFit
Download
- Registration Library Case 02: MSBrain intra-subject multi-contrast: FLAIR+lesion segmentation to SPGR + mask (Data,Presets, Solution, zip file 27 MB)
- download/view guided video tutorial
- download power point tutorial
Link to User Guide: How to Load/Save Registration Parameter Presets