elevation_traversability — DRIVE `walkterrain` op

• Data kinds: depth → mask

• Call: import fullseye as fs; fs.ledger.elevation_traversability(grid, cell: 'float' = 0.05, max_step: 'float' = 0.1, max_slope: 'float' = 0.6, window: 'int' = 3) (to call the implementation directly, import terrain; terrain.elevation_traversability(grid, cell: 'float' = 0.05, max_step: 'float' = 0.1, max_slope: 'float' = 0.6, window: 'int' = 3); from the registry, opsdrive.get("elevation_traversability"))

• GPU: none (CPU reference implementation only)

Usage

Traversable cells of an elevation map (True = within the step and slope limits) — ledger door of traversability.

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

中身は traversability と同じ。台帳の名前を変えたのは、1 語の op 名は意味が足りない(<族>_<対象>_<動作>)という名前の規則のため(素の関数の名前は変えない)。step = 窓 window の中の高さの幅、slope = 勾配の大きさ。どちらかが上限を超えるセルと観測していない(nan)セルは False。幅 1 の軸の格子も受ける。

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)

• walking_ops_tour — py -3.11 examples/walking_ops_tour.py

Ops the type connects to (they accept `mask` as input)

spin_from_marker_sequence · carla_transform_matrix · carla_pose_to_world · carla_camera_pose · carla_xy_yaw · carla_scene_load · town_chain · osm_parse

Same category (`walkterrain`)

elevation_map · fill_gaps · foothold_score · ground_surface · ground_plane · detect_obstacles · fuse_elevation · roughness_map

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

elevation_traversability — DRIVE walkterrain op