Skip to content

Add Open duck mini v2 #144

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

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

apirrone
Copy link

@apirrone apirrone commented Feb 9, 2025

Adds mjcf description for Open Duck Mini v2

Copy link

google-cla bot commented Feb 9, 2025

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

@apirrone apirrone changed the title Open duck mini v2 Add Open duck mini v2 Feb 9, 2025
Copy link
Collaborator

@kevinzakka kevinzakka left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for your contribution @apirrone! I left some comments.

@@ -0,0 +1,19 @@
# Open Duck Mini V2
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @apirrone, can you enhance this README to match other models? (e.g. here). Broadly we need to know where the source of truth was derived from (if from a URDF, a commit SHA + link to the URDF would be great) and what steps were taken to create the MJCF.

@@ -0,0 +1,454 @@
<mujoco model="onshape">
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you do some minimal formatting on this onshape generated XML? We have some instructions here.

</contact>
<worldbody>
<body name="base" pos="0 0 0.22">
<!-- <body name="base" pos="0 0 0.4"> -->
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nit: Remove comments please.

rgba="0.223529 0.219608 0.219608 1" mesh="left_knee_to_ankle_right_sheet"/>
<geom pos="0.01606 0.14365 0.10915" quat="0.707107 -0.707107 0 0" type="mesh"
rgba="0.223529 0.219608 0.219608 1" mesh="left_knee_to_ankle_left_sheet"/>
<geom pos="0 -0.05315 0.00955" quat="0.5 -0.5 -0.5 0.5" type="mesh" rgba="0.247059 0.243137 0.243137 1"
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd prefer if rgbas were converted to materials and material names used instead.

@apirrone
Copy link
Author

Hi @kevinzakka, thanks for the comments !

I actually have a question : The mjcf I added here is a heavily decimated and simplified version intended to be efficient for mjx, but I can also export a pretty one with all the geometry and features.

Which one makes most sense to publish here? Can I upload both ?

Thanks !

@kevinzakka
Copy link
Collaborator

Yes making both is fine. Note visual geometry should not affect MJX performance if you are using primitive geoms for the colliders.

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

Successfully merging this pull request may close these issues.

2 participants