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

HealthAndArmingChecks: improve messaging for position estimate failure #23711

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

sfuhrer
Copy link
Contributor

@sfuhrer sfuhrer commented Sep 23, 2024

Solved Problem

The messaging in case of estimation failures (local and global position, altitude) is very minimalistic and not end-user friendly.

Solution

  • add "Navigation error" before failure message
  • add description

This is how the notification would look like now:

Expanded event (with description):
image
This is the raw notification, that also pops up in yellow on screen:
image

Changelog Entry

For release notes:

Improvement: HealthAndArmingChecks: improve messaging for position estimate failure

Copy link
Member

@MaEtUgR MaEtUgR left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

While your change is all correct I had in mind to avoid the end user needing to understand what local position actually is. You just need a position estimate for the vehicle to stay in place.

*/
reporter.armingCheckFailure(local_position_modes, health_component_t::local_position_estimate,
events::ID("check_modes_local_pos"),
events::Log::Error, "No valid local position estimate");
events::Log::Error, "Navigation error: No valid local position estimate");
Copy link
Member

@MaEtUgR MaEtUgR Oct 1, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could we simplify by saying local position estimate = (any) position estimate, since we never have a global estimate without a local one? 🤔

Would bring me down to "Positioning insufficient, selected mode can't navigate."
This can be adapted for "global positioning" and "altitude estimate".

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could we simplify by saying local position estimate = (any) position estimate, since we never have a global estimate without a local one?

yes, then why not Navigation error: No valid position estimate

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