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

Optimizer changes #10

Merged
merged 42 commits into from
Dec 9, 2024
Merged

Optimizer changes #10

merged 42 commits into from
Dec 9, 2024

Conversation

henrygerardmoore
Copy link
Collaborator

@henrygerardmoore henrygerardmoore commented Nov 24, 2024

Allows the odom publisher to predict into the future. See the fuse_apriltag_tutorial for how to use it. You can modify the prediction time in apriltag_simulator.cpp to try out different values.

Many of the changes are just clang-tidy fixes in files I was passing through. To see the relevant changes, just look in particular at 6c6f9aa and 4557480's changes.

@henrygerardmoore henrygerardmoore marked this pull request as ready for review December 6, 2024 00:24
@henrygerardmoore henrygerardmoore enabled auto-merge (squash) December 9, 2024 17:30
Copy link
Collaborator

@rlpratt12 rlpratt12 left a comment

Choose a reason for hiding this comment

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

Code looks good, and future state prediction works as expected in sim/tutorial.

Some minor clarification notes from review:

  • Predicted state gets far away from current state at turn-around points in trajectory because it has no knowledge of the input force, so it can only assume continued motion based on the current velocity (short version: this behavior is expected).
  • occasionally get "[WARN] Could not find a connection between 'base_link' and 'april_X' "
    • This is a function of how tf is published right before using it, and sometimes it gets dropped. This is for the sim only, and will not be implemented on real system, so ok to ignore it here.
  • 3d_motion_model process noise isn't getting added in sim, so don't worry about the values too much. They're just used to reduce confidence in acceleration for example, because we have no measurement of that.

@henrygerardmoore henrygerardmoore merged commit e46c7b3 into main Dec 9, 2024
4 checks passed
@henrygerardmoore henrygerardmoore deleted the optimizer_changes branch December 9, 2024 18:04
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.

2 participants