Autoware installation type: Docker image autoware/autoware:1.14.0-melodic-cuda, as specified in the Dockerfile of https://github.com/carla-simulator/carla-autoware at commit 975b6f3.
Autoware version or commit hash - 1.14.0
ROS distribution and version:
ROS Melodic (pre-installed in the docker image)
ROS installation type:
Pre-installed in the docker image
Description of the bug
I am running Autoware 1.14.0 (docker image: autoware/autoware:1.14.0-melodic-cuda), Carla 0.9.10.1 (docker image: carlasim/carla:0.9.10.1) as a simulator and carla-autoware-bridge at 975b6f3 as a bridge.
For an unknown reason, the global path planner generates an infeasible global path that cuts through a map. Following the path, the Autoware vehicle ends up crashing into static objects (fence, houses, ...) in the map.
Please see the camera data. The vehicle makes a sudden right turn, crashing into a fence.
Looking at the visualized path, rviz, the initial global path itself is infeasible. Pure pursuit did its job in following the global path.
Please check the rosbag file for a detailed trace.
Bug report
Required information:
autoware/autoware:1.14.0-melodic-cuda
, as specified in the Dockerfile ofhttps://github.com/carla-simulator/carla-autoware
at commit975b6f3
.Description of the bug
autoware/autoware:1.14.0-melodic-cuda
), Carla 0.9.10.1 (docker image:carlasim/carla:0.9.10.1
) as a simulator and carla-autoware-bridge at975b6f3
as a bridge.Steps to reproduce the bug
Expected behavior
New motion plan should be generated to deal with the blocking object.
Actual behavior
Motion plan doesn't change, leading to a forward collision.
Screenshots
Additional information