crossing op• Data kinds: any → table
• Call: import fullseye as fs; fs.ledger.conflict_zone_intervals(dist_to_zone, zone_length: 'float', car_length: 'float', *, v0: 'float', accel: 'float' = 0.0, v_max: 'Optional[float]' = None) -> 'Dict[str, object]' (to call the implementation directly, import drivecrossing; drivecrossing.conflict_zone_intervals(dist_to_zone, zone_length: 'float', car_length: 'float', *, v0: 'float', accel: 'float' = 0.0, v_max: 'Optional[float]' = None) -> 'Dict[str, object]'; from the registry, opsdrive.get("conflict_zone_intervals"))
Times [t_in, t_out] during which a vehicle occupies the conflict zone (where 2 paths overlap inside the intersection) (closed form, arrays allowed).
The vehicle enters when its front end has advanced dist_to_zone, and its rear end exits when the front end has advanced dist_to_zone + zone_length + car_length. From initial speed v0 it accelerates at accel up to v_max (constant speed if accel = 0). If it is already inside the zone (dist_to_zone < 0), t_in = 0.
• 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_crossing — py -3.11 examples/poc_driving_crossing.py
table as input)course_layout · course_occupancy · course_contains · world_build · world_camera · world_move · lidar_scan · rss_longitudinal_same
crossing)crossing_timing_check · crossing_gate_state · crossing_lamp_signal · lamp_pair_phase · crossing_clear_time · exit_room_check · crossing_stop_check · track_sight_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.