Development of Regional Traffic Data for the Mechanistic–Empirical Pavement Design Guide
Bibliographic record
Abstract
To obtain full benefits from the new Guide for Mechanistic–Empirical Design of New and Rehabilitated Pavement Structures (MEPDG), it is necessary to characterize pavement traffic loads using detailed traffic data, including axle load spectra. Preferably, the detailed traffic data should be site specific. In the absence of site-specific traffic data, default input data need to be used. Truck traffic data, collected as part of a periodic commercial traffic survey, were used to obtain the best possible default values for traffic input parameters required for the MEPDG. Default traffic input parameters were developed for two Ontario, Canada, regions. The sensitivity of the predicted pavement performance to changes in traffic input parameters was explored. There are several notable differences between the default traffic data inputs included in the MEPDG software and the regional traffic data inputs developed for Ontario, particularly in terms of axle load spectra. Axle load spectra for Ontario have a smaller number of heavily overloaded axles, and the peaks between loaded and unloaded axles are more pronounced. There are also notable differences between axle load spectra for northern and southern Ontario. Compared with southern Ontario, northern Ontario axle load spectra are heavier and have a large proportion of fully loaded axles. The number and type of trucks, followed by the axle load spectra, have the predominant influence on the predicted pavement performance. The MEPDG contains several input parameters that do not have any significant influence on the predicted pavement performance, namely, hourly traffic volume adjustment factors and axle spacing.
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.006 |
| Meta-epidemiology (narrow) | 0.001 | 0.001 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.003 | 0.002 |
| Science and technology studies | 0.001 | 0.000 |
| Scholarly communication | 0.001 | 0.001 |
| Open science | 0.003 | 0.001 |
| Research integrity | 0.001 | 0.001 |
| Insufficient payload (model declined to judge) | 0.035 | 0.019 |
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".