town op• Data kinds: table → table
• Call: import fullseye as fs; fs.ledger.town_crossing_state(world: 'dict', t: 'float', train: 'Optional[dict]', *, exposure: 'float' = 0.0) -> 'Dict[str, object]' (to call the implementation directly, import drivetown; drivetown.town_crossing_state(world: 'dict', t: 'float', train: 'Optional[dict]', *, exposure: 'float' = 0.0) -> 'Dict[str, object]'; from the registry, opsdrive.get("town_crossing_state"))
Writes the state of the railroad-crossing equipment at time t into the world (all crossings use the same train timetable).
> The detailed description below is the original text — the summary and the headings are translated.
train = town_run の run["train"](None = 待機: かん上・灯消灯・列車は遠く)。状態は既存 op drivecrossing.crossing_gate_state(警報 → 降下 → 遮断 → 上昇、かんの角)と drivecrossing.crossing_lamp_signal (2 灯の交互点滅、exposure > 0 でカメラの露光平均)で評価する。列車の先頭は t_arrival に道路の縁(手前 margin)に着き、v_train で +y(局所)へ進む。返り値 {"state", "state_name", "boom_angle", "lamps", "entry_forbidden", "train_y"}。
Raises ValueError: world が town_world の物でない、t が非有限、train の鍵が足りない。
• 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.
• poc_driving_town — py -3.11 examples/poc_driving_town.py
table as input)course_layout · course_occupancy · course_contains · world_build · world_camera · world_move · lidar_scan · rss_longitudinal_same
town)town_chain · town_layout · town_world · town_centerline · town_stop_lines · town_rules · town_run · town_checks
*Provenance: drivetown.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.