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

EKF2: range measurement rejection in rain/fog #23579

Merged
merged 4 commits into from
Aug 30, 2024
Merged

Conversation

haumarco
Copy link
Contributor

When there's rain or fog the range sensor can provide wrong distance measurements. The goal was to create somewhat of a sanity check for the distance sensor while moving horizontally. Currently we only have the kin-consistency check without horizontal movement.

The current implementation is dependent on a new param and the magic hardcoded factor 2.

@haumarco haumarco added the EKF2 label Aug 20, 2024
@haumarco haumarco requested review from dagar and bresch August 20, 2024 09:49
Copy link
Member

@bresch bresch left a comment

Choose a reason for hiding this comment

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

I generally like the concept, but I think that the check should have its own class. It shares absolutely nothing with the kinematic consistency check (except _time_last_update_us) and make that class just less readable (e.g.: the setParams is for both but the update update function is for the kinematic check only).

@haumarco haumarco force-pushed the range_blockage_fog_rain branch from 09311d4 to 2ceafe6 Compare August 23, 2024 11:14
@haumarco haumarco marked this pull request as ready for review August 23, 2024 11:32
Copy link
Member

@bresch bresch left a comment

Choose a reason for hiding this comment

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

Please also cover the logic with some unit tests. Show that:

  • it doesn't trigger in normal operation
  • it triggers when the conditions are met
  • the fault clears when back to normal

@haumarco haumarco force-pushed the range_blockage_fog_rain branch from 2ceafe6 to a5f7d95 Compare August 30, 2024 09:17
Copy link
Member

@bresch bresch left a comment

Choose a reason for hiding this comment

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

I think it looks good now. In the future it would be nice to add some logging of the internal values at some point as it might get difficult to see which of the range finder checks are failing and why.

@bresch bresch merged commit 7dcea6b into main Aug 30, 2024
55 checks passed
@bresch bresch deleted the range_blockage_fog_rain branch August 30, 2024 15:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants