RoadRunner and OpenSCENARIO terms — a translation table
本頁內容尚未翻譯。
If you already know MathWorks RoadRunner Scenario, most of drawtonomy’s scenario editor will feel familiar — the two tools organise the same problem in similar ways, and both speak ASAM OpenSCENARIO. The vocabulary differs in places. This page lines the three up.
RoadRunner Scenario is a mature commercial desktop product with a 3D canvas, an asset library, built-in vehicle behaviours, co-simulation with CARLA and Simulink, and a gRPC API. drawtonomy is a free browser-based 2D editor. They are not the same tool; the point of this page is that the concepts transfer.
The core map
Section titled “The core map”| RoadRunner Scenario | drawtonomy | OpenSCENARIO 1.x |
|---|---|---|
| Scene Editing mode | Scene mode | — |
| Scenario Editing mode | Scenario mode | — |
| Logic editor | the LOGIC card | Storyboard |
| Action Phase | Phase | Act |
| — (actions live in phases) | Event | Event |
| Actor | Actor | ScenarioObject / Entities |
| Condition | TRIGGER | StartTrigger |
| End condition | END CONDITIONS | StopTrigger |
| Fail condition | FAIL CONDITIONS | (vendor-specific) |
| Attributes pane | the attribute panel | — |
| Library Browser (assets) | the TEMPLATE list | Vehicle / Pedestrian catalogs |
| Scenario Parameters, Variables | the {x} panel | ParameterDeclarations, VariableDeclarations |
Both products share the Scene / Scenario mode split, and for the same reason: the road is a separate artefact from the behaviour that runs on it.
Where the structures differ
Section titled “Where the structures differ”The one real structural difference is how behaviour is sequenced.
RoadRunner Scenario chains action phases per actor, with conditions sitting between them as circular nodes. Each condition determines when the phase immediately before it ends, and the next phase begins. Behaviour reads as a chain.
drawtonomy puts events inside a phase, and every event carries
its own TRIGGER. A phase has a Start condition of its own, and
events inside it fire whenever their trigger is satisfied. Behaviour
reads as a set of triggered rules rather than a chain. This mirrors
OpenSCENARIO’s own model, where an Act has a StartTrigger and each
Event has one too.
Practically: what RoadRunner writes as phase → condition → phase, drawtonomy writes as two events with different triggers in the same phase.
One more difference in naming: RoadRunner creates an initial action phase per actor for its starting state. drawtonomy keeps the starting state on the actor itself — the Set initial speed checkbox in the placement panel — and reserves phases for behaviour.
Actions
Section titled “Actions”| RoadRunner Scenario | drawtonomy | OpenSCENARIO 1.x |
|---|---|---|
| Change Speed | Change Speed | SpeedAction |
| Change Lane | Change Lane | LaneChangeAction |
| Change Lateral Offset | Lateral Offset | LaneOffsetAction |
| Change Longitudinal Distance | Keep Longitudinal Distance | LongitudinalDistanceAction |
| Path Following | Follow Path | FollowTrajectoryAction |
| — | Teleport | TeleportAction |
| — | Drive to Position | AcquirePositionAction |
drawtonomy exposes 35 actions in total, one per OpenSCENARIO action element.
Conditions
Section titled “Conditions”| RoadRunner Scenario | drawtonomy | OpenSCENARIO 1.x |
|---|---|---|
| Simulation Time | Simulation time | SimulationTimeCondition |
| Actor Speed | Actor speed | SpeedCondition |
| Distance to Actor | Distance to actor | RelativeDistanceCondition |
| Distance to Point | Distance to point | DistanceCondition |
| Collision | Collision | CollisionCondition |
| Duration | Duration (fail conditions only) | — |
| Time Gap | Time gap to actor | TimeHeadwayCondition |
| — | Phase / event state | StoryboardElementStateCondition |
The full list is on the triggers reference.
Both tools default a new scenario to failing on collision. In
RoadRunner that default arrives with the actor’s initial phase; in
drawtonomy the FAIL CONDITIONS section starts with
Collision / Any actor already in place.
Terms drawtonomy uses inconsistently
Section titled “Terms drawtonomy uses inconsistently”Two notes so the docs and the UI do not trip you up:
- Actor, participant, and entity all mean the same thing. The
drawing toolbar calls the tool Participants, the scenario toolbar
says Add actor, the attribute panel heading is ACTORS, and
OpenSCENARIO calls them
ScenarioObjects. These docs say actor throughout. - There is no button named “Run”. The ▶ button on the LOGIC card
starts the scenario;
RUNis the verdict badge shown while it is going.
Moving a scenario between the tools
Section titled “Moving a scenario between the tools”RoadRunner Scenario exports ASAM OpenSCENARIO XML, and drawtonomy
imports it. Export the .xosc together with the OpenDRIVE .xodr for
the scene, then drop both onto the drawtonomy canvas — see
Open and play an existing .xosc. Acts
arrive as phases with their original names, and events keep their
triggers, actions, and priorities.
Going the other way, drawtonomy exports .xosc + .xodr from
Hamburger → Export. See
Export OpenDRIVE + OpenSCENARIO.
Expect a lossy trip in both directions. Anything expressed as a tool-specific behaviour, asset, or built-in logic has no OpenSCENARIO representation to travel in, and the standard’s own coverage of 3D assets is limited by design. What does travel reliably is the part that matters most for review: road network, entities, and storyboard.