chenlin/Mujoco_WASM
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Fix a typo: availabe -> available

Browse Source 
PiperOrigin-RevId: 550529748
Change-Id: I1277e096809bc4d66c98da726aa14a0cbfe18e56
This commit is contained in:
Nimrod Gileadi
2023-07-24 05:47:55 -07:00
committed by Copybara-Service
parent 65c827d422
commit 5b4b3415fa
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
doc/overview.rst
+1 -1
View File
@@ -768,7 +768,7 @@ they separate? For semantic as well as computational reasons explained here.
First the similarities. Bodies, geoms and sites all have spatial frames attached to them (although bodies also have a First the similarities. Bodies, geoms and sites all have spatial frames attached to them (although bodies also have a
second frame which is centered at the body center of mass and aligned with the principal axes of inertia). The positions second frame which is centered at the body center of mass and aligned with the principal axes of inertia). The positions
and orientations of these frames are computed at each time step from ``mjData.qpos`` via forward kinematics. The results and orientations of these frames are computed at each time step from ``mjData.qpos`` via forward kinematics. The results
of forward kinematics are availabe in ``mjData`` as xpos, xquat and xmat for bodies, geom_xpos and geom_xmat for geoms, of forward kinematics are available in ``mjData`` as xpos, xquat and xmat for bodies, geom_xpos and geom_xmat for geoms,
site_xpos and site_xmat for sites. site_xpos and site_xmat for sites.
Now the differences. Bodies are used to construct the kinematic tree and are containers for other elements, including Now the differences. Bodies are used to construct the kinematic tree and are containers for other elements, including