I’m integrating NiftyReg into an extension. (one of the goals is to get the computed transformation/deformation into Slicer) I registered two images with reg_f3d and saved the control point grid (to later get the deformation). reg_f3d -ref fixed.nii -flo moving.nii -res warped.nii -cpp controlPoin…

Due to using a wrong intent code, the ITK reader does not know that the vectors store spatial displacement and therefore the vectors are not converted to the correct coordinate system. BUG: Fix read/write of displacement field in NIFTI file format …

Deforming with NiftyReg is different than deforming in Slicer

Support

koeglfryderyk (Koeglfryderyk) March 21, 2024, 7:57am 3

The problem was a bit simpler - the displacement field from NiftiReg already had the correct shape, I only had to change the intent code

Control point grid output from NiftyReg not loaded correctly

Topic		Replies	Views
Control point grid output from NiftyReg not loaded correctly Development registration , segmentation , data-loading	1	121	March 21, 2024
Import displacement field from Matlab Support registration , python , file-import	2	625	December 28, 2021
Using the invert displacement field function Development transforms	3	1626	November 15, 2018
Registration Deformation Export Support registration	35	4076	March 17, 2022
How to save ThinPlateSplineTransform (from IGT Fiducial registration) as a deformation field? Support transforms	1	524	February 4, 2022

Deforming with NiftyReg is different than deforming in Slicer

Related Topics