I’m integrating NiftyReg into an extension. I registered two images with f3d and saved the control point grid (to later get the deformation). However, the grid isn’t loaded correctly into Slicer. In the Data module it says that it has dimensions (55, 55, 26), however, it actually has dimensions (5…

Control point grid output from NiftyReg not loaded correctly

koeglfryderyk (Koeglfryderyk) March 21, 2024, 7:59am 2

I actually needed the displacement field anyway, and the way to get it and use it is described in this issue

Topic		Replies	Views
Deforming with NiftyReg is different than deforming in Slicer Support registration , deformation	3	223	March 22, 2024
Visualize BRAINS control points Support registration	12	877	July 9, 2018
Nifti file sform and Slicer image origin seem to disagree Support	2	1060	July 23, 2019
Unexpected behaviour with control point coordinates outside of Slicer Support	3	233	January 26, 2023
Compare two deformation fields Support	0	206	September 2, 2020