By convention rocon_launch files are named with the extension .concert. These are able to be tab-completed on the command line when executing rocon_launch.
Attributes
Elements
Usage
This tag has exactly the same properties as the roslaunch arg tag. They can be used in one of three ways
<arg name="foo" />
Declares the existence of foo. foo must be passed in either as a command-line argument (if top-level) or via <include> passing (if included).
<arg name="foo" default="1" />
Declares foo with a default value. foo can be overriden by command-line argument (if top-level) or via <include> passing (if included).
<arg name="foo" value="bar" />
Declares foo with constant value. The value for foo cannot be overridden. This usage enables internal parameterization of a launch file without exposing that parameterization at higher levels.
Attributes
Elements
None
Single master multi-launcher running talker in one window and listener in another. The topic name can be pre-configured via the topic_name arg.
1 2 3 4 5 6 7 8 9 10 | <concert>
<arg name="topic_name" default="chatter"/>
<launch title="talker" package="rocon_launch" name="talker.xml" port="11311">
<arg name="topic_name" value="$(arg topic_name)"/>
</launch>
<launch title="listener" package="rocon_launch" name="listener.xml" port="11311">
<arg name="topic_name" value="$(arg topic_name)"/>
</launch>
</concert>
|
A multi-master chatter concert:
1 2 3 4 5 6 7 8 9 10 | <concert>
<arg name="local_machine_only" default="true"/> <!-- only invite clients if they are on the same pc -->
<launch title="concert:11311" package="chatter_concert" name="concert.launch" port="11311">
<arg name="local_machine_only" value="$(arg local_machine_only)"/>
</launch>
<launch title="dudette:11312" package="chatter_concert" name="dudette.launch" port="11312"/>
<launch title="dude:11313" package="chatter_concert" name="dude.launch" port="11313"/>
<launch title="dude:11314" package="chatter_concert" name="dude.launch" port="11314"/>
</concert>
|