MuJoCo Warp documentation: Warmstart.
PiperOrigin-RevId: 856608941 Change-Id: Iae1bd0a3916d98affff4d5dbb442f9d951622e52
This commit is contained in:
committed by
Copybara-Service
parent
c92746641d
commit
d86acd7e12
@@ -622,3 +622,15 @@ can be accomplished by deleting the directory ``~/.cache/warp`` or via Python
|
|||||||
Yes. Please see Warp's
|
Yes. Please see Warp's
|
||||||
`Ahead-of-Time Compilation Workflows <https://nvidia.github.io/warp/codegen.html#ahead-of-time-compilation-workflows>`__
|
`Ahead-of-Time Compilation Workflows <https://nvidia.github.io/warp/codegen.html#ahead-of-time-compilation-workflows>`__
|
||||||
documentation for details.
|
documentation for details.
|
||||||
|
|
||||||
|
Differences from MuJoCo
|
||||||
|
=======================
|
||||||
|
|
||||||
|
This section notes differences between MJWarp and MuJoCo.
|
||||||
|
|
||||||
|
Warmstart
|
||||||
|
---------
|
||||||
|
|
||||||
|
If warmstarts are not :ref:`disabled <option-flag-warmstart>`, the MJWarp solver warmstart always initializes the
|
||||||
|
acceleration with ``qacc_warmstart``. In contrast, MuJoCo performs a comparison between ``qacc_smooth`` and
|
||||||
|
``qacc_warmstart`` to determine which one is utilized for the initialization.
|
||||||
|
|||||||
Reference in New Issue
Block a user