MétaCan
Menu
Back to cohort
Record W3107881557 · doi:10.17226/23055

Protocols for Collecting and Using Traffic Data in Bridge Design

2009· book· en· W3107881557 on OpenAlex

Why this work is in the frame

A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.

aboutThe title or abstract carries a Canadian signal from the geographic lexicon.
no affNo Canadian affiliation: this work is invisible to an affiliation-only frame.
No Canadian affiliation. An affiliation-only frame, the usual design, would never have seen this work. It is one of the works that make the case for inverting the frame.

Bibliographic record

VenueTransportation Research Board eBooks · 2009
Typebook
Languageen
FieldEngineering
TopicTransport Systems and Technology
Canadian institutionsnot available
Fundersnot available
KeywordsBridge (graph theory)Computer scienceTransport engineeringEngineeringMedicine

Abstract

fetched live from OpenAlex

This report documents and presents the results of a study to develop a set of protocols and methodologies for using available recent truck traffic data to develop and calibrate live load models for Load and Resistance Factor Design (LRFD) bridge design. The HL-93, a combination of the HS20 truck and lane loads, was developed using 1975 truck data from the Ontario Ministry of Transportation to project a 75-year live-load occurrence. Because truck traffic volume and weight have increased and truck configurations have become more complex, the 1975 Ontario data do not represent present U.S traffic loadings. The goal of this project, therefore, was to develop a set of protocols and methodologies for using available recent truck traffic data collected at different US sites and recommend a step-by-step procedure that can be followed to obtain live load models for LRFD bridge design. The protocols are geared to address the collection, processing and use of national weigh-in-motion (WIM) data to develop and calibrate vehicular loads for LRFD superstructure design, fatigue design, deck design and design for overload permits. These protocols are appropriate for national use or data specific to a state or local jurisdiction where the truck weight regulations and/or traffic conditions may be significantly different from national standards. The study also gives practical examples of implementing these protocols with recent national WIM data drawn from states/sites around the country with different traffic exposures, load spectra, and truck configurations.

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.

Full frame distilled prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.

metaresearch head score (Codex)0.001
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesMeta-epidemiology (narrow)
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Not applicable · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: none
Teacher disagreement score0.586
Threshold uncertainty score1.000

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0010.000
Bibliometrics0.0010.000
Science and technology studies0.0000.000
Scholarly communication0.0000.000
Open science0.0000.000
Research integrity0.0010.001
Insufficient payload (model declined to judge)0.0000.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.

Opus teacher head0.264
GPT teacher head0.395
Teacher spread0.131 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it