ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
1 | initial version |
you can use the args
flag to pass in the arguments as you would from the command line:
<node pkg="rosbag" type="record" args="-O <PATH_TO_BAGFILE>" name="record" output="screen"/>
2 | No.2 Revision |
you can use the args
flag to pass in the arguments as you would from the command line:
<node pkg="rosbag" type="record" args="-O <PATH_TO_BAGFILE>" name="record" output="screen"/>
EDIT
Even though this is probably not the way it is intended, you could also go with the prefix (note, lower case o):
<node pkg="rosbag" type="record" args="-o <PATH_TO_BAGFILE>" name="record" output="screen"/>
e.g. -o ~/Desktop/
would result in the file /home/mig/Desktop/_2016-10-12-17-06-59.bag
. But this is rather a workaround then a proper solution.
3 | No.3 Revision |
you can use the args
flag to pass in the arguments as you would from the command line:
<node pkg="rosbag" type="record" args="-O <PATH_TO_BAGFILE>" name="record" output="screen"/>
EDIT
Even though this is probably not the way it is intended, you could also go with the prefix (note, lower case o):
<node pkg="rosbag" type="record" args="-o <PATH_TO_BAGFILE>" name="record" output="screen"/>
e.g. -o ~/Desktop/
would result in the file /home/mig/Desktop/_2016-10-12-17-06-59.bag
. on my system. But this is rather a workaround then a proper solution.
4 | No.4 Revision |
you can use the args
flag to pass in the arguments as you would from the command line:
<node pkg="rosbag" type="record" args="-O <PATH_TO_BAGFILE>" name="record" output="screen"/>
EDIT
Even though this is probably not the way it is intended, you could also go with the prefix (note, lower case o):
<node pkg="rosbag" type="record" args="-o <PATH_TO_BAGFILE>" name="record" output="screen"/>
e.g. -o ~/Desktop/
would result in the file /home/mig/Desktop/_2016-10-12-17-06-59.bag
on my system. But this is rather a workaround then a proper solution.
EDIT2
whoops, soory about that. Seems like the ~
shortcut for the users home directory cannot be resolved from the launch file. So you need to specify the full path, i.e. /home/<USER>/...
for it to work.