fix(facts): use vertical m for distance-sensor up/down ranges#14617
fix(facts): use vertical m for distance-sensor up/down ranges#14617Bartok9 wants to merge 1 commit into
Conversation
Build ResultsPlatform Status
All builds passed. Pre-commit
Pre-commit hooks: 0 passed, 0 failed, 0 skipped. Test Resultslinux-coverage-integration: 33 passed, 0 skipped Code Coverage
Artifact Sizes
Updated: 2026-07-18 21:22:21 UTC • Commit: fa6e85c • Triggered by: Android |
92f6a49 to
1127683
Compare
Pitch-up and pitch-down rangefinder distances are vertical axis lengths. Tagging them as plain "m" makes Vertical Distance units settings skip them.
1127683 to
fa6e85c
Compare
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #14617 +/- ##
==========================================
+ Coverage 25.47% 31.51% +6.04%
==========================================
Files 769 785 +16
Lines 65912 66968 +1056
Branches 30495 31013 +518
==========================================
+ Hits 16788 21105 +4317
+ Misses 37285 31568 -5717
- Partials 11839 14295 +2456
Flags with carried forward coverage won't be shown. Click here to find out more. Continue to review full report in Codecov by Harness.
🚀 New features to boost your workflow:
|
Summary
rotationPitch90(Up) androtationPitch270(Down) units asvertical m.Motivation
Plain
mis treated as horizontal distance by FactMetaData. Up/down rangefinder ranges are vertical lengths; they should honor the Vertical Distance units setting. Lateral yaw ranges and min/max staym.Verification
Notes
AI-assisted; human-reviewed. Spec:
specs/qgroundcontrol/2026-07-17-1.md(Composer 2.5 Standard intent).