crossing_timing_check — DRIVE crossing op

• Data kinds: none → table (an op determined by its arguments alone — it takes no image or data input)

• Call: import fullseye as fs; fs.ledger.crossing_timing_check(t_warning, t_closed, t_arrival, *, timing: 'Optional[dict]' = None) -> 'Dict[str, object]' (to call the implementation directly, import drivecrossing; drivecrossing.crossing_timing_check(t_warning, t_closed, t_arrival, *, timing: 'Optional[dict]' = None) -> 'Dict[str, object]'; from the registry, opsdrive.get("crossing_timing_check"))

Usage

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

踏切の 3 つの時刻(警報開始・遮断動作の終了・列車の到達)を解釈基準の標準と最小に照らす(配列 = 列車ごと)。

警報→到達の 30 / 20 秒は解釈基準 5(3) の踏切警報機(遮断機なし)の値。遮断機のある踏切では 4(3)(5) の 2 つ

(15 + 20 = 35 秒が標準)が効き、30 / 20 秒の側は自動的に満たされる。

返り値: `warn_to_closed / closed_to_arrival / warn_to_arrival(各 [s])、meets_minimum`(3 つとも最小以上)、

`deviation(標準からのずれ、3 つ)、spread`(列車ごとの警報開始→到達の最大 − 最小。解釈基準 5(4)「速度等により

大きく異なるものでない」の量)。時刻の順が逆(遮断終了が警報より前など)は ValueError。

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_gate_state · crossing_lamp_signal · lamp_pair_phase · crossing_clear_time · exit_room_check · 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.