-
Notifications
You must be signed in to change notification settings - Fork 440
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
get_state
and set_state
do not involve the pos and quat of the mocap body
#473
Comments
get_state
and set_state
do not involve the pos and quat of the mocap body
Hi, thanks for bringing up this issue to our attention. Our repo is open to the community contribution, but we need to discuss and decide how to incorporate this new change. To make the codebase compatible with default behaviors in existing versions, can you make sure you have an additional flag that opt in / out the mocap body saving? Thanks! @amandlek What do you think of this new feature? |
Actually, I added a default |
Thanks for this contribution! Why don't we start by having you open a PR so we can review the changes? |
I have pulled a request for you to check. Thanks. |
Hi @zichunxx! I'm also trying to add |
Hi Robosuite team,
I constructed an arena including a
mocap
body whose pose should be reset at the beginning of each episode.However, I found
set_state
andget_state
in binding_utils.py only save and loaddata.qpos
anddata.qvel
:robosuite/robosuite/utils/binding_utils.py
Lines 1140 to 1155 in eafb81f
This way of saving and loading MoJoCo data ignores the mocap body information. Thus, I made some changes to set_state, get_state, and from_flattened to contain mocap body information. These changes are sufficient and I have verified them with my code.
If I am right and the repo is open to contributions, I'll pull a request for you to check.
Thanks.
The text was updated successfully, but these errors were encountered: