Frontend
Scenario Orchestration for Closed-loop Policy Evaluation of Autonomous Driving
arXiv cs.RO0 views
arXiv:2611.09888v1 Announce Type: new Abstract: Scenario-based simulation is central to evaluating autonomous-driving policies, but a scenario scripted before execution (i.e., with predetermined, fixed actor routes and speeds) may not preserve its intended interaction once the tested ego policy responds in closed loop. Scripted scenarios cannot adapt to unanticipated ego behavior, while learned traffic actors may remain reactive without reliably realizing a particular scenario intent. We introduce a scenario orchestrator that continuously monitors the joint traffic state and adapts non-ego actors through re-timing, re-routing, and role reassignment for creating a specific scenario intent. At each step, the orchestrator solves a constrained optimization problem that preserves the intended interaction while limiting interventions and maintaining traffic feasibility. We further distinguish scenario realization from policy failure, allowing a test to first be judged based on whether the intended interaction occurred and then by how the ego policy responded. Experiments in the CARLA simulator across multiple scenario families and driving policies show that orchestration realizes targeted interactions more reliably than scripted and learned actor-level baselines, particularly under variations in initial conditions and ego behavior. These results support closed-loop scenario orchestration as a tool for controlled and reproducible policy evaluation.
Source:https://arxiv.org/abs/2611.09888PreviousLocating Contact on Tendon-Driven Continuum Robots From Tendon Measurements Alone via Constrained Moving Horizon EstimationNextOn Agentic Manipulation Policies
Related posts

Beyond RAG: The Evolution of AI Knowledge & Memory : From LLMs to Vectorless RAG, LLM Wiki, and Memory
0dev.to Tutorial
We ran a launch check on 312 AI-built apps. Most of what's missing isn't code.
0dev.to Beginners
I have been working on CSS
0dev.to Beginners
I built 10 free dev & QA tools that run in your browser, then tested them like production
0dev.to Testing
Trying the Rust rewrite of Office: build steps, what works, and limits
0dev.to OpenSource
Your failed email runs can keep charging start fees
0dev.to TypeScript