[ITK Community] Writing of multiple transforms to file

[Andras Lasso]

Thanks for the quick response. Maybe you can help with the following more specific questions, too:

*         If I add an inverse transform then what will be written to file: A. the original transform with a flag that indicates that it has to be inverted or B. the computed (usually lossy) inverse?

*         Can I add a CompositeTransform to CompositeTransform (compTransform1->AddTransform(compTransform2))? Can it be saved to file?

*         Can I add an inverted CompositeTransform to a CompositeTransform (compTransform1->AddTransform(compTransform2->GetInverseTransform()))? Can it be saved to file?

Andras

From: Matt McCormick [mailto:matt.mccormick at kitware.com]
Sent: Wednesday, March 12, 2014 12:57 PM
To: Andras Lasso
Cc: community at itk.org
Subject: Re: [ITK Community] Writing of multiple transforms to file

Hi Andras,

The HDF5 transform format [1] can support Composite [2] transforms.

HTH,
Matt

[1] http://www.itk.org/Doxygen/html/classitk_1_1HDF5TransformIOTemplate.html

[2] http://www.itk.org/Doxygen/html/classitk_1_1CompositeTransform.html

On Wed, Mar 12, 2014 at 12:22 PM, Andras Lasso <lasso at queensu.ca<mailto:lasso at queensu.ca>> wrote:
Hi all,

We are improving the non-linear transform support in 3D Slicer and looking for a file format that can store a list of transforms. The difficulty is that we don't want to lose information when writing the transforms to file, groups of transforms may be inverted in the list, for example:
T1 * inv(T2) * inv(T3 * inv(T4 * T5 * T6)) * T7

Is there a way to save such a transformation chain into an ITK transform file? (or there are any plans or interest in ITK for supporting this in the future?)

Andras


_______________________________________________
Community mailing list
Community at itk.org<mailto:Community at itk.org>
http://public.kitware.com/cgi-bin/mailman/listinfo/community

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/community/attachments/20140312/9d68d8f7/attachment-0002.html>