Summer2009:Registration reproducibility in Slicer

• 

  Project Week Main Page

• 

  Transform for test data/GUI registration

• 

  Transform for test data/CLI registration

Key Investigators

• BWH: Andriy Fedorov, Steve Pieper, Tina Kapur
• GE: Jim Miller
• Kitware: Luis Ibanez
• EAB: Bill Lorensen

Objective

Rigid registration in general, and RigidRegistration module of Slicer3 in particular, are important workflow components for a number of applications. Two issues are of our interest:

1. We found gross inconsistency between the result of using rigid registration module on volumetric brain MRI in GUI vs command line invocation.
2. There is also significant difference between command line invocations of the module on different platforms.

The issue has been confirmed independently by Andriy, Bill, Jim and Steve. It was also confirmed by Kilian. The problem is thoroughly documented in Slicer3 bug 416.

We would like to understand the source of this inconsistency, together with the understanding what is reasonable to expect expect in terms of reproducibility from such complex numerical codes like rigid registration.

Approach, Plan

1. use clinical data to demonstrate the problem, once again
2. collect feedback from registration experts
3. create a test that demonstrates the problem, and add it to the ITK dashboard
4. Questions to consider:

• • is reproducibility a function of the architecture? is it dependent on multi-threading? can it be quantified and estimated?
  • what is the correct way to test reproducibility for this kind of applications?

Progress

• added testing mode to RigidRegistration to measure the maximum difference
• abused Slicer3 dashboard to collect the magnitude of difference on various platforms

Test setup

1. Get images and transform from Slicer3 trunk: fixed image: http://svn.slicer.org/Slicer3/trunk/Testing/Data/Input/MRMeningioma0.nrrd moving image: http://svn.slicer.org/Slicer3/trunk/Testing/Data/Input/MRMeningioma1.nrrd transform: http://svn.slicer.org/Slicer3/trunk/Testing/Data/Input/MRMeningioma01.tfm 2. To get the transform in GUI, go to RigidRegistration module, use the default parameters to initialize (see figure), EXCEPT reduce iteration cout from the default to "100,100,50,20" 3. To get the transform with CLI, here's the command line you need to run: Slicer3 --launch RigidRegistration --fixedsmoothingfactor 0 --movingsmoothingfactor 0 --histogrambins 30 --spatialsamples 10000 --iterations 100,100,50,20 --learningrate 0.01,0.005,0.0005,0.0002 --translationscale 100 --outputtransform ./RigidRegistrationTransform-CLI.txt MRMeningioma0.nrrd MRMeningioma1.nrrd 4. To get the actual difference in the corner of your image using one transform vs another, you can run RigidRegistration in the testing mode. Testing feature is not available in stable release -- you need to download nightly, or use your build from scratch!. In testing mode, initial transform is NOT used as the initial tranform, but is simply a ``ground truth transform to ustest reproducibility. Slicer3 --launch RigidRegistration --testingmode --initialtransform RigidRegistrationTransform-GUI.tfm --fixedsmoothingfactor 0 --movingsmoothingfactor 0 --histogrambins 30 --spatialsamples 10000 --iterations 100,100,50,20 --learningrate 0.01,0.005,0.0005,0.0002 --translationscale 100 --outputtransform ./RigidRegistrationTransform-CLI.txt MRMeningioma0.nrrd MRMeningioma1.nrrd

RigidRegistration initialization in GUI

References

• Mantis entry for bug 416