[Insight-developers] Change in ITK[master]: ENH: Adding simple registration method class.

[Matt McCormick]

On Fri, Oct 14, 2011 at 11:04 AM, Nicholas Tustison <ntustison at gmail.com> wrote:
> I'm fine with separating out the method class.
>
> Regarding your naming requests, it seems a
> little overkill to name the class (or any class)
> something like
>
> itkAffineTransformUsingMututalInformationWithGradientDescentOptimizationFollowedByGaussianSmoothingonUpdateDisplacementFieldTransformUsingANTSCrossCorrelationWithGradientDescentOptimizationOhAndDoNotForgetThatWeAreUsingTransformAdaptorsForMultipleLevels.h, *.hxx

:-)

'Simple' could be removed, too but then we end up with a naming conflict.

It seems we need a tag to identify the new registration classes and
avoid naming conflicts.

The new registration classes have been so far tagged with
'HighDimensional' or 'Object'.  HighDimensional is long and may be not
descriptive of the significant changes to many of the classes.
'Object' is not descriptive and confusing because.

Although acronyms are generally bad form in ITK, it may be required in
this case to get something that is both succinct and descriptive?  We
do use 'ITK' regularly after all.  'ANTS' may be too easy to confuse
with the UPenn ANTS code that is out there?  'HD' has a good history
in the radio industry for not really standing for anything other than
the next generation.  Or, like the phone industry, 'Gen2'?  I am
having trouble channeling my inner MRI researcher for coming up with
good acronyms.

Some ideas:

- HD
- v4
- ANTS
- BUGS
- UPenn
...