Allow more than 1 activation state per actuator, but only for dyntype user.

Fixes #305.

PiperOrigin-RevId: 486597273
Change-Id: I3eb806f60949e68ebe6cbe35a6e66218a167ed45
This commit is contained in:
Yuval Tassa
2022-11-07 01:42:18 -08:00
committed by Copybara-Service
parent 0514010928
commit 36b30e4500
20 changed files with 271 additions and 37 deletions
+5
View File
@@ -3019,6 +3019,11 @@ specify them independently.
it is defined in the kinematic tree; its orientation cannot be changed in the actuator definition.
:at:`user`: :at-val:`real(nuser_actuator), "0 ... 0"`
See :ref:`CUser`.
:at:`actdim`: :at-val:`real, "-1"`
Dimension of the activation state. The default value of ``-1`` instructs the compiler to set the dimension according
to the :at:`dyntype`. Values larger than ``1`` are only allowed for user-defined activation dynamics, as native types
require dimensions of only 0 or 1. For activation dimensions bigger than 1, the *last element* is used to generate
force.
:at:`dyntype`: :at-val:`[none, integrator, filter, muscle, user], "none"`
Activation dynamics type for the actuator. The available dynamics types were already described in the :ref:`Actuation
model <geActuation>` section. Repeating that description in somewhat different notation (corresponding to the mjModel