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	126	March 21, 2024
Displacement vector from a deformable reg; WARNING inverse innaccuate Support transforms	4	513	January 31, 2019
Interpolate volumetric mesh from deformation vector field image volume Support	2	332	September 4, 2023
apply a deformable registration from a REG-DICOM file Support	5	594	May 29, 2022
Displacement field and deformable registration: Unexpected folded “mirror” images outside the fixed volume Support transforms	2	1138	December 14, 2018

Deforming with NiftyReg is different than deforming in Slicer

Related topics