[Insight-developers] changes to MI registration

Lydia Ng lng@insightful.com
Wed, 6 Mar 2002 12:23:50 -0800


Why:
=3D=3D=3D=3D
As per Kitware/GE code review, registration was to change
so that registration components can be connected at run-time
instead of being compile-time template parameters.

As such, all registration components were to de-templated
and all ImageToImageXXXXXRegistration classes are to be
replaced by one generic ImageRegistrationMethod class.


Changes:
=3D=3D=3D=3D=3D=3D=3D=3D
Registration components (metric,optimizer,transform) has
been now de-templated.

Previously, exisiting MI registration classes
ImageToImageAffineMutualInformationGradientDescentRegistration
ImageToImageRigidMutualInformationGradientDescentRegistration
are now defunct and will be removed.

The upshot is that if you want to use MI registration=20
with those combination of components you have to connect
them up yourself.

Tests ImageRegistrationMethodTest_13 and
ImageRegistrationMethodTest_14=20
are examples how to use the new framework to get back the=20
same functionality that were previously provided by the above
MI registration classes.

It seems such a pity to lose the docs I had with MI
registration classes - I've moved them into the test files.


- Lydia



=20