-
Notifications
You must be signed in to change notification settings - Fork 45
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
[BUG] Initialization Velocities Scale with Distance from the Origin #1
Comments
Hi @zalo, Sorry for the late response. Great job with Mujoco viewer! It looks very nice. As a workaround, I can propose placing all the ants at the same start pose and render with displacement only their visual meshes. @mmacklin could it be because of the way in dflex joint_qd are not in the center of mass in a world frame, but in a twist representation?
|
Ah, interesting! That does indeed seem to fix the issue. I also note that the separation of the agents is disabled when not visualizing: Perhaps this behavior is a known issue? |
Dividing initial velocities by their distance from the origin appears to normalize the velocities across the spread, even in visualization. I tested this by appending : / torch.clamp_min(self.start_pos[env_ids, 2:3], 1.0) to the end of this line, but using the magnitude is probably preferable. 👍 |
Warp envs syntax and added doubleqcritic
@ViktorM
While writing a MuJoCo-Viewer Renderer for DiffRL, I noticed that initialization velocities appear to scale the farther out an actor is from the origin.
This behavior appears to occur in the original .usd's as well, so I don't believe it's an artifact of the visualization.
ExplodingVelocities.mp4
The early termination threshold also seems more sensitive far away from the origin.
I tested setting the stochastic initialization velocity to a constant and the velocities were still amplified far away from the origin, so I believe this is something deeper within the fundaments of dflex...
The text was updated successfully, but these errors were encountered: