[ITK-users] Fwd: [ITK] 3D registration with level set motion

[CocoM]

No I don't think so, it happens after triggering the registration process
(before any iteration) but just once in the beginning and once in the end.
But actually the deformation field is never updated because the physical
spaces don't match so theoretically it's endless. The exception occurs both
times in the function VerifyInputInformation, called by
UpdateOutputInformation (ProcessObject).

I am not using any optimizer because it's a registration method solving a
PDE iteratively : itkLevelSetMotionRegistrationFilter. It works with a
finite difference resolution scheme, but I can modify the time step,
although I wouldn't really see the point. Any idea?

Thanks,
Marie

 



--
View this message in context: http://itk-insight-users.2283740.n2.nabble.com/3D-registration-with-level-set-motion-tp7590137p7590145.html
Sent from the ITK Insight Users mailing list archive at Nabble.com.