exit_room_check — DRIVE crossing op

• Data kinds: any → table

• Call: import fullseye as fs; fs.ledger.exit_room_check(queue_rear, far_edge: 'float', car_length: 'float', *, gap: 'float' = 1.0, beyond: 'float' = 0.5) (to call the implementation directly, import drivecrossing; drivecrossing.exit_room_check(queue_rear, far_edge: 'float', car_length: 'float', *, gap: 'float' = 1.0, beyond: 'float' = 0.5); from the registry, opsdrive.get("exit_room_check"))

Usage

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

踏切(横断歩道・交差点も同じ)の向こう側に、自分が止まれる余地があるか(50 条 2 項)。配列可。

前の車の後端 `queue_rear の後ろ gap` で止まると、自分の後端 = queue_rear − gap − car_length。これが

far_edge + beyond 以上なら入ってよい。返り値: `room = queue_rear − far_edge、need` = car_length + gap + beyond、

`ok、rear_if_stopped`。前の車が無い場合は queue_rear = +∞。

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_driving_crossing — py -3.11 examples/poc_driving_crossing.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 (crossing)

crossing_timing_check · crossing_gate_state · crossing_lamp_signal · lamp_pair_phase · crossing_clear_time · crossing_stop_check · track_sight_distance · sight_triangle_distance

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