跳转到内容

GTRS: Generalized Trajectory Scoring for End-to-end Multimodal Planning

GTRS: Generalized Trajectory Scoring for End-to-end Multimodal Planning

Section titled “GTRS: Generalized Trajectory Scoring for End-to-end Multimodal Planning”

⚠️ AI 生成 · 建议对照原文 本页为自动整理的学习笔记;关键数据与引用如需引用,请回查 PDF / 官方版本。

学习档位 中文笔记

类型 文献 · 更新 2026-07-19

标签 autonomous-driving · planning · end-to-end-learning · trajectory-scoring · navsim

所属 自动驾驶预测、规划与控制 · 端到端驾驶

Migration status: imported from ad_projs@a823662; source anchors and claims remain needs-source-verification.

中文学习笔记(自动生成,需核验)

Section titled “中文学习笔记(自动生成,需核验)”

Topic: ad-prediction-planning-control · Tier: recent · Year: 2025 · Venue:
Evidence level: partial · 本地全文: 是 · 建议阅读: ~40 分钟
Paper: https://arxiv.org/abs/2506.06664
Code:
Generator: grok

作为Navsim v2 Challenge获胜方案,GTRS统一解决端到端多模态规划中静态大词汇缺乏细粒度适应与动态小提案泛化不足的问题,即使传感器次优也能接近基于真值感知的特权方法性能,对具身智能规划泛化有直接参考价值。

GTRS通过扩散轨迹生成、超密词汇dropout泛化与传感器增强+细化,实现端到端多模态规划中对静态/动态轨迹的鲁棒联合评分。

端到端多模态规划需在无真值感知条件下对多轨迹候选进行评分并选最优;现有方法要么评分大静态词汇(粗粒度、难细粒度适应),要么评分小动态提案(训练仅见窄子集,难泛化未见轨迹),均缺乏对多样轨迹分布的泛化能力。

端到端自动驾驶规划基础、BEV特征提取与Transformer编解码、扩散策略/DDPM轨迹生成、轨迹词汇/tokenizer评分范式(如Hydra-MDP)、Navsim/PDM类规则指标。

  • 提出GTRS统一框架,结合扩散动态生成与词汇评分,支持对动态与静态候选的有效评分。
  • 引入超密词汇(16384)+轨迹dropout训练策略,实现训练-推理词汇不匹配下的泛化,可评分未见分布。
  • 提出传感器旋转扰动增强+top-k细化训练(自蒸馏EMA),提升域外鲁棒与细粒度判别。
  • 在Navhard上验证,模型集成后作为Navsim v2获胜方案,传感器方法接近PDM-Closed特权性能。

训练三支柱子网络:1)DP扩散生成器(图像骨干+BEV编码器+Diffusion Transformer,BEV分割辅助,DDPM去噪归一化GT轨迹)产生Vdp提案;2)GTRS-Dense评分器在超密VXL上训练(半dropout),推理可用较小VL;3)GTRS-Aug在传感器旋转扰动+对应GT变换上训练,附加top-k细化解码器(EMA自蒸馏软目标)。推理时将Vdp附加到推理词汇VL形成Vdp∪VL,tokenizer后由评分器打分选argmax(或集成)。

DP:BEV条件扩散生成细粒度提案,补静态粗离散不足。GTRS-Dense:超密词汇训练+dropout(对齐token数、制造分布偏移、正则),基于Transformer Decoder交互轨迹/图像token,可泛化到静态/动态。GTRS-Aug:2D水平视角旋转扰动应对传感器分布偏移;细化解码器对top-k候选 refinement,EMA教师软监督+clip保证目标合理。取舍:训练仅静态多样词汇以获泛化,推理再注入动态细粒度提案,避免训练中集成扩散的开销与不稳定。

Navsim数据集及其v2 Challenge新划分Navhard(困难真实场景+3DGS合成延续,合成有畸变/模糊伪影);两阶段评估(Stage1真实、Stage2合成)聚合扩展PDM Score(EPDMS,由多规则指标如NC/DAC/DDC/TLC/EP/TTC/LK/HC/EC等组成)。实现细节在extract中截断,分辨率/骨干有多种配置(如512×2048 EVA-ViT-L、256×1024 ViT-L等)。

Table1路线图:DP无评分随机选EPDMS 25.6;GTRS-Dense最佳配置(VXL dropout训练 + Vdp∪VL推理)达EPDMS 43.4;GTRS-Aug达43.4。Table2 Navhard:PDM-Closed(GT感知)51.3;GTRS-Dense(EVA-ViT-L)43.4;GTRS-Aug多配置约42-45;GTRS-E-Lite 46.6;挑战获胜GTRS-E(集成全部)49.4,接近特权方法。动态提案与词汇联合+dropout带来增益。

Navhard合成数据存在畸变模糊伪影,可能损害传感器规划器;超密词汇与高分辨率/大骨干计算开销较高;extract未详述失败场景或长尾边界,域外主要靠旋转扰动,其他传感器退化待进一步验证。

与前序 / 同期 / 后续方法的关系

Section titled “与前序 / 同期 / 后续方法的关系”

多模态规划与评分:对比静态大词汇(Hydra-MDP等)与动态小提案;生成器继承Diffusion Policy/Transfuser BEV;评分基于Hydra-MDP架构改进;对比LTF、PDM-Closed等;定位为同时处理粗/细分布的统一评分框架。

官方将开源https://github.com/NVlabs/GTRS。建议按三支柱分别训练后推理集成,复现注意超密词汇构建、dropout比例、旋转扰动与EMA细化、Navhard两阶段EPDMS评估;骨干初始化(StreamPETR/Depth Anything等)与分辨率配置见表。

摘要与引言问题动机 → Fig1/Sec2三支柱(2.1 DP、2.2 Dense、2.3 Aug)→ Fig2推理集成Sec3 → Table1路线图消融 → Sec4实验与Table2主结果 → 代码与后续。

  1. Q: GTRS解决的核心泛化矛盾是什么? A: 静态大词汇缺乏细粒度适应,动态小提案训练分布窄难泛化未见轨迹;需同时在粗与细分布上训练评分器。
  2. Q: Vocabulary Generalization的关键训练技巧是什么?为何有效? A: 在超密VXL(16384)上训练并对半dropout,推理用较小VL或Vdp∪VL;制造训练-推理不匹配、对齐token数、正则防过拟合,从而泛化到未见分布。
  3. Q: 推理时为何将动态提案附加到静态词汇而非训练时联合? A: 训练纯静态多样词汇获鲁棒泛化;推理注入场景感知细粒度提案;避免训练集成扩散采样的计算开销与不稳定。
  4. Q: GTRS-Aug如何提升域外与细粒度判别? A: 对输入图像做可控2D水平旋转扰动并同步变换GT;附加top-k细化Decoder,用EMA教师自蒸馏+clip软目标优化相似轨迹区分。
  5. Q: 主结果中GTRS-E相对PDM-Closed如何?证据何在? A: GTRS-E(集成)EPDMS 49.4接近PDM-Closed(GT感知)51.3,见Table2,证明传感器方法可逼近特权规划。
  • Abstract / page 1: As the winning solution of the Navsim v2 Challenge, GTRS demonstrates superior performance even with sub-optimal sensor inputs, approaching privileged methods that rely on ground-truth perception. Code will be available at https://github.com/NVlabs/GTRS.
  • Sec 1 / page 1-2: GTRS consists of three complementary innovations: (1) a diffusion-based trajectory generator… (2) a vocabulary generalization technique that trains a scorer on super-dense trajectory sets with dropout regularization… (3) a sensor augmentation strategy that enhances out-of-domain generalization while incorporating refinement training…
  • Sec 2.2 / page 2: we deliberately train on a super-dense trajectory vocabulary (VXL with 16,384 distinct trajectories)… while inferencing on a smaller vocabulary (VL with 8,192 trajectories)… we apply vocabulary dropout to VXL during training, randomly removing half of the trajectories in each batch.
  • Table 1 / page 3: GTRS-Dense … VXL (Dropout) … Vdp ∪ VL … 73.1 59.0 43.4 … GTRS-Aug … 75.0 56.9 43.4
  • Table 2 / page 4: PDM-Closed … 51.3 … GTRS-E … 49.4 … GTRS-E-Lite … 46.6
  • Sec 3 / page 3: The dynamic proposals generated by the generator Vdp are appended to the inference vocabulary VL , and the combined set Vdp ∪ VL is tokenized and scored by the scorer.
Topic Evidence-backed note Source Short original cue
Problem A planner can fail either because candidates do not cover good behavior or because the scorer cannot select the right candidate. [PDF p.1, Abstract] Introduction
Representation The note treats the method as trajectory proposals + generalized scorer because the paper’s method pages introduce the relevant representation/module vocabulary. [PDF p.3, Method] Method
Core mechanism Combine diffusion-based proposals, vocabulary generalization, sensor augmentation, and refinement training for robust scoring. [PDF p.3, Method] trajectory scoring
Input / Output Input: NAVSIM scene features and candidate trajectories. Output: ranked trajectory candidates. [PDF p.3, Method] NAVSIM
Training / Evaluation The paper reports NAVSIM-style planning performance; local reproduction needs benchmark assets. [PDF p.3, Method] PDMS
Relationship SparseDriveV2 also focuses scoring but uses factorized vocabulary/scoring; DiffusionDrive focuses generation. [PDF p.1, Abstract] arXiv:2506.06664v1 [cs.RO] 7 Jun 2025 Generalize
Failure/Risk Candidate coverage, vocabulary/scorer mismatch, NAVSIM version, and OOD sensor augmentation settings are critical. [PDF p.3, Method] trajectory scoring
Reproduction boundary Needs NAVSIM, trajectory statistics, and checkpoint assets. [PDF p.3, Method] NAVSIM
Local path Why it matters
92a740def80610e4096962d25cc837b21e72ef78:README.md Code/repo anchor for implementation cross-check.
92a740def80610e4096962d25cc837b21e72ef78:navsim/agents/gtrs_aug/hydra_config_aug.py Code/repo anchor for implementation cross-check.
92a740def80610e4096962d25cc837b21e72ef78:navsim/agents/gtrs_dense/hydra_config.py Code/repo anchor for implementation cross-check.
92a740def80610e4096962d25cc837b21e72ef78:navsim/planning/script/config/common/agent/gtrs_aug_vov.yaml Code/repo anchor for implementation cross-check.
92a740def80610e4096962d25cc837b21e72ef78:navsim/planning/script/config/common/agent/gtrs_dense_vov.yaml Code/repo anchor for implementation cross-check.
92a740def80610e4096962d25cc837b21e72ef78:navsim/planning/script/config/common/agent/gtrs_diffusion_policy.yaml Code/repo anchor for implementation cross-check.
  • Treat this note as paper/code reading material first; do not interpret mini-data smoke tests as paper reproduction. [PDF p.3, Method]
  • Before running experiments, verify the local code entry points above against the paper method terminology and dataset protocol. [PDF p.3, Method]
  • If a claim is not linked to a PDF page or code path in this note, treat it as an implementation hypothesis rather than established paper fact.
  • topic: ad-end-to-end-driving
  • sources: arxiv, openalex
  • retrieved_at: 2026-07-20
  • query: end-to-end autonomous driving planning perception
  • arxiv: 2506.06664
  • doi: 10.48550/arxiv.2506.06664
  • score_total: 66
  • suggested_tier: recent

(no prose relevance explanation — numeric score only or HTTP source)

(no snippet evidence in candidate pool)

生成:2026-07-21 · 来源条数 2 · 模型 heuristic · 需人工核验数字

围绕「GTRS: Generalized Trajectory Scoring for End-to-end Multimodal Planning」的核心问题与动机(待结合全文核验)。

  • 见原文方法章节;以下为基于摘要/摘录的要点提示。
  • Generalized Trajectory Scoring for End-to-end Multimodal Planning Zhenxin Li1, 2 Wenhao Yao2 Zi…

与相近工作的关系待核验;请对照 related work。

  • 勿仅凭摘要推断未给出的数值指标。
  1. 这篇工作的输入/输出表示是什么?(GTRS: Generalized Trajectory Scoring for End-to-end Multimodal Planning)
  2. 训练目标与评测协议各是什么?
  3. 主要失败模式或局限是什么?
flowchart LR
A["输入 / 观测"] --> B["表示 / 编码"]
B --> C["推理 / 解码"]
C --> D["输出 / 动作或检测"]
%% method sketch for: GTRS: Generalized Trajectory Scoring for End-to-end Multimodal Planning

方法结构示意(重绘;细节以原论文为准,待 PDF 核验)。

GTRS: Generalized Trajectory Scoring for End-to-end Multimodal Planning arch p.1

来源:原论文约 p.1(arch);学习用途摘录。

展开英文 Paper Card / AI deep analysis
Field Content
One-line takeaway GTRS separates candidate trajectory generation from generalized scoring to improve multimodal planning selection.
Problem A planner can fail either because candidates do not cover good behavior or because the scorer cannot select the right candidate.
Representation trajectory proposals + generalized scorer
Input / Output Input: NAVSIM scene features and candidate trajectories. Output: ranked trajectory candidates.
Core Mechanism Combine diffusion-based proposals, vocabulary generalization, sensor augmentation, and refinement training for robust scoring.
Training / Evaluation The paper reports NAVSIM-style planning performance; local reproduction needs benchmark assets.
Reproduction Status Needs NAVSIM, trajectory statistics, and checkpoint assets.
Compare With SparseDriveV2 also focuses scoring but uses factorized vocabulary/scoring; DiffusionDrive focuses generation.
Failure/Risk Candidate coverage, vocabulary/scorer mismatch, NAVSIM version, and OOD sensor augmentation settings are critical.
展开 Extract / Selections / Local assets
Anchor What to verify Source Short original cue
Title and abstract Use to verify paper identity and top-level contribution. [PDF p.1, Abstract] GTRS: Generalized Trajectory Scoring for End-to-end Multimodal Planning
Motivation Use to verify the problem statement and why the work is needed. [PDF p.1, Abstract] Introduction
Core method Use to verify the main modeling mechanism and module names. [PDF p.3, Method] Method
Key module terms Use to verify exact component names before editing the note. [PDF p.3, Method] trajectory scoring
Dataset and protocol Use to verify data dependencies: NAVSIM. [PDF p.3, Method] NAVSIM
Metrics and results Use to verify metric names and reported benchmark context. [PDF p.3, Method] PDMS
Experiments or ablation Use to verify which claims are experimentally supported. [PDF p.3, Method] Experiments
Position in related work Use to verify the claimed relationship to neighboring methods. [PDF p.1, Abstract] arXiv:2506.06664v1 [cs.RO] 7 Jun 2025 Generalize
Conclusion or limits Use to verify final claims and remaining constraints. [PDF p.1, Abstract] Limitations