Add tf_prefix parameter for hardware interface #14
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.
When using a robot description that uses a tf_prefix for the robot,
the joint names will be different than expected in the hardware interface.
This commits ads a tf_prefix parameter to the hardware node in order to pass
a tf_prefix into the node.
Obviously, this could be solved differently, e.g. by reading the joint names from the parameter server completely, I've seen that approach in other RobotHW implementations, as well. That would have the benefit of being completely flexible with the downside of adding an additional list parameter to the node.