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
On the refactor branch #67 all AAM fitting algorithms using the LucasKanadeStandardInterface are slightly wrong. At the moment they are performing additive, instead of compositional updates!
We have to options to amend this:
Re-implement the solve_all_map and solve_all_ml methods on the previous interface so that they effectively use the "parameter Jacobian" Jp. This might make the functions _solve_all_map and _solve_all_ml quite complicated...
Go back to using the VComposable interface. This would mean that PDMs need to support the previous interface and that ModelDrivenTransforms and PDMs need to handle priors internally.
The text was updated successfully, but these errors were encountered:
In Option 1 - how complicated? I think I prefer option 1. Even if there are basically two subfunctions that do either additive or compositional updates?
On the refactor branch #67 all AAM fitting algorithms using the
LucasKanadeStandardInterface
are slightly wrong. At the moment they are performing additive, instead of compositional updates!We have to options to amend this:
solve_all_map
andsolve_all_ml
methods on the previous interface so that they effectively use the "parameter Jacobian"Jp
. This might make the functions_solve_all_map
and_solve_all_ml
quite complicated...VComposable
interface. This would mean thatPDMs
need to support the previous interface and thatModelDrivenTransforms
andPDMs
need to handle priors internally.The text was updated successfully, but these errors were encountered: