Local Simulation
The fastest sanity check for LAV2 remains the local MuJoCo runner.
Quick Start
Install the project first via Installation, then launch the local runner:
uv run lav2
You can also invoke the module directly:
uv run python -m lav2.controller
Runtime Notes
- The interactive runner expects the MuJoCo scene under
lav2/assets/mjcf/scene.xml. - Mode
0(default) runs the rotor flight stack and mode1runs the tracked vehicle stack. Set the initial mode via--mode(e.g.,uv run lav2 --mode 1). You can switch modes at runtime via a key press. - If the simulation saturates or diverges, check in order: (1) that
lav2/assets/mjcf/scene.xmland referenced mesh files are present; (2) that the MuJoCo rendering backend is functional; (3) controller gains inVehicleParams(especially position/velocity P-gains and integration limits); (4) rotor parameters such asmax_rpm, thrust coefficient, and motor time constants.
What To Read Next
- Read Assets to see where the MuJoCo scene, MJCF robot file, meshes, and USD assets are stored.
- Read Dynamics to understand how VehicleParams, RotorDynamics, and TrackDynamics define the simulated actuator behavior.
- Read Controllers to trace the control loop built around FlightController, TrackController, and Mixer.