risk_aware_path — DRIVE `roverslip` op

• Data kinds: table × any × any → table

• Call: import fullseye as fs; fs.ledger.risk_aware_path(cost_map, start, goal) -> 'dict' (to call the implementation directly, import roverslip; roverslip.risk_aware_path(cost_map, start, goal) -> 'dict'; from the registry, opsdrive.get("risk_aware_path"))

Usage

8-neighbor Dijkstra (directed edges — uphill and downhill differ) on the edge travel times of cvar_cost_map.

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

start・goal は (行, 列)。返り値 {"path": (n, 2) の添字, "cost": 合計の所要時間 [s] (届かなければ inf), "reached": bool, "cost_to_come": (H, W)}。届かないときは path が空。

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_rover_slip_risk_path — py -3.11 examples/poc_rover_slip_risk_path.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 (`roverslip`)

bekker_pressure · bekker_wheel_sinkage · wheel_forces · wheel_sinkage · wheel_traction_curve · slope_slip_curve · ground_shift_track · odometry_slip

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

risk_aware_path — DRIVE roverslip op