Hi, thanks for maintaining LIBERO!
I inspected several object assets in upstream LIBERO at commit 8f1084e3132a39270c3a13ebe37270a43ece2a01 and noticed that their collision geoms consistently use density="100", without an explicit body <inertial> element.
Under the standard robosuite configuration (inertiagrouprange="0 0"), this appears to produce very low object masses:
| Object |
Collision geoms |
Inferred mass |
akita_black_bowl |
40 boxes |
5.59 g |
porcelain_mug |
22 boxes |
16.46 g |
glazed_rim_porcelain_ramekin |
25 boxes |
9.66 g |
milk |
4 boxes |
31.67 g |
butter |
1 box |
5.25 g |
These are static calculations from the XML, not measurements of model.body_mass in a running LIBERO environment. For each box, I used:
mass = density × 8 × size_x × size_y × size_z
Here, MuJoCo's box size values are half-extents. I summed the masses of the group-0 collision geoms and excluded the group-1 visual mesh.
Examples
Questions
- Is this low density an intentional choice for numerical stability or easier manipulation, rather than physical realism?
- Does any environment-loading step override these densities or inferred masses?
- Are these objects intended to represent empty packaging or filled products?
- Would it be useful to document the effective masses and, optionally, provide a physically calibrated asset configuration?
I understand that changing the default dynamics could affect compatibility with existing demonstrations and checkpoints. An opt-in configuration could preserve the original benchmark.
I have not yet tested the effect on policy success rates, so this issue is a request to clarify the intended physical parameters rather than a claim about benchmark performance.
Thank you!
Hi, thanks for maintaining LIBERO!
I inspected several object assets in upstream LIBERO at commit
8f1084e3132a39270c3a13ebe37270a43ece2a01and noticed that their collision geoms consistently usedensity="100", without an explicit body<inertial>element.Under the standard robosuite configuration (
inertiagrouprange="0 0"), this appears to produce very low object masses:akita_black_bowlporcelain_mugglazed_rim_porcelain_ramekinmilkbutterThese are static calculations from the XML, not measurements of
model.body_massin a running LIBERO environment. For each box, I used:Here, MuJoCo's box
sizevalues are half-extents. I summed the masses of the group-0 collision geoms and excluded the group-1 visual mesh.Examples
Questions
I understand that changing the default dynamics could affect compatibility with existing demonstrations and checkpoints. An opt-in configuration could preserve the original benchmark.
I have not yet tested the effect on policy success rates, so this issue is a request to clarify the intended physical parameters rather than a claim about benchmark performance.
Thank you!