Fixed tf for odometry #86
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
Signed-off-by: Jakub Delicat <[email protected]>
|
Thank you! I'll check the changes later. |
|
@delipl |
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.
The current transform publisher works wrong when an odometry is used.
The proper tf tree should look:
base_link -> odom -> map
but current implementation provides:
base_link -> odom
base_link -> map
The video of flicking robot model on the current version:
Screencast from 22.04.2024 21:50:52.webm
The video of this PR:
Screencast from 22.04.2024 21:41:05.webm
This kind of aproch can be found in nav2_amcl and slam_toolbox
PS: fixed typo 👯