micro-ROS / micro-ROS/micro-ROS-Agent
A way to set a ROS namespace in the Agent
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 201
- Forks
- 111
- Avg merge
- 1d 6h
- Merged PRs (30d)
- 10
Description
I would like to have the ability to set an arbitrary ROS namespace of the node from the computer running the Agent. The way of doing this in ROSSerial is to just run the serial_node under a namespace. In micro-ROS it's a little more problematic because the namespace has to be passed to rclc_node_init_default function, so it has to be retrieved before the ROS communication is initialized.
The way I see it could work is when the Agent could be run with some parameters and the client had functions to retrieve these parameters. Then, I could just define the namespace parameter and retrieve it in the firmware before initializing the node.
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
The issue names no repository files or tests. Start by tracing Agent startup and the communication path between Agent parameters and client initialization, paying attention to the namespace needed before rclc_node_init_default. Done means a namespace can be supplied when launching the Agent, retrieved by the client before node initialization, and verified by appropriate tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100