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
As far as I understood the contact.velRef is not updated in FootstepPlan::updateInitialTransform function. So I think that this is a bug of the LIPM. I like to suggest adding the following commands to the mentioned function.
This velocity is only set in PlanInterpolator::runWalking_() and it should indeed be updated by FootstepPlan::updateInitialTransform(), otherwise ModelPredictiveControl::updateVelCost() uses the velocity in the wrong frame.
I agree with your fix. Here is how it checks for me:
Let's write v' the new contact.refVel after update and v the old one
We want v'_C' in the new contact frame C' to be the same as v_C in the old contact frame C
Old and new contact frame orientations are, by construction: R_0_C' = R_0_C * R_delta
Hello @stephane-caron
As far as I understood the
contact.velRef
is not updated inFootstepPlan::updateInitialTransform
function. So I think that this is a bug of the LIPM. I like to suggest adding the following commands to the mentioned function.The text was updated successfully, but these errors were encountered: