ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange
Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

Hi @mandymandymandy,

At the end of the day the only thing you will have will be a set of thread executing publishing tasks or subscribing ones so technically it does not matter. On the other hand, there are important things like keeping the code clean, adjust to ROS standards and organizing properly your project. As ROS said: "When a publisher and subscriber use the same topic both exist inside the same node"

If you are OK dealing with the set of subscribers and publishers in the same node go ahead, but take into account that if you split this two sets in two different nodes, technically you will have the same set up but better understanding of your package structure and code.

At least is how I see it, if someone in this community wants to add more background on this kind of problems I will be glad to hear it.

Hi @mandymandymandy,

At the end of the day the only thing you will have will be a set of thread executing publishing tasks or subscribing ones so technically it does not matter. On the other hand, there are important things like keeping the code clean, adjust to ROS standards and organizing properly your project. As ROS said: "When a publisher and subscriber use the same topic both exist inside the same node"project.

If you are OK dealing with the set of subscribers and publishers in the same node go ahead, but take into account that if you split this two sets in two different nodes, technically you will have the same set up but better understanding of your package structure and code.

At least is how I see it, if someone in this community wants to add more background on this kind of problems I will be glad to hear it.