MétaCan
Menu
Back to cohort
Record W2319038170 · doi:10.1061/40972(311)114

Modeling the Creep Compliance of Asphalt Concrete Using the Artificial Neural Network Technique

2008· article· en· W2319038170 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.

affAt least one author lists a Canadian institution in the pinned OpenAlex snapshot.
aboutThe title or abstract carries a Canadian signal from the geographic lexicon.

Bibliographic record

VenueGeoCongress 2008 · 2008
Typearticle
Languageen
FieldEngineering
TopicAsphalt Pavement Performance Evaluation
Canadian institutionsNational Research Council Canada
Fundersnot available
KeywordsCreepAsphaltArtificial neural networkCrackingRutAsphalt concreteFatigue crackingCivil engineeringComputer scienceStructural engineeringEngineeringMaterials scienceMachine learningComposite material

Abstract

fetched live from OpenAlex

The new mechanistic-empirical pavement design guide developed under the NCHRP project 1-37A adopted the creep compliance parameter to characterize the low-temperature behavior of bituminous materials. It is used to predict thermal cracking of roads. However, determination of the creep compliance at three temperatures (–20, –10 and 0°C) involves elaborate laboratory testing and special training of technical staff, a capability that the majority of road jurisdictions in Canada lack today. This paper presents a scheme to estimate the needed parameter by taking advantage of the wealth of field information available from long term pavement performance (LTPP) sites. The proposed technique is based on the use of artificial neural network technique to have a good estimation of the creep compliance of asphalt concrete mixes. Several ANN models were trained and tested using simple parameters collected over the years from LTPP sites. Results of ANN simulations showed the good potential that proposed model has to predict the creep compliance (at different low temperatures) of mixes prepared with different binders. Such a model represents an attractive alternative to testing for small jurisdictions with limited budget and personnel.

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.000
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Simulation or modeling · Consensus signal: Simulation or modeling
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.124
Threshold uncertainty score0.510

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0000.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.000
Science and technology studies0.0000.000
Scholarly communication0.0000.000
Open science0.0000.000
Research integrity0.0000.000
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.091
GPT teacher head0.290
Teacher spread0.199 · 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