MétaCan
Menu
Back to cohort
Record W2089356890 · doi:10.1139/cjce-2013-0578

Evaluation of a modification of current microsurfacing mix design procedures

2015· article· en· W2089356890 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.
venuePublished in a venue whose home country is Canada.

Bibliographic record

VenueCanadian Journal of Civil Engineering · 2015
Typearticle
Languageen
FieldEngineering
TopicTunneling and Rock Mechanics
Canadian institutionsÉcole de Technologie Supérieure
Fundersnot available
KeywordsGradationAsphaltAggregate (composite)EngineeringFactorial experimentDesign of experimentsPortland cementCivil engineeringProcess engineeringCementComputer scienceStatisticsMathematicsMaterials science

Abstract

fetched live from OpenAlex

Although microsurfacing is widely used, current tests and mix design methods mostly rely on laboratory conditions and the correlation between laboratory results and field performance is poor. Therefore, there is a need to develop new mix design procedures, specifications, and guidelines for microsurfacing mixtures. The research described in this paper intended to suggest modifications to the actual International Slurry Seal Association (ISSA) mix design procedure for microsurfacing. The first part of study reports the findings of a detailed laboratory investigation concerning the effect of asphalt emulsion, added water content, and Portland cement on the design parameters and properties of microsurfacing mixtures. A multilevel factorial design is used to assess the effect of different mixture proportions on the test responses. For this, one aggregate type, one asphalt emulsion type or grade, and one aggregate gradation were used in the study. This part of study consisted mainly of establishing a method for preparing and testing microsurfacing mixture using four main mixture design tests proposed by the ISSA (TB 139, TB 113, TB 100, and TB 109). The results obtained with ISSA TB 109 and ISSA TB 100 mixture design tests were found highly variable and not precise enough to suggest optimum mix design. For the second part of this study, different tests were also studied to refine the current mix design procedure. The results have shown that ISSA TB 139 can be used to define the optimum water content at which samples should be tested, and that ISSA TB 147 mix design test should be used to define the optimum asphalt emulsion content.

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.001
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: none
Teacher disagreement score0.606
Threshold uncertainty score0.402

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.001
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.069
GPT teacher head0.254
Teacher spread0.186 · 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