ITK/Release 4/Enhancing Image Registration Framework/Proposal for Revised Framework/Composite Transform: Difference between revisions
From KitwarePublic
Jump to navigationJump to search
(→IO) |
(→IO) |
||
| Line 9: | Line 9: | ||
* The TransformFileReader and TransformFileWriter must be modified to manage composite transform. | * The TransformFileReader and TransformFileWriter must be modified to manage composite transform. | ||
== Writing == | |||
* The TransformFileWriter can dynamic_cast to CompositeTransform | * The TransformFileWriter can dynamic_cast to CompositeTransform | ||
** Then extract its internal transforms | ** Then extract its internal transforms | ||
== Reading == | |||
* The TransformFileReader will create the CompositeTransform directly by using the standard Factories. | |||
* Conditional code will deal with reading the N Transform components. | |||
= Changes = | = Changes = | ||
Revision as of 22:19, 25 February 2011
Overview
- CompositeTransform abstracts a concatenation of transform
- Deriving from TransformBase (non-templated)
- Contain a list of pointers to TransformBase
IO
- The TransformFileReader and TransformFileWriter must be modified to manage composite transform.
Writing
- The TransformFileWriter can dynamic_cast to CompositeTransform
- Then extract its internal transforms
Reading
- The TransformFileReader will create the CompositeTransform directly by using the standard Factories.
- Conditional code will deal with reading the N Transform components.
Changes
- Refactor GetJacobians() to manage sparse matrices OR
- Make them obsolete and add to the Transforms the method that provide the service of mapping a point through the Jacobian on the transform. In this way they don't have to be represented explicitly.
