-
Notifications
You must be signed in to change notification settings - Fork 2
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
P2 - Address GPS Drift #63
Comments
ideas:
|
Good idea. Where would we make that channge, move base or navigate waypoints? |
I would actually publish a topic in the odom folder, and then reference that other topic from the navigate waypoints (if we so choose to) |
What we should look into:
How to convert GPS to odom frame for verification
How to do GPS -> odom
|
Global seems to be much more off local global |
these are all at spawn btw |
I ran a test where it went to the first few points of load waypoints (although we didn't get over the ramp and drift made the points innacurate) |
Observations:
|
We have been looking into manually setting values for the covariance matrices to have certain values converge slower (Like X and Y). You can change these settings in odom.yaml . The reason we do this is as you can see in the graphs above, some of our sensors seem to be having spikes of bad data, which we don't want to affect our position estimate above |
Obtaining absolute position ways
Measuring Localization Performance, we can plot
|
Note: Previous work done on branch 63, file Caffeine/nav/load_waypoints/scripts/test_gps.py |
Note: Details about non-sensor specific covariances in file Caffeine/odom/config/odom.yaml |
Description:
Goals:
Acceptance Criteria:
Notes:
The text was updated successfully, but these errors were encountered: