-
Notifications
You must be signed in to change notification settings - Fork 22
Description
I'd like to compute some tracking metrics on the mujoco rollout of the policy. I tried logging the contents of /joint_states
using
ros2 topic echo --full_length /joint_states
but that does not give me the root transform.
I also tried writing a script that runs inference in MuJoCo directly (without using ROS), but without success. Does your first observation in IsaacLab and in MuJoCo match exactly? Mine has some slight differences (on the order of 0.01), but I would guess domain randomization would make the policy robust to those fluctuations.
I also noticed that your ROS MuJoCo runs at a time step of 0.002, while IsaacLab runs at 0.005, so I suppose that there is more to getting the policy to work in MuJoCo than simply matching the joint indices between MuJoCo and the order that the policy expects (plus the parameters like action scale, offset, stiffness, and damping). For sim2sim, is the following what your system is doing:
- MuJoCo is running at 500Hz
- There's a separate controller also running at 500Hz that calculates the torques based on the latest action and sends them to MuJoCo
- The policy is running at 50Hz, setting the PD targets of the controller
?