Closed ajoardar007 closed 1 month ago
The reason is that the bodies in flexcomp inherit the wam
defaults. Can you set the hinge joint directly in the body instead of using the default?
Yup. That seemed to resolve the issue. I guess, even if a joint was not defined for the body (no range), the other attributes that were defined as default were absorbed.
Maybe, later down the line, a rule, similar to how joint-behavior is defined for body
, could be ported to flexcomp
; like how a body
with no joint-range does not throw the same error as for flexcomp
.
Intro
Hi!
I am a graduate student at the University of Waterloo, and I am using MuJoCo for validating my control-scripts before running them on the actual robot.
My setup
Based upon the requirements (by running this cell while displaying all outputs):
absl-py
: 2.1.0,etils
: 1.3.0 (cannot get it to upgrade it any further),numpy
: 1.24.4Environment: Python, Architecture: x86_64, OS: Ubuntu 20.04.6 LTS
What's happening? What did you expect?
Objective: Place flex-material pads on the fingers of the end-effector. Result:
Expected:
Observation: Element
softbody_1
causes no issues in its implementation (I want it to be attached to its parent-body). However,softbody_2
is causing errors, even-though it has been placed significantly far-away to prevent it from initially colliding with any other body.Steps for reproduction
softbody_2
element (flexcomp
element starting at line 173 to 181), and run again.(successful compilation)
Minimal model for reproduction
No mesh-files needed. The MJCF is included in the script for compactness.
Code required for reproduction
Confirmations