ros2 topic delay for tf
Open
Nobody has claimed this yet.
backlog
- Dominant language
- Python
- Stars
- 262
- Forks
- 228
- Avg merge
- 23h 15m
- Merged PRs (30d)
- 12
Description
Feature request
Feature description
It would be nice to be able to run ros2 topic delay for the /tf topic. It has the message type tf2_msgs/msg/TFMessage which is a list of TransformStamped, each containing a header.
Implementation considerations
Either messages of type tf2_msgs/msg/TFMessage could always be treated in this way or a command line option could be added that makes it possible to give a subfield that should be checked for headers.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the ros2 topic delay command entry point and inspect how message types are handled. Resolve whether TFMessage should be supported automatically or through a subfield option, then verify that delay calculation uses the contained TransformStamped headers.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100