MeningiomaMRIRegistrationStudy

Objective

Accurate registration of same patient/same modality MRI data for longitudinal analysis of tumor progression.

Specific Aims

1. Compare the accuracy of registration using existing Slicer and non-Slicer tools
2. Identify parameter settings that produce satisfactory results
3. Outline the limitations of the available registration tools in the context of the specific clinical research application

Data

• Input images: isotropic post-contrast T1 MRI acquired at different locations of BWH during 2006-2008, used under medical records study IRB. Time period between acquisition of scans for each patient is about 1 year.
• images were acquired with the same sequence, but possible on different scanners, all scans are axial
• Ground truth transformation: not available
• Expert landmarks for registration evaluation: not available
• Checkerboard appearance of unregistered images for the representative data of interest

• • Case01

• 
• 
• 

• • Case03

• 
• 
• 

• • Case04

• 
• 
• 

• • Case10

• 
• 
• 

Environment

• all registration methods were executed on george.bwh.harvard.edu, which has 16 cores like this one (output of "cat /proc/cpuinfo"):

processor       : 0
vendor_id       : AuthenticAMD
cpu family      : 15
model           : 33
model name      : Dual Core AMD Opteron(tm) Processor 880
stepping        : 2
cpu MHz         : 1000.000
cache size      : 1024 KB
physical id     : 8
siblings        : 2
core id         : 0
cpu cores       : 2
fpu             : yes
fpu_exception   : yes
cpuid level     : 1
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt lm 3dnowext 3dnow rep_good pni lahf_lm cmp_legacy
bogomips        : 2010.02
TLB size        : 1024 4K pages
clflush size    : 64
cache_alignment : 64
address sizes   : 40 bits physical, 48 bits virtual
power management: ts fid vid ttp

• Where number of threads was possible to specify (RegisterImages and BRAINSFit), it was set to 4. RigidRegistration uses maximum number of threads available, while FLIRT is single-threaded (need to be checked)

Measures of success

• qualitative assessment: visually pleasing results
• quantitative assessment: something better than "visually pleasing" (TBD)
• minimum execution time to meet the application requirements: interactive quantification of tumor growth
• minimum tuning of registration parameters (is this possible? to answer this sub-question we compare the results with FLIRT registration using its default parameters)

Methods

Registration

RegisterImages Slicer module

• parameters:

Slicer3 --launch RegisterImages --saveTransform ${RI_TFM} \
  --initialization ImageCenters --registration Rigid --expectedOffset 10 \
  --expectedRotation 0.1   --expectedScale 0.05 --expectedSkew 0.01 \
  --verbosityLevel Standard   --sampleIntensityPortion 0.05 --randomNumberSeed 12345 \
  --numberOfThreads 4   --baselineNumberOfFailedPixelsTolerance 1000 \
  --baselineIntensityTolerance 10 --baselineRadiusTolerance 0 --rigidMaxIterations 200 \
  --rigidSamplingRatio 0.01   --affineMaxIterations 50 --affineSamplingRatio 0.02 \
  --bsplineMaxIterations 20 --bsplineSamplingRatio 0.1 --controlPointSpacing 40 \
   ${FIXED_IMAGE} ${MOVING_IMAGE}

• execution time: ~1-2 min

RigidRegistration Slicer module

• parameters

Slicer3 --launch RigidRegistration --fixedsmoothingfactor 0  \
  --movingsmoothingfactor 0 --histogrambins 50 --spatialsamples 100000 \
  --iterations 1000,1000,500,200 --learningrate 0.01,0.005,0.0005,0.0002 \
  --translationscale 100 --outputtransform ${RR_TFM}
  ${FIXED_IMAGE} ${MOVING_IMAGE}

• execution time: ~4min

BRAINSFit

• BRAINSFit on NITRC
• Technical details on InsightJournal
• Parameters:

${SLICER} --launch BRAINSFitExe \
  --fixedVolume ${TIME_POINT_1}  --movingVolume ${TIME_POINT_2} \
  --transformType Rigid --initializeTransformMode CenterOfHead \
  --numberOfIterations 200 --numberOfSamples 100000 --minimumStepSize 0.005 \
  --spatialScale 1000 --reproportionScale 1 \
  --outputTransform ${BF_TRANSFORM} --histogramMatch \
  --strippedOutputTransform ${BF_STRIPPED_TRANSFORM} \
  --patientID ANON --studyID ANON --outputVolumePixelType float \
  --backgroundFillValue 0 --maskProcessingMode ROIAUTO \
  --fixedVolumeTimeIndex 0 --movingVolumeTimeIndex 0 \
  --fixedVolumeOrigin 0,0,0 --movingVolumeOrigin 0,0,0 \
  --medianFilterSize 0,0,0 --permitParameterVariation 1,1,1 \
  --useCachingOfBSplineWeightsMode ON --useExplicitPDFDerivativesMode Whatever \
  --relaxationFactor 0.5 --maximumStepSize 0.2 --failureExitCode -1 \
  --fixedVolumeROI ${FIXED_IMAGE_ROI} --movingVolumeROI ${MOVING_IMAGE_ROI} \
  --numberOfHistogramBins 50 --numberOfMatchPoints 10 --debugNumberOfThreads 4

Note: all parameters are the default settings except numberOfIterations (default 1500), maskProcessingMode (default NOMASK).

• execution time: ~12 min. Breakdown for Case01: CenterOfHead transform initialization: 343s, ROIAUTO mask detection: 139s + 181s (fixed + moving), Rigid registration: 46s

FSL FLIRT

• FSL FLIRT
• Technical details
• parameters:

flirt -in ${TIME_POINT_2} -ref ${TIME_POINT_1} -omat ${FLIRT_TRANSFORM} -out ${RESAMPLED_IMAGE} -dof 6 -v

• execution time: ~4 min

Results

BRAINSFit

• • Case01

• 
• 
• 

• • Case03

• 
• 
• 

• • Case04

• 
• 
• 

• • Case10

• 
• 
• 

FSL FLIRT

• • Case01

• 
• 
• 

• • Case03

• 
• 
• 

• • Case04

• 
• 
• 

• • Case10

• 
• 
• 

Conclusions

Limitations of the Slicer registration tools

• RigidRegistration (the following are trivial to fix in the code)

• • Number of samples is specified as an absolute value, better if it is a relative value to the total number of the image voxels
  • Not possible to specify input mask, or sampling threshold for metric voxels
  • Not possible to specify the number of threads, while variable number of threads used in registration may result in irreproducible results (see ITK bug #9222

• RegisterImages

• • Output transform should be loaded manually via Transform IO (convenience). Not trivial to fix, since RegisterImages is generic to use the same output transform for different types of registration (e.g., Rigid, Affine and BSpline), while BSpline cannot be loaded in Slicer via transform IO

• all of the tools implemented in Slicer require to specify the max number of iterations, which essentially requires the user to monitor convergence (metric value while iterating can be found in Slicer error log), and increase the number of iterations if the satisfactory result is not achieved. Not practical for interactive application

• not possible to specify the similarity metric: apparently, FLIRT is able to get good result using cross correlation