Behavior different when simulating robot using Isaac Sim GUI and when launching through Isaac Lab. Also, IdealPDActuatorCfg throws an error #1909
Replies: 13 comments
-
Thank you for posting this. Could you provide more details on how are you are using Isaac Lab, and a script to reproduce the behavior you mention? Regarding the NaN output, it is likely due to the fact that the robot didn't get spawned in the first place. Could you provide your error log so we can investigate? Thanks. |
Beta Was this translation helpful? Give feedback.
-
Hello @RandomOakForest , Sure. from future import annotations import torch import omni.isaac.lab.sim as sim_utils Pre-defined configsfrom omni.isaac.lab_assets.husky import HUSKY_CFG # isort: skip # Change this @configclass
)
class HuskyEnv(DirectRLEnv):
If you require additional information, I'd be happy to send it separately. |
Beta Was this translation helpful? Give feedback.
-
Hi @RandomOakForest, |
Beta Was this translation helpful? Give feedback.
-
Thanks for following up. What is the error message you get? Could you share the log or stdout with the error? Thanks |
Beta Was this translation helpful? Give feedback.
-
Hi @RandomOakForest, tensor([nan], device='cuda:0') What I noticed is, If I keep damping to 10.0, It does not show an error but the moment I make it 20.0, there is this error for IdealPDActuatorCfg. I briefly noticed that with high damping, robot kind of flies off and is not spawned again. Additionally, when I set the target joint velocity of left wheels to 12.0 rad/s and right wheels to 4 rad/s, they dont reach those velocities. Here are the values of joint velocities (This happens even with ImplicitActuatorCfg): tensor([[ 4.9236, 12.1095, 3.7108, 6.4523]], device='cuda:0') tensor([[ 6.4652, 6.5897, 3.5293, 7.8635]], device='cuda:0') tensor([[ 6.4083, 11.4830, 6.3876, 10.1888]], device='cuda:0') |
Beta Was this translation helpful? Give feedback.
-
Hi @RandomOakForest, |
Beta Was this translation helpful? Give feedback.
-
Hi @RandomOakForest , |
Beta Was this translation helpful? Give feedback.
-
Thanks for following up. There is a related conversation with suggestions that may help. Having said that, we are able to repro the error message you get in some examples we are working on. Will keep you posted. |
Beta Was this translation helpful? Give feedback.
-
How are you getting those joint velocities? The tensors you're showing look like quaternions, not velocities. Are you using |
Beta Was this translation helpful? Give feedback.
-
Hi @StrainFlow , |
Beta Was this translation helpful? Give feedback.
-
Hi @StrainFlow and @RandomOakForest, |
Beta Was this translation helpful? Give feedback.
-
Hi Everyone, |
Beta Was this translation helpful? Give feedback.
-
Following up on this. Regarding the original issue on the different actuators, it seems the way they are implemented they differ in how they handle the step in simulation. However, if you have small enough dt, both should yield similar results. I will move this post to a discussion for the team to continue to follow up. Thanks for your interest in Isaac Lab. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Describe the bug
Hi,
I've setup an RL task for a mobile robot with Isaac Lab.
What I've noticed is that when I test the motion through Isaac Sim GUI, behavior looks reasonable. However, when launching through Isaac lab with the exact same settings, behavior is drastically different. I am implementing velocity control so I am setting stiffness to 0.0 and damping to 20.0.
Additionally If I use IdealPDActuatorCfg intstead of ImplicitActuatorCfg, robot does not get spawned and throws Nan if I try to access joint velocity values
Steps to reproduce
Physics scene settings in Isaac Sim:
Solver: PGS
dt: 200
physics material: static_friction - 2.0
dynamic_friction - 1.0
restitution - 0.0
System Info
Additional context
Add any other context about the problem here.
Checklist
Acceptance Criteria
Add the criteria for which this task is considered done. If not known at issue creation time, you can add this once the issue is assigned.
Beta Was this translation helpful? Give feedback.
All reactions