Scenario Builder for MATLAB

When to Use

• User has recorded driving data (GPS/GNSS, camera, lidar, actor tracks) and needs to convert it into a simulation-ready scenario
• User asks to export trajectories or scenarios to RoadRunner, drivingScenario, ASAM OpenSCENARIO, OpenDRIVE, ASAM OpenCRG, or Unreal Engine. Default target is RoadRunner — only generate a standalone drivingScenario object and open Driving Scenario Designer when the user explicitly asks for "DSD", "Driving Scenario Designer", drivingScenarioDesigner, or "build a drivingScenario object" (Workflow 15).
• User mentions safety standards (SOTIF / ISO 21448, ISO 26262) and scenario coverage from real-world data
• User needs to extract a road surface (OpenCRG) from lidar for vehicle-dynamics or chassis testing
• User needs to add elevation to an HD map, georeference point clouds, or extract per-frame point clouds along an ego path
• User needs to localize an ego trajectory on a map using lane detections (RVLD preferred, CLRNet fallback)
• User needs to add static objects (signs, trees, poles, buildings, barriers) to a RoadRunner HD Map from cuboid detections
• User wants to augment / enhance / improve a road scene from aerial lidar — adding trees + buildings (Variant A) or improving OSM elevation / banking / gradient / height only (Variant B) — see Workflow 16
• User wants to add traffic signs from recorded camera + lidar logs with pre-detected sign bounding boxes — see Workflow 17
• User needs to generate 3D mesh assets from a single camera image
• User needs to extract critical scenario events (cut-ins, hard brakes, near-misses) from recorded drives
• User needs accurate non-ego tracks via sensor fusion (multiSensorTargetTracker) before scenario building
• User mentions multi-sensor preprocessing: synchronization, alignment, offset correction, cropping, timestamp normalization

When NOT to Use