QuickZone: Case Study Snapshot #4: Justifying the Additional Cost of Night Work in Nova Scotia
Bibliographic record
Abstract
In 2001, the intersection of Reeves Street and Trunk 4 in Port Hawkesbury, Nova Scotia— along a key access route to the Trans Canada Highway—was slated to be upgraded. Both roads are generally two-lane roads with certain sections upgraded to include designated turn lanes. Average annual daily traffic (AADT) through the intersection is roughly 8,000 vehicles per day with approximately 10 percent truck volume. Truck traffic is concentrated during the daytime on weekdays. Most of the traffic volume at this location in Port Hawkesbury is through-traffic continuing on to some of the industrial centers near the town or to points further north. The reconstruction involved a major upgrade of the intersection including additional dedicated turn lanes to accommodate higher traffic volumes and to improve safety. Construction was slated to take place only during daylight hours because of cost and safety concerns. However, it was also evident that any construction during the day would have an impact on motorists. QuickZone Version 1.0 was used to test alternate strategies, including the possibility of a detour route through a residential district. Under the original traffic control plan, the intersection operated 24 hours a day, 7 days a week. Under these conditions, QuickZone predicted up to a 6.5-kilometer (4.1-mile) queue and 70 minutes of delay. Project engineers noted that queues and delays did not form during the overnight hours on any day, especially Friday. They also tested a scenario that eliminated construction during daylight hours on Fridays and Saturdays. Using this information, construction was planned for mornings and evenings during weekdays. This approach cut in half the queuing and the delays associated with the construction. In addition, the number of vehicles on the detour route was reduced to 6,000 vehicles per week, a 40 percent reduction. The QuickZone analysis allowed project engineers to better plan the construction schedule and make the decision to perform some of the most disruptive phases of construction at night.\n
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.001 | 0.002 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.001 | 0.001 |
| Science and technology studies | 0.005 | 0.002 |
| Scholarly communication | 0.002 | 0.001 |
| Open science | 0.002 | 0.002 |
| Research integrity | 0.002 | 0.001 |
| Insufficient payload (model declined to judge) | 0.005 | 0.000 |
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".