Update M1 Pro with M3 Max benchmarks in MJX docs

PiperOrigin-RevId: 584918133
Change-Id: I442972cdc1f19020e6b5bbc7ff3e98fd556cf125
This commit is contained in:
Yuval Tassa
2023-11-23 10:45:57 -08:00
committed by Copybara-Service
parent f2025c6abf
commit 6a83b86553
4 changed files with 8 additions and 8 deletions
+4 -4
View File
@@ -5787,10 +5787,10 @@ Associate this actuator with an :ref:`engine plugin<exPlugin>`. Either :at:`plug
.. _actuator-plugin-dyntype:
:at:`dyntype`: :at-val:`[none, integrator, filter, filterexact, muscle, user], "none"`
Activation dynamics type for the actuator. The available dynamics types were already described in the
:ref:`Actuation model <geActuation>` section. See also :ref:`actuator-general-dyntype`. If dyntype is
not none, an activation variable will be added to the actuator. This variable will be added after
any activation state computed by the plugin (see :ref:`actuator plugin activations<exActuatorAct>`).
Activation dynamics type for the actuator. The available dynamics types were already described in the :ref:`Actuation
model <geActuation>` section. If :ref:`dyntype<actuator-general-dyntype>` is not "none", an activation variable will
be added to the actuator. This variable will be added after any activation state computed by the plugin (see
:ref:`actuator plugin activations<exActuatorAct>`).
.. _actuator-plugin-actrange: