ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
1 | initial version |
You can configure the launch file so that the same group of nodes are put in different namespaces.
For example:
<launch>
<group ns="group1">
<node name="pub" pkg="myPkg" type="pub_node"/>
<node name="sub" pkg="myPkg" type="sub_node"/>
</group>
<group ns="group2">
<node name="pub" pkg="myPkg" type="pub_node"/>
<node name="sub" pkg="myPkg" type="sub_node"/>
</group>
Note that the full names for the topic will be, for example /group1/sub_in
or /group2/pub_out
. You might want to remap the names outside the namespace accordingly.
2 | No.2 Revision |
You can configure the launch file so that the same group of nodes are put in different namespaces.
For example:
<launch>
<launch>
<group Note that the full names for the topic topics (and nodes) will be, for example /group1/sub_in
or /group2/pub_out
. You might want to remap the names outside the namespace accordingly.
3 | No.3 Revision |
You can configure the launch file so that the same group of nodes are put in different namespaces.
For example:
<launch>
<group ns="group1">
<node name="pub" pkg="myPkg" type="pub_node"/>
<node name="sub" pkg="myPkg" type="sub_node"/>
</group>
<group ns="group2">
<node name="pub" pkg="myPkg" type="pub_node"/>
<node name="sub" pkg="myPkg" type="sub_node"/>
</group>
</launch>
Note that the full names for the topics (and nodes) will be, for example /group1/sub_in
or
. You might want to remap the names outside the namespace accordingly./group2/pub_out/group2/pub_node
4 | No.4 Revision |
You can configure the launch file so that the same group of nodes are put in different namespaces.
For example:
<launch>
<group ns="group1">
<node name="pub" pkg="myPkg" type="pub_node"/>
<node name="sub" pkg="myPkg" type="sub_node"/>
</group>
<group ns="group2">
<node name="pub" pkg="myPkg" type="pub_node"/>
<node name="sub" pkg="myPkg" type="sub_node"/>
</group>
</launch>
Note that the full names for the topics (and nodes) will be, for example instance/group1/sub_in
or /group2/pub_node
. You might want to remap the names outside the namespace accordingly.
5 | No.5 Revision |
You can configure the launch file so that the same group of nodes are put in different namespaces.
For example:
<launch>
<group ns="group1">
<node name="pub" pkg="myPkg" type="pub_node"/>
<node name="sub" pkg="myPkg" type="sub_node"/>
</group>
<group ns="group2">
<node name="pub" pkg="myPkg" type="pub_node"/>
<node name="sub" pkg="myPkg" type="sub_node"/>
</group>
</launch>
Note that the full names for the topics (and nodes) will be, for instanceinstance /group1/sub_in
or /group2/pub_node
. You might want to remap the names outside the namespace accordingly.
6 | No.6 Revision |
You can configure the launch file so that the same group of nodes are put in different namespaces.
For example:
<launch>
<group ns="group1">
<node name="pub" pkg="myPkg" type="pub_node"/>
<node name="sub" pkg="myPkg" type="sub_node"/>
</group>
<group ns="group2">
<node name="pub" pkg="myPkg" type="pub_node"/>
<node name="sub" pkg="myPkg" type="sub_node"/>
</group>
</launch>
Note that the full names for the topics (and nodes) will be, for instance instance, /group1/sub_in
or /group2/pub_node
. You might want to remap the names outside the namespace accordingly.