ros-perception / ros-perception/image_common
Handling namespace for multiple CameraInfoManagers in ROS2 jazzy
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 153
- Forks
- 253
- Avg merge
- 5m
- Merged PRs (30d)
- 1
Description
Hi,
I'm trying to set up the driver for a stereo camera, so I need two CameraInfoManager instances.
The hope was that I could set up the classes in such a way that they advertise:
/stereo/node_name/left/set_camera_info and
/stereo/node_name/right/set_camera_info
However, they always seem to end up advertising the exact same service name...?
/stereo/node_name/set_camera_info
Is there a workaround?
I saw that on the rolling branch, there is a "namespace" (ns) parameter that one can pass to the CameraInfoManager constructor, however it's missing on the jazzy branch. Is there a workaround? Or could this be backported?
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
Compare the rolling-branch CameraInfoManager constructor and its namespace parameter with the Jazzy implementation. Reproduce the stereo setup with two CameraInfoManager instances and verify whether the left and right set_camera_info services receive distinct names. Done means the requested namespace behavior is available on Jazzy or a documented workaround is established.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- robotics
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100