You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've noticed that when I set interpolation order of reg_aladin to nearest neighbour or trilinear, the output image which was initially non-negative, may contain negatives. To me, this implied that the interpolation was likely cubic.
I've created a small bash test to illustrate my point. It does the following:
Downloads an example nifti from Slicer's BRAINSTools module
Applies a translation of 10.5mm, to create the moved image
The moved image is registered with reg_aladin with NN interpolation
The transformation matrix from the registration is used with reg_resample for different types of interpolation.
Here is the output:
source min: 0.0
moved min: 0.0
registered NN min: -21.0
resampled NN min: 0.0
resampled LIN min: 0.0
resampled CUB min: -21.0
For anyone who has the same question, I believe this is actually the intended behavior as mentioned in the help "Interpolation order to use internally to warp the floating image". Interp will only be used to do internal interpolation not to get the final warped image. You can make changes in https://github.com/KCL-BMEIS/niftyreg/blob/master/reg-lib/_reg_aladin.cpp#L663 to do whatever you want.
I've noticed that when I set interpolation order of
reg_aladin
to nearest neighbour or trilinear, the output image which was initially non-negative, may contain negatives. To me, this implied that the interpolation was likely cubic.I've created a small bash test to illustrate my point. It does the following:
moved
imagereg_aladin
with NN interpolationreg_resample
for different types of interpolation.Here is the output:
Have I misunderstood something or is this a bug?
The script is as follows:
The text was updated successfully, but these errors were encountered: