Skip to content
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

[Proposal] Viewer tracking for non-root bodies during RL training #1534

Open
1 of 2 tasks
KyleM73 opened this issue Dec 12, 2024 · 0 comments
Open
1 of 2 tasks

[Proposal] Viewer tracking for non-root bodies during RL training #1534

KyleM73 opened this issue Dec 12, 2024 · 0 comments

Comments

@KyleM73
Copy link
Contributor

KyleM73 commented Dec 12, 2024

Proposal

In commit #59e6c68 the viewer config was added such that the default viewer could track the world origin, the environment origin, or the asset_root during training. I would like to be able to specify the origin of a different body in an articulation or rigid body to track as the origin, for example the end effector in a manipulation task. I am happy to work on this as a PR if there is no concurrent work being done to this effect.

Motivation

The currently documented setup for wheeled navigation tasks suggests using a virtual arm to control the SO2 position of the robot instead of simulating the wheel dynamics directly, since the GPU pipeline currently struggles with smooth cylinders. This is also an easy way to implement quadcopter dynamics, which would suffer from the same problem (the robot is not the root). There is currently no way to track the robot (the way quadrupeds are tracked with asset_root) since the vehicle is not the asset_root in this setup. Additionally, it would be helpful to directly track the end effector in manipulation tasks to observe the grasps in high detail, no matter where the object is located prior to the grasp.

Alternatives

Cameras can be configured to save videos e.g. in a play script that can take any origin. But this is only useful for analyzing policies after the fact, not during training.

Checklist

  • I have checked that there is no similar issue in the repo

Acceptance Criteria

  • Support "asset_body" as an origin mode in the viewer cfg with an optional parameter "body_name" to specify which body to place the origin at for the camera.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant