naive_execute — DRIVE `agv` op

• Data kinds: table → table

• Call: import fullseye as fs; fs.ledger.naive_execute(paths, delay_prob=0.3, seed=0, max_steps=10000) (to call the implementation directly, import agvfleet; agvfleet.naive_execute(paths, delay_prob=0.3, seed=0, max_steps=10000); from the registry, opsdrive.get("naive_execute"))

Usage

Naive execution for comparison: uses only the plan's sequence of cells and advances whenever the next cell is free (no ordering agreement).

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

遅れが入ると、計画では時間差ですれ違うはずの 2 台が向かい合って止まる。返りは adg_execute と同じ形に waits_for(デッドロックの瞬間の「誰が誰を待つか」の辺)を足したもの。

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_conflicts · plan_cost

*Provenance: agvfleet.py — DRIVE operator registry. This per-op note is generated by tools/opdocs.py md (do not hand-edit).*

naive_execute — DRIVE agv op