- Rating
- 2
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 3
- Soundness
- 2
Read review
Paper summary
CoFiDrive extends DrivoR with scene-conditioned register refinement, a scorer combining register and patch features, and control-space augmentation for scorer training. The paper reports 92.9 PDMS on NAVSIM-v1 and 48.0 EPDMS on NavHard, with component ablations examining the contributions of these additions.
Critical strengths
-
The idea of giving the scorer access to finer visual features is sensible: trajectories that look similar at the scene level may differ in their clearance from nearby objects or road boundaries.
-
CSA is also useful in principle, as it supplies additional scoring examples without adding inference candidates.
Critical weaknesses
-
The additions to DrivoR are incremental, and the claimed improvement in trajectory scoring is not directly demonstrated. Each model generates its own proposals, while scorer training also changes the shared visual features. Higher PDMS therefore does not establish better ranking.
-
The default configuration scores 91.85 in Table 4 versus 92.40 in Table 3. The authors acknowledge the difference but do not explain it. This gap exceeds several component gains, including those in the additional appendix controls. Without run-level results, these improvements are difficult to assess.
-
Measured latency and peak memory are also missing, leaving the cost of the added experts and patch branch unclear.
Questions for authors
-
Does CCS select higher-scoring trajectories than the baseline when evaluated on identical proposals? A comparison using common, fixed visual features would further isolate the scorer architecture.
-
What explains the difference between Tables 3 and 4? Please provide individual run results for the key ablations, including the baseline with CSA alone if available.
-
What are the end-to-end inference latency and peak memory relative to the baseline under identical hardware and execution settings?