Upload parameters to paramserver, Change scope to local everywhere,
bag_recorder records camera and collision topic as set in the yaml file
Problem is solved by making setupRobotService optional

If the parameter is omitted or empty assume we are ready
Set move_base_action in the config
Done in commit fe266822a1f1771ae85d3422f8b790ff47dd8f6b
Problem solved differently

By uploading the parameters from the yaml config into the same
namespace, the bagrecorder can access camera and collision topic
settings. It includes those topics into the bagfile
Collisions detection supports multiple bumper topics
Add camera and collision topic(s) meta data to status

Start image_view based on those information in the analysis step
Move to mid priority
Routes no longer required

Route data in included in the respective yaml file
Move into config dir
Update the timeout scenario
Use an extra node to display the cameras
Use rostime for timeout instead of realtime
In case of an error, display the actual metrics
Dont rotate the camera
Initial version for the new ipa test scenarios

Include two different routes. A compact one in the apartment and an
extended one that enters an office.
If an msg was omitted, don't throw an error
Change failure message
Change error code from failed:aborted to aborted
Update the rosbag patcher to work with groovy as well.

Include an additional debug script. Paths must be adapted to an existing
damanged bagfile to test