{"id":"7524d5e8-4b72-4b70-b472-b45b20f3bd34","arxiv_id":"2606.26533","paper_version":1,"verdict":"UNVERDICTED","confidence":"LOW","novelty_score":7.0,"correctness_risk":"unknown","formal_verification":"none","parameter_count":0,"one_line_summary":"OSC2Runner is the first native orchestration framework mapping OpenSCENARIO v2.x DSL to CARLA via a multi-pass transpiler to dynamic behavior trees, claiming tick-by-tick determinism and exact trigger evaluation.","lead":"The paper introduces OSC2Runner, a new framework that translates OpenSCENARIO 2.x scenarios into executable behavior trees for the CARLA simulator. This could allow more precise and deterministic testing of autonomous vehicle behaviors in complex scenarios.","discovery_kind":"new_method","skeptic_critique":{"model":"grok-4.3","headline":"Central claim of 'mathematically rigorous execution' rests on empirical determinism results rather than a verified semantic equivalence between v2.x DSL and generated py_trees.","rationale":"The reader's weakest assumption correctly isolates the unverified semantic-preservation step that the empirical results alone cannot close. No additional internal inconsistency or stronger formal evidence appears in the supplied abstract and claim wording.","tokens_in":1716,"tokens_out":310,"duration_ms":13007,"concrete_test":"Extract the transpiler passes from §3–4 and the full set of v2.x constructs exercised in the case studies; for each construct, manually derive the expected state transition sequence from the OpenSCENARIO 2.x language spec and compare it against the emitted py_tree execution trace on a single deterministic replay; any mismatch in trigger timing or actor state constitutes a semantic gap.","verdict_should_be":"UNCHANGED","load_bearing_attack":"The strongest claim requires that the multi-pass transpiler produces py_trees whose runtime behavior is exactly equivalent to the OpenSCENARIO 2.x specification for all constructs, including complex event chains and spatial triggers. The described validation (tick-by-tick determinism, 100 ms blackboard sync, kinematic boundary adherence) shows practical fidelity in selected adversarial cases but supplies no formal semantics, bisimulation argument, or exhaustive equivalence proof. Without such a mapping, it remains possible that CARLA atomic API translations introduce untested divergences in timing, state updates, or nondeterministic scheduling that the empirical suite does not expose.","agreement_with_reader":"agree"},"referee_report":{"model":"grok-4.3","summary":"The manuscript presents OSC2Runner, a framework for natively executing OpenSCENARIO 2.x DSL scenarios in CARLA. It uses a multi-pass transpiler to synthesize type-safe ASTs into dynamic py_trees mapped to CARLA atomic APIs, bypassing static trajectory playback. Empirical validation in concurrent adversarial cases shows tick-by-tick determinism, exact spatial trigger evaluation, 100 ms blackboard synchronization, and kinematic boundary adherence, claiming this establishes mathematically rigorous execution for scenario-based testing, co-simulation, and LLM-driven pipelines.","tokens_in":1836,"tokens_out":320,"duration_ms":23501,"significance":"If the transpiler preserves exact v2.x semantics without introducing drift or latency, the work would provide a practical deterministic backend that addresses longstanding limitations of 1.x interpreters, enabling more reliable hardware-in-the-loop testing and automated scenario generation in autonomous vehicle research.","major_comments":[{"comment":"Abstract: The central claim that the architecture transitions Scenario-Based Testing to 'mathematically rigorous execution' and that 'kinematic analysis proves the strict adherence' is not supported by a formal semantic mapping, bisimulation, or equivalence proof between OpenSCENARIO 2.x constructs (including complex event chains and spatial triggers) and the generated py_trees. Only empirical results from selected adversarial cases are described, which cannot rule out untested divergences in timing, state updates, or nondeterministic scheduling as noted in the stress-test concern.","section":"Abstract"}],"minor_comments":[],"recommendation":"major_revision","confidential_remarks":null},"author_rebuttal":{"model":"grok-4.3","summary":"We thank the referee for the detailed feedback. We address the concern regarding the abstract claims below.","responses":[{"response":"We agree that the abstract overstates the contribution by using the phrases 'mathematically rigorous execution' and 'kinematic analysis proves the strict adherence' without providing a formal semantic mapping, bisimulation, or equivalence proof. The validation relies on empirical results from selected adversarial cases, which do not constitute a complete proof against all possible divergences. We will revise the abstract to remove these stronger claims and instead describe the empirical demonstration of tick-by-tick determinism, exact trigger evaluation, and boundary adherence in the evaluated scenarios.","revision_made":"yes","referee_comment":"[Abstract] Abstract: The central claim that the architecture transitions Scenario-Based Testing to 'mathematically rigorous execution' and that 'kinematic analysis proves the strict adherence' is not supported by a formal semantic mapping, bisimulation, or equivalence proof between OpenSCENARIO 2.x constructs (including complex event chains and spatial triggers) and the generated py_trees. Only empirical results from selected adversarial cases are described, which cannot rule out untested divergences in timing, state updates, or nondeterministic scheduling as noted in the stress-test concern."}],"tokens_in":1326,"tokens_out":273,"duration_ms":10598,"standing_objections":[]},"desk_editor":{"model":"grok-4.3","letter":"The main point for you is that this paper ships a concrete compilation pipeline that takes the v2.x DSL, builds type-safe ASTs, and emits deterministic behavior trees mapped straight to CARLA atomic APIs. That is new; earlier work either stayed on 1.x XML or layered approximate interpreters on top.\n\nIt handles the stated problems of spatiotemporal drift and event latency by avoiding static playback altogether. The reported tick-by-tick determinism, 100 ms blackboard sync, and kinematic boundary checks in concurrent adversarial cases show the implementation can stay stable under load. That is useful engineering for anyone who needs repeatable scenario execution.\n\nThe soft spot is the jump from those results to 'mathematically rigorous execution.' The validation is empirical and case-based; there is no bisimulation argument, formal semantics mapping, or exhaustive equivalence check for the full language, including nested triggers and event chains. Without that, it remains possible that some constructs produce untested timing or state differences once the generated trees run. The paper would be stronger if it separated the practical fidelity claims from the stronger semantic ones.\n\nThis is for simulation and AV testing groups that already use CARLA and want native v2.x support. A reader who needs a working bridge between the standard and the simulator will get value from the architecture description and the reported numbers.\n\nIt deserves peer review. The contribution is a real implementation that fills a documented gap, even if the rigor language needs calibration.","headline":"OSC2Runner gives a practical transpiler from OpenSCENARIO 2.x to CARLA py_trees, but the 'mathematically rigorous' label rests only on selected empirical runs.","tokens_in":2290,"tokens_out":376,"would_cite":false,"duration_ms":17042,"reading_group":"maybe","serious_thinker":"yes","would_accept_peer_review":true},"rs_alignment":null,"lean_confirmation":null,"pith_extraction":{"msc":[],"pacs":[],"model":"grok-4.3","headline":"OSC2Runner compiles OpenSCENARIO 2.x DSL into deterministic py_trees for native CARLA execution.","keywords":["OpenSCENARIO 2.x","CARLA simulator","autonomous vehicle testing","behavior trees","scenario-based testing","transpiler","deterministic simulation"],"falsifier":"Execute a set of highly concurrent adversarial scenarios and verify whether every spatial trigger evaluates to the exact expected value on each simulation tick and whether any kinematic snapping or timing drift appears in the recorded trajectories.","tokens_in":2616,"feed_emoji":"🚗","tokens_out":681,"duration_ms":13098,"temperature":0.7,"pith_summary":"The paper introduces OSC2Runner as the first orchestration framework that maps the OpenSCENARIO v2.x domain-specific language directly onto the CARLA simulator. It achieves the mapping by treating scenario translation as a compilation pipeline that runs through a multi-pass transpiler to produce type-safe abstract syntax trees and then dynamic deterministic behavior trees. These trees connect straight to CARLA's atomic APIs instead of relying on static trajectory playback or legacy interpreters. A sympathetic reader would care because the approach removes spatiotemporal drift, event latencies, and kinematic snapping that previously limited the reliability of scenario-based testing for autonomous vehicles. The result supplies the deterministic execution layer needed for co-simulation, hardware-in-the-loop setups, and automated scenario generation.","feed_headline":"Transpiler turns OpenSCENARIO 2.x into exact CARLA behavior trees","feed_subtitle":"Multi-pass architecture produces tick-by-tick deterministic py_trees from DSL, removing drift in AV scenario execution.","key_machinery":"The multi-pass transpiler architecture that converts OpenSCENARIO v2.x DSL into type-safe ASTs and then into py_trees behavior trees mapped to CARLA atomic APIs.","core_discovery":"OSC2Runner formalizes scenario translation as a compilation pipeline through a multi-pass transpiler architecture. The architecture synthesizes type-safe Abstract Syntax Trees directly into dynamic deterministic behavior trees natively mapped to CARLA's atomic APIs. Empirical validation in highly concurrent adversarial case studies demonstrates tick-by-tick determinism, exact spatial trigger evaluation, and 100.0 ms cross-actor blackboard synchronization, while kinematic analysis confirms strict adherence to continuous environmental boundaries.","pith_inferences":["The same transpiler pattern could be adapted to other simulators that expose atomic APIs, extending deterministic execution beyond CARLA.","Tick-by-tick determinism may allow testing pipelines to replace statistical sampling with exhaustive replay of critical scenarios.","The blackboard synchronization mechanism could serve as a template for multi-agent coordination in other real-time simulation domains."],"forward_implications":["Scenario-Based Testing moves from approximate behavioral interpretation to mathematically rigorous execution.","The deterministic backend supports co-simulation and hardware-in-the-loop testing.","Automated LLM-driven generation pipelines gain a reliable execution target.","Kinematic analysis shows strict adherence to continuous environmental boundaries in all tested cases."],"fun_headline_variants":["OSC2Runner transpiles OpenSCENARIO 2.x DSL into CARLA py_trees","Multi-pass transpiler maps OpenSCENARIO 2.x to CARLA behavior trees","OSC2Runner compiles OpenSCENARIO 2.x DSL to CARLA behavior trees","Compilation pipeline maps OpenSCENARIO 2.x to CARLA py_trees"],"cache_read_input_tokens":2112,"weakest_assumption_plain":"The multi-pass transpiler correctly synthesizes type-safe ASTs into py_trees that preserve exact OpenSCENARIO v2.x semantics when mapped to CARLA atomic APIs without introducing spatiotemporal drift or asynchronous latencies.","fun_headline_variants_meta":{"raw":{"variants":["OSC2Runner transpiles OpenSCENARIO 2.x DSL into CARLA py_trees","Multi-pass transpiler maps OpenSCENARIO 2.x to CARLA behavior trees","OSC2Runner compiles OpenSCENARIO 2.x DSL to CARLA behavior trees","Compilation pipeline maps OpenSCENARIO 2.x to CARLA py_trees"]},"model":"grok-4.3","cost_usd":0.006827,"raw_usage":{"total_tokens":3178,"prompt_tokens":679,"num_sources_used":0,"completion_tokens":84,"cost_in_usd_ticks":68274500,"prompt_tokens_details":{"text_tokens":679,"audio_tokens":0,"image_tokens":0,"cached_tokens":256},"completion_tokens_details":{"audio_tokens":0,"reasoning_tokens":2415,"accepted_prediction_tokens":0,"rejected_prediction_tokens":0}},"tokens_in":679,"tokens_out":84,"duration_ms":15871,"temperature":1.0,"reasoning_tokens":2415,"cache_read_input_tokens":256,"cache_creation_input_tokens":0},"cache_creation_input_tokens":0},"created_at":"2026-06-26T05:36:15.063386+00:00","model_set":{"reader":"grok-4.3"},"falsifier":"Execute a set of highly concurrent adversarial scenarios and verify whether every spatial trigger evaluates to the exact expected value on each simulation tick and whether any kinematic snapping or timing drift appears in the recorded trajectories.","supporting_citations":[],"review_version":1}