This repository was archived by the owner on May 31, 2025. It is now read-only.
Make transform_listener reset tf buffer on loop detection#68
Merged
tfoote merged 1 commit intoros:hydro-develfrom Sep 18, 2014
Merged
Make transform_listener reset tf buffer on loop detection#68tfoote merged 1 commit intoros:hydro-develfrom
tfoote merged 1 commit intoros:hydro-develfrom
Conversation
This makes tf2 work with `rosbag --clock --loop` as expected.
Contributor
Author
|
Also, please cherry-pick this change to indigo-devel if this request is merged. |
tfoote
added a commit
that referenced
this pull request
Sep 18, 2014
Make transform_listener reset tf buffer on loop detection Fixes #43
tfoote
added a commit
that referenced
this pull request
Sep 18, 2014
This file contains hidden or 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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
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.
This makes tf2 work with
rosbag --clock --loopas expected.For some reason rostime does not use CLOCK_MONOTONIC,
so I'm not sure whether we should allow for tiny backjumps (< 1s).
I know for sure this is an issue with the rospy API at least.
Also addresses issue #64.