Ga naar inhoud
drawtonomy drawtonomy

OpenSCENARIO editor — visual, browser-based scenario authoring

Deze inhoud is nog niet vertaald.

drawtonomy is a free, browser-based OpenSCENARIO editor. You draw the road (or import an existing .xodr), place the actors, and then build the whole storyboard visually — phases, events, 35 actions, and 19 trigger conditions — on a canvas instead of by hand in XML. Because the embedded esmini-WASM engine ships in the same browser tab, you run the scenario the moment you finish it and read a PASS / FAIL verdict — no local install, no round-trip to a simulator. When it does what you meant, export standard ASAM OpenSCENARIO 1.2 .xosc together with the OpenDRIVE .xodr it runs on, bundled as an esmini-ready zip.

Draw a road, place a vehicle, build a phase with Change Speed and Change Lane events, and run it in the browser.

How it compares to other scenario authoring tools

Section titled “How it compares to other scenario authoring tools”
  • esmini — the reference OpenSCENARIO player and runtime, with a rich command-line and library API. drawtonomy exports scenarios that esmini plays.
  • MathWorks RoadRunner Scenario — a scenario-authoring add-on for RoadRunner. Commercial.
  • Cognata / Foretellix Foretify — enterprise scenario platforms. Commercial.
  • scenariogeneration / py-scenariogeneration — Python libraries for generating .xodr + .xosc programmatically.

drawtonomy is the browser-based, visual, free option that lets you both author the storyboard and run it in the same tab. It doesn’t try to replace esmini as a runtime at scale or RoadRunner Scenario’s commercial toolchain — it makes the common case (build a scenario, watch it run, check the verdict, export standard XML) fast and installation-free.

Because the export is standard ASAM XML, it bridges straight out to the reference runtime: the same .xosc + .xodr you author here run unmodified in native esmini, no drawtonomy involved at playback.

One take: draw the scene, export the esmini zip, then replay the exported .xosc in native esmini — the standard XML plays as-is.

When to reach for drawtonomy

Section titled “When to reach for drawtonomy”
  • You want to author an ADAS test scenario (cut-in, lane change, unprotected left, lead-vehicle braking, pedestrian crossing, roundabout entry) visually and get a runnable .xosc out.
  • You want to run it and see a verdict — set END and FAIL conditions and read PASS / FAIL in the browser, without a local esmini install.
  • You want to review or edit an existing .xosc with a stakeholder who doesn’t read OSC XML — open it, inspect the phases, tweak, re-run.
  • You want to go from a visual storyboard to a standard, portable esmini-ready zip in one export.

From canvas to a running scenario

Section titled “From canvas to a running scenario”

You build the whole scenario on the canvas and never have to open a text editor to make it run.

What the editor gives you

Section titled “What the editor gives you”
  • A visual storyboard: phases and events with actor rows, start conditions, and execution order — the OpenSCENARIO Story / Act / ManeuverGroup structure, composed by clicking rather than nesting XML by hand.
  • 35 actions — Change Speed, Change Lane, Follow Path, Teleport, controllers, traffic sources, trailers, lights, and more — and 19 trigger conditions: simulation time, time gap, time to collision, distance, speed, storyboard element state, and the advanced conditions.
  • END and FAIL conditions: separate when a run stops from whether it passed, turning any scenario into a PASS / FAIL check.
  • In-browser playback on the embedded esmini-WASM engine — seek the timeline, Follow Ego, ghost motion trails, the verdict badge, and a .webm recording of the run.
  • A standard ASAM OpenSCENARIO 1.2 .xosc + OpenDRIVE .xodr export, bundled with a run.sh so any esmini install plays it.

Honest limits

Section titled “Honest limits”

The editor covers the storyboard you can compose on the canvas — not the whole OpenSCENARIO 1.x spec. Parameter sweeps and value distributions, custom or plugged-in controllers beyond the built-in set, simulator-specific extensions, and OpenSCENARIO 2.x / M-SDL are outside what the UI expresses. If you need any of those, the exported .xosc is a clean, standard starting point you can extend in code or by hand. For scenario fleets, generate from a DSL (scenariogeneration or similar) rather than by hand on a canvas.

The workflow

Section titled “The workflow”
  1. Draw or import the road network. Lane Tool, Intersection Templates, and Crosswalk shapes — or import an existing OpenDRIVE .xodr.
  2. Place the actors. Ego on a specific lane, other entities at known longitudinal offsets.
  3. Build the storyboard. Switch to Scenario mode and compose phases, events, actions, and triggers in the scenario editor.
  4. Run it in the browser. Press ▶, seek, Follow Ego, and read the PASS / FAIL verdict. Iterate until it does what you meant.
  5. Export the esmini bundle — standard .xosc + .xodr + run.sh — and take it to any esmini install or extend it further.
Section titled “Related reading”