Also, to clarify point #3 on that page, what it does allow you to do
is multiply define a <machine> tag, thus, "remapping" is achieved by
repeating the machine definition, but with the name you want to alias
it to.

HTH,
Ken

On Mon, Sep 20, 2010 at 9:12 AM, Ken Conley <kwc@willowgarage.com> wrote:
> Hi Mike,
>
> remap applies only to ROS graph resources names. Machine names are not
> considered as part of this designation. Graph resource names are
> described here:
>
> http://www.ros.org/wiki/Names
>
> If you are using ROS 1.2, you may want to look into use the new <arg>
> tag and $(arg) substitution variable.
>
>  - Ken
>
> On Mon, Sep 20, 2010 at 8:29 AM, Mike Purvis
> <mpurvis@clearpathrobotics.com> wrote:
>> Hey,
>> It doesn't seem to be possible to use <remap> with machine names. Is this
>> intentional? Following from point #3 on this page
>> <http://www.ros.org/wiki/roslaunch/Architecture>, I expected to be able to
>> structure my launch file like so:
>> <launch>
>>   <include file="all_machines.launch">
>>   <remap from="robot_machine" to="cpr-demo-01" />
>>   <remap from="joystick_machine" to="cpr-demo-02" />
>>   <remap from="gui_machine" to="cpr-demo-03" />
>>   <group ns="my_robot">
>>     <include file="robot_stuff.launch" />
>>     <include file="more_robot_stuff.launch" />
>>   </group>
>> </launch>
>> The nodes listed inside of robot_stuff.launch and more_robot_stuff.launch
>> would be able to refer to robot_machine and have that resolve to
>> cpr-demo-01. Have I misunderstood the expected structure? Is the idea that
>> the machine aliasing occurs in the file containing the master machines list?
>> Thanks,
>> Mike
>> _______________________________________________
>> ros-users mailing list
>> ros-users@code.ros.org
>> https://code.ros.org/mailman/listinfo/ros-users
>>
>>
>