ArduPilot / MethodicConfigurator / 37315537808

90%

push

github

fix(autotune): format back-off reasons and complete Heli result metadata

Use the parameter display format when recording the previous staged
gain in back-off reasons. Avoid floating-point artifacts during repeated
reductions without rounding the underlying gain calculations.

Complete the required metadata for all four OMP_M4 AutoTune result
steps to satisfy the configuration schema:
- Pitch and roll rate P/D results (AUTOTUNE_SEQ=2)
- Roll/pitch and yaw angle P results (AUTOTUNE_SEQ=4)

Provide stage-specific explanations, documentation links, review-tool
references and mandatory levels. Mark these steps as externally changed
by ArduPilot AutoTune to enable the existing FC-result import prompt.

Document the OMP_M4 staged sequence separately from general roll/pitch
re-autotuning. Clarify that gain back-off changes only staged New values,
does not upload or save parameters, and leaves acceleration limits
unchanged.

Add regression coverage for stage identifiers, documentation anchors,
result filenames and FC-import metadata.

Signed-off-by: Dr.-Ing. Amilcar do Carmo Lucas <amilcar.lucas@iav.de>

6325 of 7574 branches covered (83.51%)

22682 of 25135 relevant lines covered (90.24%)

2.69 hits per line