ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange
Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

As joq and dornhege pointed out, you cannot control the order in which nodes are started. When I encountered this problem, I did added the following node to my launch script:

<node name="dump_rosparams" pkg="aliencontrol" type="aliencontrol" args="'sleep 5; rosparam dump params.yaml'"/>

It simply waits five seconds for all other nodes to start, and then dumps the parameters to the given file.

For that to work, you need to install the aliencontrol package. And please make sure the command is enclosed in single quotes inside XML's double quotes, because aliencontrol expects the command to execute to be a single argument.

As joq and dornhege pointed out, you cannot control the order in which nodes are started. When I encountered this problem, I did added the following node to my launch script:

<node name="dump_rosparams" pkg="aliencontrol" type="aliencontrol" args="'sleep 5; rosparam dump params.yaml'"/>
~/ROS/params.yaml'"/>

It simply waits five seconds for all other nodes to start, and then dumps the parameters to the given file.

For that to work, you need to install the aliencontrol package. And please make sure the command is enclosed in single quotes inside XML's double quotes, because aliencontrol expects the command to execute to be a single argument.

As joq and dornhege pointed out, you cannot control the order in which nodes are started. When I encountered this problem, I did added the following node to my launch script:

<node name="dump_rosparams"  pkg="aliencontrol"  type="aliencontrol"  args="'sleep 5; rosparam dump ~/ROS/params.yaml'"/>

It simply waits five seconds for all other nodes to start, and then dumps the parameters to the given file.

For that to work, you need to install the aliencontrol package. And please make sure the command is enclosed in single quotes inside XML's double quotes, because aliencontrol expects the command to execute to be a single argument.

As joq and dornhege pointed out, you cannot control the order in which nodes are started. When I encountered this problem, I did added the following node to my launch script:

<node name="dump_rosparams" 
      pkg="aliencontrol" 
      type="aliencontrol" 
      args="'sleep 5; rosparam dump ~/ROS/params.yaml'"/>

It simply waits five seconds for all other nodes to start, and then dumps the parameters to the given file.

If you are interested in the last set of parameters before shutdown, save them periodically until ROS shutdown:

<node name="dump_rosparams" 
      pkg="aliencontrol" 
      type="aliencontrol" 
      args="'while true; do rosparam dump ~/ROS/params.yaml; sleep 5; done'"/>

For that the above options to work, you need to install the aliencontrol package. And please make sure the command is enclosed in single quotes inside XML's double quotes, because aliencontrol expects the command to execute to be a single argument.