# Elastix registration toolbox is now available in Slicer

**URL:** <https://discourse.slicer.org/t/elastix-registration-toolbox-is-now-available-in-slicer/165>\
**Category:** Support\
**Tags:** registration, feature\
**Created:** [April 21, 2017, 3:22pm UTC](https://discourse.slicer.org/t/elastix-registration-toolbox-is-now-available-in-slicer/165 "2017-04-21T15:22:52Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![lassoan](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/lassoan/32/13_2.png) [@lassoan](https://discourse.slicer.org/u/lassoan)\
**Post date:** [April 27, 2017, 7:29pm UTC](https://discourse.slicer.org/t/elastix-registration-toolbox-is-now-available-in-slicer/165/6 "2017-04-27T19:29:56Z")

</div>

Time for reading/writing uncompressed binary files is negligible (compared to registration or resampling time), even for very large files. Generating the resampled output and displacement field are time-consuming, so that deserves some attention.

1. I think the resampled output volume is generated twice (once by elastix, at the end of each registration phase; once by transformix at the end - these are redundant).
2. We could avoid id completely by changing Elastix to write ITK-compatible transforms or implement Elastix transform readers in SlicerElastix.

Contributions are welcome!

---

_[View the full topic](https://discourse.slicer.org/t/elastix-registration-toolbox-is-now-available-in-slicer/165)._