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

EKF3: investigate when GPS is used even though source sets say it should not be used #28968

Open
rmackay9 opened this issue Dec 30, 2024 · 0 comments
Labels

Comments

@rmackay9
Copy link
Contributor

rmackay9 commented Dec 30, 2024

As discussed on PR #28750 there are cases where the EKF source sets are configured so that the EKF is not using the GPS (for position, velocity, altitude or yaw) but the EKF may actually still use it.

The two places we know it does this are:

  1. position and velocity resets where the source is left as "default". GPS is used if it is providing data
  2. automatic setting of the origin

When fixing this issue we should remember that there are potentially situations where the current behaviour is actually convenient for the user. So this issue is not claiming that the behaviour is always a problem. It is certainly a problem sometimes but perhaps not always

@rmackay9 rmackay9 added the EKF label Dec 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant