From 463bc47633f6cb747366fa14f8ad3b11fc564122 Mon Sep 17 00:00:00 2001 From: Yuval Tassa Date: Sat, 18 Jan 2025 12:38:28 -0800 Subject: [PATCH] Clarify that equality constraints defined using the body-based semantic are assumed to be satisfied at ``mjData.qpos0``. PiperOrigin-RevId: 717050088 Change-Id: I02e82cab5a60f0af48f7f921ba9bca11837f8063 --- doc/XMLreference.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/doc/XMLreference.rst b/doc/XMLreference.rst index 141a4d5b..1c856cf3 100644 --- a/doc/XMLreference.rst +++ b/doc/XMLreference.rst @@ -4380,7 +4380,7 @@ ball joint outside the kinematic tree. Connect constraints can be specified in o - Using :ref:`body1` and :ref:`anchor` (both required) and optionally :ref:`body2`. When using this specification, the constraint is assumed to be - satisfied in the configuration in which the model is defined. + satisfied at the configuration in which the model is defined (``mjData.qpos0``). - :ref:`site1` and :ref:`site2` (both required). When using this specification, the two sites will be pulled together by the constraint, regardless of their position in the default configuration. An example of this specification is shown in @@ -4426,8 +4426,8 @@ ball joint outside the kinematic tree. Connect constraints can be specified in o :at:`anchor`: :at-val:`real(3), optional` Coordinates of the 3D anchor point where the two bodies are connected, in the local coordinate frame of :at:`body1`. - The constraint is assumed to be satisfied in the configuration in which the model is defined, which lets the compiler - compute the associated anchor point for :at:`body2`. + The constraint is assumed to be satisfied in the configuration at which the model is defined (``mjData.qpos0``), + which lets the compiler compute the associated anchor point for :at:`body2`. .. _equality-connect-site1: