Bibliographic record
Abstract
407ETR is a multi-lane, electronic toll highway that currently runs 69 km across the top of the Greater Toronto Area. 407ETR is four lanes, except between Highway 10 and McCowan Road, which is six lanes. To accommodate future traffic needs, 407ETR has the capability of expanding to 10 lanes. 407ETR was built in stages, in just four-and-a-half years. The first phase of 407ETR was opened in the summer of 1997, with extensions opened in 1997, 1998 and 1999. Traffic volume has risen steadily since tolling began and continues to grow with over 240,000 average weekday trips each month! A comprehensive pavement evaluation program was performed on 407ETR to determine the pavement conditions and to identify areas with high possibility of premature deterioration. Advanced, non-destructive testing (NDT) techniques were implemented in this program to detect performance problems at early stages before they manifest on the pavement surface in the form of distresses. The pavement evaluation program consisted of a visual distress survey, a profile based rideability (roughness) survey, a skid resistance survey and a limited deflection survey using the Falling Weight Deflectometer (FWD). Several analyses were performed on the collected data. These analyses included the calculation of the MTO Distress Manifestation Index (DMI), the International Roughness Index, (IRI), the MTO Riding Comfort Index (RCI) and the Surface Friction Number (FN), estimating joint faulting, determining the in-situ pavement structural capacity and foundation condition, evaluating the load transfer efficiency across transverse joints and detecting the existence of voids underneath the PCC slabs. Results of the comprehensive pavement evaluation program performed on 407ETR indicated that the overall condition of the pavement is good. However, based on the deflection analysis and the faulting analysis some preventative maintenance is required. This paper describes the testing and analysis performed on 407ETR, as well as the analysis performed to identify the need for preventative maintenance. For the covering abstract of this conference see ITRD number E201066. (A)
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.002 | 0.003 |
| Meta-epidemiology (narrow) | 0.001 | 0.000 |
| Meta-epidemiology (broad) | 0.001 | 0.000 |
| Bibliometrics | 0.002 | 0.002 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.001 | 0.001 |
| Open science | 0.001 | 0.001 |
| Research integrity | 0.001 | 0.000 |
| Insufficient payload (model declined to judge) | 0.005 | 0.001 |
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".