commonroad op• Data kinds: table × table → any
• Call: import fullseye as fs; fs.ledger.cr_solution_xml(scene, run, *, vehicle_model: 'str' = 'KS', vehicle_type: 'str' = 'BMW_320i', cost: 'str' = 'JB1', benchmark_version: 'str' = '2020a', date=None) -> 'str' (to call the implementation directly, import drivecommonroad; drivecommonroad.cr_solution_xml(scene, run, *, vehicle_model: 'str' = 'KS', vehicle_type: 'str' = 'BMW_320i', cost: 'str' = 'JB1', benchmark_version: 'str' = '2020a', date=None) -> 'str'; from the registry, opsdrive.get("cr_solution_xml"))
Returns the official solution XML (same form as commonroad-io CommonRoadSolutionWriter) as a string.
> The detailed description below is the original text — the summary and the headings are translated.
<CommonRoadSolution benchmark_id="KS2:JB1:<scenario id>:2020a" date="YYYY-MM-DDTHH:MM:SS"> の中に <ksTrajectory planningProblem="<pp id>"> と ksState{x, y, steeringAngle, velocity, orientation, time}。位置は 車両中心(run["x"], run["y"])。date を渡すと再現可能(省略で今)。
Raises ValueError: vehicle_model が "KS" 以外(状態が KS の物なので)、vehicle_type が未知、run が不正。
• Sample-data catalog (download URLs / licences) — 2-D uses skimage.data (BSD/public domain) plus synthetic images; 3-D lists download URLs for real data sources (Stanford, PDS, …).
• Operator provenance and references — the sources of the research/methods this op family came from.
• The canonical algorithm (author, year) and its uses are named in the family usage guide above.
• poc_driving_commonroad — py -3.11 examples/poc_driving_commonroad.py
any as input)course_crank · course_s_curve · course_turnaround · course_slope · course_intersection · course_parallel_parking · course_crossing · course_road
commonroad)cr_synthetic · cr_read · cr_route · ks_step · cr_drive · cr_drive_sweep · cr_feasible · cr_collision
*Provenance: drivecommonroad.py — DRIVE operator registry. This per-op note is generated by tools/opdocs.py md (do not hand-edit).*
© 2026 Kazufumi Furuse — Fullseye operator documentation. Licensed under Apache-2.0.