Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AP_GPS: improve reporting of backend inaccurancy #26286

Merged

Conversation

peterbarker
Copy link
Contributor

I didn't find this debug message particularly informative; add more info.

Old:

calculate_moving_base_yaw:372: Exceeded the permitted error margin 29.73999 > 0.052001
calculate_moving_base_yaw:372: Exceeded the permitted error margin 29.73999 > 0.052001
calculate_moving_base_yaw:372: Exceeded the permitted error margin 29.73999 > 0.052001
calculate_moving_base_yaw:372: Exceeded the permitted error margin 29.73999 > 0.052001

New:

calculate_moving_base_yaw:372: Offset=0.300000 vs reported-distance=0.250000 (max-delta=0.050000)
calculate_moving_base_yaw:372: Offset=0.300000 vs reported-distance=0.250000 (max-delta=0.050000)
calculate_moving_base_yaw:372: Offset=0.300000 vs reported-distance=0.250000 (max-delta=0.050000)
calculate_moving_base_yaw:372: Offset=0.300000 vs reported-distance=0.239990 (max-delta=0.047998)

Only affects things when you've got the compile-time debug option enabled

@peterbarker peterbarker force-pushed the pr/gps-backend-debug-improvement branch from 5fe7f3e to 541212d Compare February 22, 2024 03:47
@tridge tridge merged commit cb2f764 into ArduPilot:master Feb 26, 2024
92 checks passed
@peterbarker peterbarker deleted the pr/gps-backend-debug-improvement branch February 27, 2024 04:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants