Saving Transform Information to DICOM » History » Version 1
Peter Qian, 31/08/2021 03:03 PM
| 1 | 1 | Peter Qian | h1. Saving Transform Information to DICOM |
|---|---|---|---|
| 2 | |||
| 3 | Documentation to describe how the Transform Information is saved into a DICOM file. |
||
| 4 | |||
| 5 | After a fixed and moving image are successfully co-registered, the function |
||
| 6 | <pre><code class="python"> |
||
| 7 | def register_images(image_1, image_2): |
||
| 8 | </code></pre> |
||
| 9 | |||
| 10 | Will produce the moving image(translated) and SITK.CompositeTransform object. The SITK.CompositeTransform will contain a number of transforms in a queue. |
||
| 11 | |||
| 12 | As of the time of development, it can be only observed that Euler3DTransform and Versor3DRigidTransform transform objects are stored into the SITK.CompositeTransform object. |
||
| 13 | |||
| 14 | <pre><code class="python"> |
||
| 15 | def create_fused_model(old_images, new_image) |
||
| 16 | </code></pre> |