- Rating
- 3
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 2
- Soundness
- 2
Read review
Paper summary
This paper proposes SafeCoDriver, a post-intervention safety assessment framework for cooperative perception in autonomous driving. It integrates three components, i.e., Trajectory Conflict Resolution, Multidirectional Threat Assessment, and Long-Horizon Feasibility Assessment, to refine planned safety interventions before execution, avoiding secondary collisions or traffic stagnation introduced by the intervention itself. The method is validated on closed-loop SUMO simulations and the open-loop DeepAccident dataset, showing improved safety and maintained mobility across multiple baselines.
Critical strengths
(1) It has a well-justified problem framing. The paper uses matched controlled experiments to clearly show that standard safety interventions can induce new collisions or stagnation in scenarios that are safe without intervention. This is an important, under-studied problem in cooperative driving. (2) It has a comprehensive empirical validation. The evaluation spans closed-loop simulation, open-loop real-world datasets, component ablation, and robustness tests under sensor noise and communication delay. The results seem to consistent and strongly support the claimed benefits.
Critical weaknesses
(1) The core technical components (beam-search trajectory correction, TTC-based threat scoring, horizon collision checking) are mostly adapted from existing methods. The work is more of a system-level integration than a fundamental advance. Thus, the novelty of this work can be further improved. (2) Surrounding vehicles are modeled as non-reactive constant-velocity agents. The paper does not evaluate how other road users’ responses to the ego vehicle’s braking or lane change would affect post-intervention safety, which weakens the real-world validity.
Questions for authors
(1) Did you test the framework with reactive surrounding driver models (e.g. IDM car-following)? Would more realistic interactive traffic change the main collision and stagnation results? (2) The design decouples trajectory correction from warning output. How would this two-branch structure map to real in-vehicle warning logic, and is there any validation of the warning performance beyond the geometric check?
4 comments
2/2 Response to Reviewer wHkm
Response 3. Role of warning and evidence for decoupling
Reviewer comment (Question 2)
The design decouples trajectory correction from warning output. How would this two-branch structure map to real in-vehicle warning logic, and is there any validation of the warning performance beyond the geometric check?
Response
The warning is meant to alert the driver to risks. It uses a learned collision-risk score, nominal-trajectory geometric conflicts, and MTA-filtered TTC to identify risky situations and imminent threats. Cooperative observations make relevant occluded road users available to this assessment. An advisory output could help a driver recognize hazards beyond the onboard view and understand when greater attention is needed.
Even when no warning is issued, the system continues to check risks and adjust the vehicle's actions. To test this choice, we compare Full with a warning-gated variant that permits correction only when warning is active, using the same warning model and signal. The comparisons use 1,200 matched responsive episodes and 400 matched joint-input-error episodes.
Table R2. Warning-decoupling ablation.
| Variant | Responsive collision rate (%) | Joint-error collision rate (%) |
|---|---|---|
| Full, decoupled | 4.33% | 3.25% |
| Without warning decoupling | 13.42% | 5.25% |
Keeping correction independent of warning reduces collisions in both settings. This supports decoupling advisory activation from the availability of corrective action.
Dear Reviewer,
As the discussion period draws to a close, we would like to kindly follow up on our response to your review. We would appreciate hearing whether our clarifications have addressed your concerns, and whether there are any remaining points we could help clarify.
Thank you again for your time and thoughtful feedback.
Best regards, The Authors
Comment
Thanks for the responses. Overall, the responsive-traffic and warning-decoupling experiments address my main questions with concrete evidence. I keep my rating at 3 (weak accept), while noting that the components are still adapted from existing work and that real-road validation remains a limitation.
1/2 Response to Reviewer wHkm
We sincerely thank you for your careful reading of our paper and for your constructive comments. Your questions have guided our additional experiments and helped us clarify the method and experimental results. We address each concern below and hope that the additional evidence and explanations will help you reassess our work.
Response 1. Contribution
Reviewer comment (Weakness 1)
The core technical components (beam-search trajectory correction, TTC-based threat scoring, horizon collision checking) are mostly adapted from existing methods. The work is more of a system-level integration than a fundamental advance. Thus, the novelty of this work can be further improved.
Response
Thank you for asking us to clarify the contribution. We believe that the problem addressed in this work deserves careful investigation. A safety intervention changes ego motion and can create conflicts with surrounding traffic or prevent continued passage. Assessing these consequences is important because resolving the initial hazard alone does not establish the safety of the resulting maneuver.
SafeCoDriver explores a solution to this problem through cooperative observations and candidate intervention assessment. A suitable cooperative vehicle reveals relevant road users occluded from ego. These observations inform trajectory correction and the assessment of directional threats, future conflicts, and lane blockage before action selection. The ablation studies examine how these choices affect waypoint exposure, collisions, and mobility. The following responsive-traffic experiments demonstrate the effectiveness of this approach in the evaluated settings. We will make this problem-specific design and the role of cooperative observations clearer, with the observation assumptions and family-level results in the Appendix.
ACR is a further contribution. It measures collisions introduced into matched episodes that were collision-free under nominal driving. Reporting ACR alongside overall collisions, completion, and Progress distinguishes added risk from unresolved hazards and collision avoidance achieved through stagnation. This evaluation can be applied to other safety interventions.
Response 2. Responsive-traffic experiments
Reviewer comment (Weakness 2 / Question 1)
Surrounding vehicles are modeled as non-reactive constant-velocity agents. The paper does not evaluate how other road users’ responses to the ego vehicle’s braking or lane change would affect post-intervention safety, which weakens the real-world validity.
Did you test the framework with reactive surrounding driver models (e.g. IDM car-following)? Would more realistic interactive traffic change the main collision and stagnation results?
Response
We evaluated all nine methods across eight scenario families in responsive traffic based on the Intelligent Driver Model (IDM). The methods use the same scenario settings and acceleration and braking limits. Each method is evaluated on 1,200 matched episodes. Secondary counts episodes with a later ego collision involving an object absent from the first collision step, using all episodes as the denominator.
Table R1. Supplementary comparison under responsive traffic.
SafeCoDriver records 52/1,200 collisions (4.33%), 95.67% completion, and 165.07 m mean Progress. It has the lowest collision rate and the highest completion rate and mean Progress in this comparison. These results show that SafeCoDriver remains effective in the evaluated responsive traffic.