Integrity / coverage / limitations

Data quality

The archive is highly complete but not continuous. Coverage, restarts, imported series, and algorithmic limitations are first-class data—not cleanup details.

Daily sample coverage
Minimum of both directions · 95% completeness threshold

Bay Lights optical regime change

The 48,000-LED installation entered a 24/7 burn-in approximately February 19, 2026, according to a February 26 report in the San Francisco Chronicle. The official Grand Lighting followed on March 20, after which the primary installation was scheduled to run nightly from dusk until dawn.

The camera data shows a pronounced nighttime detector discontinuity during commissioning, with a sharp high-noise onset around March 8–12 and persistent elevation after March 20. The timing and night-only signature are consistent with animated LEDs creating false motion tracks. This is strong observational evidence, not a controlled causal experiment.

Nighttime spike excess
22:00–05:00 Pacific · mean of directions · nightly p95 minus median
Do not compare mixed-regime nighttime statistics as though the sensor were stable. Use pre-lights, commissioning, illuminated-era, or all-data controls on the analysis pages. Pre-lights is the preferred baseline for traffic-pattern interpretation; commissioning should generally be treated as a transition period.

Longest interruptions

Counter reset

The reset occurred on August 9, 2025 after an interruption. The detector ignores persisted counter state older than 24 hours, allowing both directional counters to restart. Published lifetime totals must therefore use reset-aware positive deltas, not the final counter value alone.

Known limitations

Preservation status: the active 689.6 MB Prometheus Docker volume has been identified but not yet frozen into an immutable verified copy. No volume, block, or historical artifact should be deleted or recreated before that backup exists.