Penetration instead of collision #2686
Unanswered
NadeenElh
asked this question in
Asking for Help
Replies: 1 comment 5 replies
-
Beta Was this translation helpful? Give feedback.
5 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi!
I'm a graduate student and I'm using MuJoCo for my research which requires peg-in-hole disassembly using Reinforcement Learning.
My setup
MuJoCo: 3.3.2 | Python | Ubuntu 20.04
My question
I'm testing using this model and the collision between the peg and hole worked fine when they were in their own xml file.
But, when I added a robot arm (Kuka IIWA 14), and ran the RL algorithm, the peg started penetrating the hole.
The peg is redefined as a child of the last link of the robot arm, like an extra link.
Is the penetration now due to the kinematic characteristics of the robot arm itself and the peg being a child part or is it an error in definition somehow? Is contact (contact forces) detectable between the peg and hole in this setting or does the peg have to be a (dynamically) free object for collision/contact to be valid?
If there's no way for it to be valid with this setting, would it be better to make it a separate body from the robot arm and use a weld equality on two sites instead?
I've attached the XML file.
Model:
minimal XML
Beta Was this translation helpful? Give feedback.
All reactions