vda5050_order — DRIVE `agv` op

• Data kinds: table → table

• Call: import fullseye as fs; fs.ledger.vda5050_order(path, *, order_id='order-1', order_update_id=0, cell_size=1.0, map_id='floor', allowed_xy=0.05, allowed_theta=0.087, max_speed=1.0, released_nodes=None) (to call the implementation directly, import agvfleet; agvfleet.vda5050_order(path, *, order_id='order-1', order_update_id=0, cell_size=1.0, map_id='floor', allowed_xy=0.05, allowed_theta=0.087, max_speed=1.0, released_nodes=None); from the registry, opsdrive.get("vda5050_order"))

Usage

> This operator's description has not been translated yet. The original text follows as it is.

1 台の計画(マスの列)を VDA 5050 の order(dict)にする。待ちは除き、マスの中心をノードにする。

ノードの `sequenceId` は 0, 2, 4 …(偶数)、エッジは 1, 3, 5 …(奇数)、エッジ数 = ノード数 − 1。

`released_nodes` 個までを base(released=True)、残りを horizon にする(既定 = 全部 base)。

座標は `x = col * cell_size、y = −row * cell_size`(行は下向き、地図の y は上向き)。

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).*

vda5050_order — DRIVE agv op