[Documentation] [TitleIndex] [WordIndex

  Show EOL distros: 

pr2_common: pr2_dashboard_aggregator | pr2_description | pr2_machine | pr2_msgs

Package Summary

This package contains the xxx.machine files that describe the different hosts a node can be spawned on. Currently there is one machine file for the pr2 robot, and one for the simulated pr2 robot.

pr2_common: pr2_dashboard_aggregator | pr2_description | pr2_machine | pr2_msgs

Package Summary

This package contains the xxx.machine files that describe the different hosts a node can be spawned on. Currently there is one machine file for the pr2 robot, and one for the simulated pr2 robot.

pr2_common: pr2_dashboard_aggregator | pr2_description | pr2_machine | pr2_msgs

Package Summary

This package contains the xxx.machine files that describe the different hosts a node can be spawned on. Currently there is one machine file for the pr2 robot, and one for the simulated pr2 robot.

pr2_common: pr2_dashboard_aggregator | pr2_description | pr2_machine | pr2_msgs

Package Summary

This package contains the xxx.machine files that describe the different hosts a node can be spawned on. Currently there is one machine file for the pr2 robot, and one for the simulated pr2 robot.

pr2_common: pr2_dashboard_aggregator | pr2_description | pr2_machine | pr2_msgs

Package Summary

This package contains the xxx.machine files that describe the different hosts a node can be spawned on. Currently there is one machine file for the pr2 robot, and one for the simulated pr2 robot.

pr2_common: pr2_dashboard_aggregator | pr2_description | pr2_machine | pr2_msgs

Package Summary

This package contains the xxx.machine files that describe the different hosts a node can be spawned on. Currently there is one machine file for the pr2 robot, and one for the simulated pr2 robot.

Machine files

This package provides 2 files:

These files are intended to be included by roslaunch files. The intended usage is:

  <include file="$(find pr2_machine)/$(env ROBOT).machine" />

The user sets the ROBOT environment variable to pr2 when working with a physical PR2, and sim when working in simulation. In this way, roslaunch files that refer to machines c1 and c2 will distribute computation appropriately on the robot, but still work on a single machine in simulation (assuming that the single machine can support the processing requirements).


2019-04-20 13:04