Ask Your Question

Revision history [back]

click to hide/show revision 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.

You can configure the launch file so that the same group of nodes are put in different namespaces.
For example:
<launch>

<launch>

  <group ns="group1">
ns="group1">  
        <node name="pub" pkg="myPkg" type="pub_node"/>
type="pub_node"/>  
        <node name="sub" pkg="myPkg" type="sub_node"/>
type="sub_node"/>  
  </group> 
<group ns="group2"> ns="group2"> <node name="pub" pkg="myPkg" type="pub_node"/> type="pub_node"/> <node name="sub" pkg="myPkg" type="sub_node"/> type="sub_node"/> </group>

</launch>

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.

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 /group2/pub_out/group2/pub_node. You might want to remap the names outside the namespace accordingly.

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.

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.

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.