- Rating
- 3
- Confidence
- 2
- Informativeness
- 2
- Presentation
- 2
- Soundness
- 2
Read review
Paper summary
In this paper, the authors designed a new knowledge-dense and token-sparse visual encoder to extract visual, semantic, and geometric knowledge for better end-to-end autonomous driving. To solve the problem of spatiotemporal information redundancy, the authors design a register-guided token compression mechanism to reduce redundant patch computation across cameras and frames. The experiment shows that the visual encoder and the three-stage framework are effective.
Critical strengths
I agree that optimizing visual encoders is an effective method to enhance end-to-end planning capabilities, so I support the core claim of this paper: “makes the visual encoder knowledge-dense and token-sparse for end-to-end driving”. Considering the visual, semantic, and geometric knowledge required for autonomous driving, it is intuitive for the stage 1 of the framework to distill different information from multiple teachers. In addition, reducing patch computation is a practical way to improve inference efficiency. Finally, the author's experiments show that the framework achieves excellent results in different NAVSIM sets and HUGSIM.
Critical weaknesses
I think the paper would benefit from a direct quantitative evaluation of the distilled visual encoder’s semantic and geometric capabilities. The authors claim that the visual encoder in stage 1 transfers the semantic and geometric knowledge from the teachers. I believe that if the corresponding semantic and depth estimation performance can be evaluated, the overall paper will be more complete and the powerful capabilities of the visual encoder can be reflected.
Questions for authors
- What are the results of DriveZero on NAVSIM v1 set? The paper discusses DriveZero in the main text, but its results are not included in Table 1.
3 comments
Anticipating Your Participation as Reviewer-Author Discussion Deadline Approaching
Thank you for your time and thoughtful feedback. We have provided comprehensive responses to all the concerns. As the discussion period ends in two days, we would appreciate knowing whether any questions remain. We are happy to provide further clarification. Thank you again for your time and consideration.
The authors have addressed my concerns, and I will keep my original score.
Response to Reviewer JBX4
We appreciate the recognition of our contributions and address the raised points in detail below.
Question1: I think the paper would benefit from a direct quantitative evaluation of the distilled visual encoder’s semantic and geometric capabilities.
Response1: Thank you for suggesting this quantitative evaluation. We evaluate semantic segmentation on Cityscapes and monocular depth estimation on KITTI. For each task, we train a separate prediction head of the same design on the frozen final-layer patch features of each encoder. For KITTI, we use 800 training pairs and 200 evaluation pairs from the selected validation set. We have added training and evaluation details to Appendix A.
Relative to the original DeiT-S, the distilled encoder improves Cityscapes mIoU by 28.33 points and reduces KITTI RMSE by 47.8%. The distilled visual encoder captures richer semantic and geometric information. Under the same frozen-feature probing protocol, the distilled encoder scores lower than the comparably sized DINOv3 ViT-S/16 on Cityscapes but achieves lower KITTI RMSE. These results demonstrate the effectiveness of our multi-teacher visual distillation.
Question2: What are the results of DriveZero on NAVSIM v1 set? The paper discusses DriveZero in the main text, but its results are not included in Table 1.
Response2: Thank you for pointing this out. For fair comparison, Sec. 5.2 uses the result for DriveZero with DriveVFM ViT-S. This variant uses NAVSIM navtrain without SimScale for downstream training (DriveZero, arXiv:2609.06055v1, Tabs. 7 and A13).
ConDenseDrive achieves better performance despite using a narrower distillation corpus and no RL-generated trajectory supervision. Our design changes are confined to the visual encoder, leaving the downstream planner architecture unchanged.