Change tf2_ros Python buffer client to a service?
Open
Nobody has claimed this yet.
enhancement
question
- Dominant language
- C++
- Stars
- 153
- Forks
- 256
- Avg merge
- 3d 23h
- Merged PRs (30d)
- 14
Description
In the port of tf2_ros Python to ROS 2 in #99, there was a TODO added asking why the buffer client is an action and not a service. We should revisit this decision and switch it to a service (maybe an asynchronous one) if it makes sense.
Contributor guide
No contributing guide indexed for this repository
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 by reviewing the tf2_ros Python buffer client and the TODO added in pull request #99. Determine whether its action interface should become a service, including whether an asynchronous service is appropriate; done requires a decided interface change rather than an open-ended investigation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- robotics
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100