Difference between revisions of "Projects:RegistrationLibrary:RegLib C08"
Line 3: | Line 3: | ||
[[Projects:RegistrationDocumentation:UseCaseInventory|Back to Registration Use-case Inventory]] <br> | [[Projects:RegistrationDocumentation:UseCaseInventory|Back to Registration Use-case Inventory]] <br> | ||
− | = | + | = <small>v3.6.1</small> [[Image:Slicer3-6Announcement-v1.png|150px]] Slicer Registration Library Case #08: Intra-subject whole-body PET-CT = |
− | + | === Input === | |
− | {| style="color:#bbbbbb | + | {| style="color:#bbbbbb; " cellpadding="10" cellspacing="0" border="0" |
− | |[[Image:RegLib_C08_CT1_thumbnail.png| | + | |[[Image:RegLib_C08_CT1_thumbnail.png|150px|lleft|this is the fixed CT image. All images are aligned into this space]] |
− | |[[Image:RegLib_C08_PET1_thumbnail.png| | + | |[[Image:RegLib_C08_PET1_thumbnail.png|150px|lleft|this is the fixed PET image. All images are aligned into this space]] |
− | |[[Image: | + | |[[Image:RegArrow_NonRigid.png|100px|lleft]] |
− | |[[Image:RegLib_C08_CT2_thumbnail.png| | + | |[[Image:RegLib_C08_CT2_thumbnail.png|150px|lleft|this is the moving image. The transform is calculated by matching this to the reference image]] |
− | |[[Image:RegLib_C08_PET2_thumbnail.png| | + | |[[Image:RegLib_C08_PET2_thumbnail.png|150px|lleft|this is the moving image. The transform is calculated by matching this to the reference image]] |
− | |||
− | |||
− | |||
− | |||
|- | |- | ||
− | | | + | |fixed image/target |
− | | | + | |fixed image/target |
| | | | ||
− | |[ | + | |moving image |
− | + | |moving image | |
− | + | |} | |
+ | |||
+ | === Modules === | ||
+ | *'''Slicer 3.6.1 recommended modules: [http://www.slicer.org/slicerWiki/index.php/Modules:BRAINSFit BrainsFit], [http://www.slicer.org/slicerWiki/index.php/Modules:RegisterImagesMultiRes-Documentation-3.6 Robust Multiresolution Affine]''' | ||
+ | |||
|CT: <small> 512 x 512 x 267<br> 0.97 x 0.97 x 3.27 mm | |CT: <small> 512 x 512 x 267<br> 0.97 x 0.97 x 3.27 mm | ||
|PET: 128 x 128 x 267<br> 4.7 x 4.7 x 3.3 mm </small> | |PET: 128 x 128 x 267<br> 4.7 x 4.7 x 3.3 mm </small> | ||
Line 29: | Line 29: | ||
|} | |} | ||
===Objective / Background === | ===Objective / Background === | ||
− | Change assessment. | + | Change assessment.=== Keywords === |
− | === Keywords === | ||
PET-CT, whole-body, change assessment | PET-CT, whole-body, change assessment | ||
===Input Data=== | ===Input Data=== | ||
− | * | + | *reference/fixed : baseline '''CT''': 0.97 x 0.97 x 3.27 mm , 512 x 512 x 267; '''PET''': 4.7 x 4.7 x 3.3 mm , 128 x 128 x 267 |
− | * | + | *moving: '''CT''': 0.98 x 0.98 x 5, 512 x 512 x 195; '''PET''': 4.1 x 4.1 x 5 mm, 168 x 168 x 195 |
− | |||
=== Registration Results=== | === Registration Results=== |
Revision as of 17:16, 5 October 2010
Home < Projects:RegistrationLibrary:RegLib C08Back to ARRA main page
Back to Registration main page
Back to Registration Use-case Inventory
Contents
v3.6.1 Slicer Registration Library Case #08: Intra-subject whole-body PET-CT
Input
fixed image/target | fixed image/target | moving image | moving image |
Modules
- Slicer 3.6.1 recommended modules: BrainsFit, Robust Multiresolution Affine
|CT: 512 x 512 x 267
0.97 x 0.97 x 3.27 mm
|PET: 128 x 128 x 267
4.7 x 4.7 x 3.3 mm
|
|CT: 512 x 512 x 195
0.98 x 0.98 x 5.0 mm
|PET: 168 x 168 x 195
4.1 x 4.1 x 5 mm
|}
Objective / Background
Change assessment.=== Keywords === PET-CT, whole-body, change assessment
Input Data
- reference/fixed : baseline CT: 0.97 x 0.97 x 3.27 mm , 512 x 512 x 267; PET: 4.7 x 4.7 x 3.3 mm , 128 x 128 x 267
- moving: CT: 0.98 x 0.98 x 5, 512 x 512 x 195; PET: 4.1 x 4.1 x 5 mm, 168 x 168 x 195
Registration Results
BSpline registration of full volumes achieves better alignment in the abdominal and thoracic region of interest. But the solution is suboptimal because the algorithm is distracted by the strong differences in head position.Rather than trying to address this with more DOF, we calculate a BSpline transform based on croped images including only the main region of interest.
Download
- download example data set (Data only, zip file 135 MB)
- download step-by-step tutorial (PowerPoint 2 MB)
- download registration BSpline testset only (zip file .nrrrd files 67 MB)
Link to User Guide: How to Load/Save Registration Parameter Presets
Discussion: Registration Challenges
- 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 series have different voxel sizes
- because of the large FOV we have strong non-rigid deformations from differences in patient/limb positions etc.
- images are large volumes (>100 MB total)
- image content reaches border of image on two sides
- 2 images pairs have to be aligned, i.e. the calculated transform must be applied to the second (PET) image.
Discussion: Key Strategies
- to calculate the transform, we use the images with the most accurate geometric representation and the smallest expected change, i.e. we align the follow-up CT to the baseline CT and then apply the transforms to the PET image.
- because of the non-rigid differences due to posture and breathing we will need to apply a 2-step registration with an affine alignment followed by a BSpline.
- the strong differences in head position is likely to distract the registration and lead to suboptimal results. Hence we produce a cropped version of the two CT images to calculate the BSpline transform.
- the two images are far apart initially, we will need some form of initialization. We will try an automated alignment first. If this fails, we do a 2-step process with manual initial alignment, followed by automated affine.
- because accuracy is more important than speed here, we increase the iterations and sampling rates. Note however the large image size, which makes comparable sampling % still large compared to other datasets.
- the two images have identical contrast, hence we could consider "sharper" cost functions, such as NormCorr or MeanSqrd. However, since these are not (yet) available for the BSpline registration.