-
-
Notifications
You must be signed in to change notification settings - Fork 88
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Question] reset_mocapxbody()
in mocap_set_action()
#113
Comments
Hey @matinmoezzi . I can give you an answer to why the reset function is used but I don't know for certain why you are experiencing extra end-effector displacements. It shouldn't be adding any extra movement to the end-effector body if the mocap is linked to it. Are you experiencing big displacements due to this reset function? You are correct that this is a little redundant but it is a good sanity check to make sure that the mocap is at the same pose as the body it is linked to before adding the displacement action to the mocap. |
Hi @rodrigodelazcano, |
@matinmoezzi yes you are correct, Mujoco will prioritize having a feasible IK configuration before following the mocap body (this is the reason the mocap is reset every step, to make sure that it doesn't grow to unachievable configurations). Do you have the time to implement these changes in a PR? |
Question
Hi, I have a robotic arm and am controlling it using a mocap body and
mocap_set_actoin()
provided inmujoco_utils
. What I am observing is that every time I callmocap_set_action
,reset_mocapxbody()
is called inside it which leads to an undesirable movement of the end-effector as it is trying to change the mocap body position. I am wondering ifreset_mocapxbody
is necessary formocap_set_action
. I understand the purpose of this function but it causes an extra unwanted movement of the end-effector.Thanks.
The text was updated successfully, but these errors were encountered: