# Control point grid output from NiftyReg not loaded correctly

**URL:** <https://discourse.slicer.org/t/control-point-grid-output-from-niftyreg-not-loaded-correctly/34967>\
**Category:** Development\
**Tags:** registration, segmentation, data-loading\
**Created:** [March 19, 2024, 7:20am UTC](https://discourse.slicer.org/t/control-point-grid-output-from-niftyreg-not-loaded-correctly/34967 "2024-03-19T07:20:46Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![koeglfryderyk](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/koeglfryderyk/32/14638_2.png) [@koeglfryderyk](https://discourse.slicer.org/u/koeglfryderyk)\
**Post date:** [March 21, 2024, 7:59am UTC](https://discourse.slicer.org/t/control-point-grid-output-from-niftyreg-not-loaded-correctly/34967/2 "2024-03-21T07:59:23Z")

</div>

I actually needed the displacement field anyway, and the way to get it and use it is described in this [issue](https://discourse.slicer.org/t/deforming-with-niftyreg-is-different-than-deforming-in-slicer/34992/3)

---

_[View the full topic](https://discourse.slicer.org/t/control-point-grid-output-from-niftyreg-not-loaded-correctly/34967)._
