Abstract

With the promising development and deployment trends of autonomous vehicles (AVs), AVs’ operation safety has become a key issue worldwide. Studies have been conducted to reveal the risk factors of AV operation safety based upon AV-involved crash reports. However, the crash data sample size was limited and the crash reports only recorded static information, thus it failed to identify crash contributing factors and further provide feedbacks to AV algorithm development. In this study, the risk factors were investigated based upon hazardous scenarios, which were claimed to possess consistent causal mechanisms with crash events. First, contributing factors were extracted from both vehicle kinematics and traffic environment aspects, and their volatility features were obtained. Then, path analysis models were developed to reveal the concurrent relationships between scenario volatility and hazardous scenario occurrence probability. Besides, to understand the varying risk factors for hazardous scenarios caused by human drivers and AVs, a logit regression model was further established. The modeling results showed that large volatility of space headway held direct impacts on increasing the AV driving risks. And the volatility of the drivable road area had no significant impacts on AV driving risks while it indirectly influenced human driving risks. Finally, result implications for AV driving behavior improvements have been discussed.

Full Text
Paper version not known

Talk to us

Join us for a 30 min session where you can share your feedback and ask us any queries you have

Schedule a call

Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.