FA-68267 / Traffic signal timing plans / Member archive

Split failure detection: split failure requires strictly more than 80 percent · case 02

Split failure detection returns a wrong result when split failure requires strictly more than 80 percent.

Member previewVariant 2 · 3 implementations · 8 checks per implementation

Case contract

Input {cycles: [{green: [start, end), red_start, occ: [[on, off]]}]} with at least one cycle. Green occupancy ratio GOR = occupied seconds in green / green length; red occupancy ratio ROR5 = occupied seconds in the first 5 s after red start / 5. A cycle is a split failure when GOR >= 0.8 and ROR5 >= 0.8. Return {fails: indices, pct: floor(100*fails/cycles)}.

Why this case matters

Signal timing arithmetic is exact and integer or rational; a wrong rule silently produces unsafe or inefficient timing plans.

One recorded failure

Sample boundary fixture

This sample comes from the broken implementation of a controlled reproducer.

Boundary fixture	Actual	Expected	Outcome
timing oracle 0	`{"fails": [], "pct": 0}`	`{"fails": [2], "pct": 25}`	Failed

MEMBER ARCHIVE

The complete case is available to members.

This record includes three runnable implementations, regression fixtures, execution results, and source hashes.

Member access is invitation-based. Sign in with your invited account to inspect the sources.