You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Starting this as more of a reminder that when we pull the system ID model, which has the built-in attitude controller, we need to align out conventions for the rotational velocity representation. This is what I have gathered so far (and think is correct).
PyBullet:
getBaseVelocity --> (translation velocity of body in interial frame, angular velocity of body in inertial frame)
getBasePositionAndOrientation --> (position in inertial frame, quaternion)
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Starting this as more of a reminder that when we pull the system ID model, which has the built-in attitude controller, we need to align out conventions for the rotational velocity representation. This is what I have gathered so far (and think is correct).
PyBullet:
3D Quadrotor (with thrust input):
https://github.com/middleyuan/safe-control-gym/blob/9dc45a47ced86ca3bce86f6fb35582838c278cee/safe_control_gym/math_and_models/transformations.py#L173C1-L187C13
Attitude Controller:
Question: What do we put in the YAML? RPY rates or Ang vel?
Beta Was this translation helpful? Give feedback.
All reactions