plan_conflicts — DRIVE agv op

• Data kinds: table → table

• Call: import fullseye as fs; fs.ledger.plan_conflicts(paths) (to call the implementation directly, import agvfleet; agvfleet.plan_conflicts(paths); from the registry, opsdrive.get("plan_conflicts"))

Usage

List of conflicts: same cell at the same time (vertex), passing each other (edge), following (follow).

> The detailed description below is the original text — the summary and the headings are translated.

返りは [(種類, i, j, 時刻, マス)]。着いた車両はその場に居続けるものとして数える。follow は「i が時刻 t にマス v へ入ったとき、j が t-1 に v に居た」(i ≠ j)。

References (sample data, literature)

• 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.

Runnable examples (verified samples that actually call this op)

• poc_agv_fleet — py -3.11 examples/poc_agv_fleet.py

Ops the type connects to (they accept table as input)

course_layout · course_occupancy · course_contains · world_build · world_camera · world_move · lidar_scan · rss_longitudinal_same

Same category (agv)

warehouse_grid · grid_distances · mapf_cbs · mapf_ecbs · mapf_joint_astar · mapf_prioritized · plan_cost · adg_build

*Provenance: agvfleet.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.