Use of TransformRigidityPenalty #981
Unanswered
cagatayalici
asked this question in
Q&A
Replies: 1 comment 1 reply
-
Hello, did you understand the reason of this behaviour? I have the same problem but only on Mac OS. I tried the exact same images, same parameters, same Elastix version (5.0.1) on windows and everything works fine... really strange. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi,
I use 3 different parameter maps with a multi-resolution approach to register pretreatment and posttreatment lung CTs to evaluate tumor treatment ( Rigid -> Affine -> B-Spline). I want a specific region defined by a segmentation not to be deformed much during nonlinear registration.
For that, I introduced TransformRigidityPenalty where I used Elastix manual and "A rigidity penalty term for nonrigid registration." as reference. However, I am getting weird results for the registered image as can be seen below:
Below you can see the red region in 3D which I want it not to be deformed:
I only used TransformRigidityPenalty in 3rd parameter map which is B-Spline. Beloware the parameters I used:
And I set the rigidity index of voxels in the moving image via:
parameter_object.SetParameter(2, "MovingRigidityImageName", "moving_rigidity_mask.nrrd"))
With iterations TransformRigidityPenalty gets less however, it is still too high:

What could be the reason for black regions formed in the registered image?
Thank you!
Beta Was this translation helpful? Give feedback.
All reactions