ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
2020-09-13 21:39:07 -0500 | received badge | ● Great Answer (source) |
2019-11-20 07:39:03 -0500 | commented answer | How to include a .launch file on a remote machine from a .launch file? This is indeed the case. The same goes for the fact that any nodes you want to launch remotely, have to be installed loc |
2019-01-10 08:48:11 -0500 | received badge | ● Enthusiast |
2018-10-05 08:17:31 -0500 | edited answer | Roslaunch machine tag on include If anyone is still looking for an answer, I think currently the most elegant solution is: <launch> <i |
2018-10-05 08:17:31 -0500 | received badge | ● Editor (source) |
2018-07-19 10:53:54 -0500 | received badge | ● Nice Answer (source) |
2018-04-19 05:54:35 -0500 | received badge | ● Necromancer (source) |
2018-04-19 05:39:12 -0500 | received badge | ● Good Answer (source) |
2018-02-22 04:08:14 -0500 | commented answer | How to include a .launch file on a remote machine from a .launch file? Do you mean the defailt="true" attribute of the <machine> element (which is present in my example)? Or is an addit |
2018-02-22 03:58:42 -0500 | edited answer | How to include a .launch file on a remote machine from a .launch file? If anyone is still looking for an answer, I think currently the most elegant solution is: <launch> <i |
2018-02-16 05:01:04 -0500 | commented answer | start and kill rosbag record from bash shell script The correct command that worked for me (ROS Kinetic) is: rosbag record -o /file/name /topic __name:=my_bag rosnode kill |
2018-02-16 05:00:56 -0500 | commented answer | start and kill rosbag record from bash shell script The correct command that worked for me (ROS Kinetic) is: rosbag record -o /file/name /topic __name:=my_bag rosnode kill |
2018-02-16 04:59:00 -0500 | commented answer | start and kill rosbag record from bash shell script The correct command that worked for me (ROS Kinetic) is: rosbag record -o /file/name /topic __name:=my_bag rosnode kill |
2017-04-12 06:40:07 -0500 | received badge | ● Nice Answer (source) |
2017-02-08 05:20:34 -0500 | received badge | ● Teacher (source) |
2017-02-08 05:20:34 -0500 | received badge | ● Necromancer (source) |
2017-02-06 03:56:19 -0500 | commented answer | How to include a .launch file on a remote machine from a .launch file? Apparently the machine tag doesn't apply to a specific group, but to any nodes/includes that come after it. So the order in which the tags are defined is important! |
2017-01-17 02:59:55 -0500 | answered a question | How to include a .launch file on a remote machine from a .launch file? If anyone is still looking for an answer, I think currently the most elegant solution is: Tested with ROS Kinectic on Ubuntu 16.04. Edit: Apparently the machine tag doesn't apply to a specific group, but to any nodes/includes that come after it. So the order in which the tags are defined is important! |
2017-01-17 02:58:06 -0500 | answered a question | Roslaunch machine tag on include If anyone is still looking for an answer, I think currently the most elegant solution is: Tested with ROS Kinectic on Ubuntu 16.04. Edit: Apparently the machine tag doesn't apply to a specific group, but to any nodes/includes that come after it. So the order in which the tags are defined is important! |
2017-01-16 08:13:35 -0500 | commented answer | How to include a .launch file on a remote machine from a .launch file? This isn't working on ROS Kinetic either, resulting in a warning and the nodes being launched on the local PC. |
2017-01-13 10:09:22 -0500 | received badge | ● Supporter (source) |