Verification and Validation of Next-Generation Traffic Cameras
Bibliographic record
Abstract
Modern traffic cameras are taking advantage of recent advances in deep learning and related technologies to detect, classify and count both vehicles and other road users. In recent years, the number of products with such advanced features has increased dramatically. For road authorities, this has made development of effective and efficient techniques for verifying and validating the performance of alternative products ever more important. Many organizations have adopted, with slight variations, the steps described in Section 660 of the Florida Department of Transportation’s Standard Specifications for Road and Bridge Construction for comparing manual and machine counts. However, there are many aspects of Section 660 that could be improved, including: 1) extending its protocols to include both vehicles and other road users, 2) incorporating provisions for improving the accuracy of manual counting while reducing analyst fatigue, and 3) reassessing the amount of data that needs to be processed in order to achieve the required level of confidence. Amongst those road authorities that have used Specification 660 as the foundation for their own efforts, the lack of consensus concerning the best metric for expressing the accuracy of machine counts is problematic. Here, we suggest how these limitations might be overcome and recommend that Canadian road authorities join forces to develop a consensus-based standard that addresses these concerns.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.024 | 0.051 |
| Meta-epidemiology (narrow) | 0.001 | 0.001 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.003 | 0.001 |
| Science and technology studies | 0.001 | 0.002 |
| Scholarly communication | 0.004 | 0.005 |
| Open science | 0.005 | 0.003 |
| Research integrity | 0.003 | 0.003 |
| Insufficient payload (model declined to judge) | 0.005 | 0.004 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".