[Insight-developers] code production line & registration refactoring

[brian avants]

just a quick email to see that i understand the dev process
that we might want to use for registration refactoring:

1.  check out the current development version of itk

2.  create a topic branch , e.g. registration

3.  develop unit tests using the google unit test style ?

4.  write some code --- local commits etc --- make sure tests pass.

5.  uncrustify , kwstyle , review the code , document , etc.

6.  push to the git topic branch --- or is this where gerrit comes in?

is this correct?  i need to be able to communicate a cohesive dev
procedure to the rest of the development team here and i'm having a
hard time finding a single doc that covers the whole system ....

re: registration refactoring --- see the proposed plan in the shared
google docs :

ITKv4 =>  v4 Proposals

we are currently working on refactoring the linear registration metric classes
such that the transformation of the object (e.g. image) is separated from the
metric computation.    this just means that transformation of the
object happens
outside of the metric ( currently, transformation of the objects happens inside
the metrics ).    there are a number of simplifications that this
strategy will allow ,
including enabling a generalized (e.g. sparse) sampling strategy for
all the metrics,
symmetric / robust registration ( e.g.
http://reuter.mit.edu/index.php/publications/ ) , masked registration
and it can probably be implemented in a backwards compatible way ...

discussing this has been a tcon topic for some time but we havent
gotten to it probably
because there have been so many other lower level bases to cover.

would be happy to schedule a specific tcon time or a separate conf
call if people are
interested.

brian