quadrotor/dt_convergence
A scenario of the Quadrotor model, from tools/trace/scenarios/quadrotor/dt_convergence.cpp.
✓ pass
- The clang run (clang 18.1 optimized) matches the committed trace.
- The gcc run (gcc 13.3 optimized) matches the committed trace.
Shown on
These players show the same trace, with panels chosen to explain it:
- How fast does the error shrink as the step size halves? (Quadrotor V&V Plan)
Every channel
The 3-D view needs WebGL, which this browser does not provide. The plots and the description below show the same trace.
position [m] x y z
velocity [m/s] x y z
body_rates [rad/s] x y z
rotor_speeds [rad/s] rotor 1 rotor 2 rotor 3 rotor 4 dashed: command
rotor_thrusts [N] rotor 1 rotor 2 rotor 3 rotor 4
roll_pitch_yaw [rad] roll pitch yaw
position_error_log10 [log10 m] [0] [1] [2] [3] [4]
t = 0.000 s / 0.640 s
Keys (with the player focused): Space play/pause · ← → one sample (Shift: ten) · Home/End · [ ] speed
0.64 s of the model/quadrotor scenario dt_convergence.cpp, 65 samples every 0.01 s. The panels plot every channel that changes: position, velocity, body_rates, rotor_speeds, rotor_thrusts, roll_pitch_yaw, position_error_log10, with setpoints dashed. Pass criteria: BB-V2 position_order_min >= 3.7.
- ✓ passBB-V2 position_order_min = 3.97 (>= 3.7), computed by the scenario harness
Constant over the run
rotor_speeds_setpoint= [1743, 1610, 1693, 1593] rad/s