domains / families / design / stepinfo-3d

stepinfo-3d

separate

Use this skill when computing 3D step-response performance metrics for point-to-point drone flight — rise time, settling time, percent overshoot, and steady-state error based on Euclidean distance to the final target. Use instead of 1D stepinfo for any flight where all three position axes move simultaneously.

When to use

• | Scenario | Metric to use | |---|---| | Pure z-step (hover, takeoff, land) | 1D `stepinfo` on `z` signal | | Diagonal flight (x, y, z all change) | `stepinfo_3d` on 3D Euclidean distance | | Circular / figure-eight trajectory | Neither —…

When not to use

• **Assumes point-to-point flight** — the drone starts away from a fixed target and converges. For circular trajectories, use RMS or cumulative error instead.
• `dist_initial` is the distance at `t[0]`. If the drone starts at the target (hover command), all metrics return `0`.
• Overshoot is defined by **distance**, not by crossing the target in one axis — the drone must physically move farther from the target after settling to register overshoot.
• If the settling band is never entered (common for very short commands where d0 is small, making `band = 0.02 × d0` only a few centimetres), `Overshoot_pct` returns `0.0` — the drone approached the target without oscillating past it.

Skill page

Source