ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
1 | initial version |
I thought so as well. But I think i found the problem now, thanks to gvdhoorn mentioning the run_id
.
It seems that we have the run_id
in a parameter file which we load with roslaunch
. This caused the second log directory.
I removed the run_id from the parameter file now, but this file is sometimes created by our partners so i cann't make sure this does not happen again from time to time. Maybe there a way not to load the run_id parameter.
Anyway. Thank you gvdhoorn and dornhege for your help.