Conversation
Member
Author
|
@alexlin2 renamed the parameter as per our discussion |
alexlin2
force-pushed
the
configurable-staticTF-pub
branch
from
15118ce to
12f887c
Compare
… configurable static TF publishing
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
3 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.
Currently, static transforms are published between:
These parameters are kept somewhat arbitrarily and configurable for different robot platforms. But, if the stack is to be used which a robot state publisher, which can publish these transforms exactly, a configurable parameter should exist to disable the publishing of these static transforms.
I have added a launch argument for the same with the default behaviour to follow whatever was happening previously.