[Insight-developers] Registration classes

[Asad A. Abu-Tarif]

Hi,
Why not have registration estimators also derive from
the same class?
Most registration algorithms don't care what estimator
you use as long as they do the same thing.
This way, if someone implements a new optimization algorithm
(say a new robust estimator or a new way of maximizing the MI), 
he/she doesn't need to also write a new registration algorithm 
specially for it. He/she can just pass it to an existing registration 
algorithm that uses the same 'kind' of estimator.

Also, most estimators take two sets of correspondences 
(geometrical features, raw data, ..etc) and minimize/maximize some
metric
for them. So, they do have things in common!!

The SetEstimator member function (that should be added) of any
registration 
algorithm should check whether the estimator to be set takes the same
type of correspondences that specific registration algorithm
is passing to the estimator. If not, it can return an error status.

Each estimator class should have a member function like
(GetCorrespondencesType)
that the registration algorithm can call!!

Regards,
Asad

===============================================
Asad A. Abu-Tarif
Computer Engineering.
PhD Candidate, Rensselaer Polytechnic Institute
Research Assistant, NYS Center for Automation Technologies.
tarifa@rpi.edu
===============================================

Luis Ibanez wrote:
> 
> The registration classes have been modified
> to factorize some common aspects.
> 
> Now they derive from itkRegistrationMethod,
> which derives from itkProcesObject.
> 
> itkRegistrationMethod receives a Traits class,
> pretty much as itkMesh does.
> 
> Additionally, the name of the optimization method
> was added at the end of the registration method name.
> 
> The PointSet to Image registration methods still
> need some debuggin to verify that they are doing
> the right thing at run time, but by now they are
> compiling fine.
> 
> Some of these methods will be available in the
> example at /Examples/ImageRegistration.
> 
> There's still some need for communication between
> the registration methods and the GUI....
> 
> Luis
> 
> _______________________________________________
> Insight-developers mailing list
> Insight-developers@public.kitware.com
> http://public.kitware.com/mailman/listinfo/insight-developers