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

Support for MJCF Files #8634

Open
jleibs opened this issue Jan 9, 2025 · 0 comments
Open

Support for MJCF Files #8634

jleibs opened this issue Jan 9, 2025 · 0 comments
Labels
enhancement New feature or request 🪵 Log & send APIs Affects the user-facing API for all languages

Comments

@jleibs
Copy link
Member

jleibs commented Jan 9, 2025

MJCF is a common file format for kinematic robot (and other general physics simulation) descriptions.

It's part of the MuJoCo physics engine.

Although not as widely used as URDF it has some nice properties and shows up frequently in simulators:

At a minimum we should have a reference dataloader implemented in Python or C++ which loads an MJCF project into Rerun by translating to a set of Transforms and Meshes.

However, coercing into the Rerun hierarchy and expanding transforms loses some of the fidelity that could be expressed. This could be a good opportunity to take a look at #1533 and think about some form of Viewer-derived joint-space -> Transform conversion leveraging the MJCF model.

In an ideal world a user would be able to publish a single component containing an array of joint-positions at each time stamp and have the robot model fully articulate in the correct way.

@jleibs jleibs added enhancement New feature or request 🪵 Log & send APIs Affects the user-facing API for all languages labels Jan 9, 2025
@jleibs jleibs changed the title Support or MJCF Files Support for MJCF Files Jan 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request 🪵 Log & send APIs Affects the user-facing API for all languages
Projects
None yet
Development

No branches or pull requests

1 participant