-
Notifications
You must be signed in to change notification settings - Fork 919
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Adds documentation on the frames for asset data #742
Conversation
source/extensions/omni.isaac.lab/omni/isaac/lab/assets/rigid_object/rigid_object_data.py
Outdated
Show resolved
Hide resolved
world frame unless otherwise specified. | ||
|
||
For a rigid body, there are two frames of reference that are used: | ||
|
||
- Actor frame: The frame of reference of the actor that contains the rigid body. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Shall we mention that this coincides with the Xform on which the rigid body is attached?
I guess people do not necessarily know the concept of actors.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I found xform frame in the docs to be a bit confusion. Left it as actor frame for now.
Co-authored-by: David Hoeller <dhoeller@nvidia.com> Signed-off-by: Mayank Mittal <12863862+Mayankm96@users.noreply.github.com>
Description
This MR adds docstrings in articulation and rigid object data to clarify the exact frames they are reported in. This was previously causing confusion as PhysX reports the transforms in actor frame and velocities in CoM frame. Right now, there is no mechanism to get all this data in the same frame, so the best we can do is document behavior.
Type of change
Checklist
pre-commit
checks with./isaaclab.sh --format
config/extension.toml
fileCONTRIBUTORS.md
or my name already exists there