Fix odom messages being converted to tf #1137
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
andrew-aj
approved these changes
Feb 22, 2024
|
Hola, your friendly InvestiGator bot here with another message! Because this PR was closed/merged, I'm going to remove the docs preview for now. Have a great day! Go gators! 🐊 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
#1097 broke the
odometry_to_tfnode because it filters out all odom messages after the first one is sent. oopses!This PR fixes that by just making sure that no messages are sent that have exactly the same timestamp.
Screenshot or Video
Related Issues
- Closes #XXX
Testing
About This PR