[Melodic] Fixes timestamp in waitForTransform#231
Open
pet1330 wants to merge 1 commit intostrands-project:melodic-develfrom
Open
[Melodic] Fixes timestamp in waitForTransform#231pet1330 wants to merge 1 commit intostrands-project:melodic-develfrom
pet1330 wants to merge 1 commit intostrands-project:melodic-develfrom
Conversation
pet1330
changed the title
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Currently, a different timestamp is provided to the
waitForTransformandtransformPosefunctions which may cause issues if they are different. The system should use the msg timestamp, however, because of an issue with the bayesian tracker, the msg timestamp is set to 0.0 causing the waitForTransform to timeout (causing a 3 second delay in starting). To solve this, I have instead set it to use the current timestamp.