MétaCan
Menu
Back to cohort
Record W4389409160 · doi:10.1002/cepa.2935

Preventing Alkali‐Silica Reaction in Concrete

2023· article· en· W4389409160 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.

Bibliographic record

Venuece/papers · 2023
Typearticle
Languageen
FieldEngineering
TopicConcrete and Cement Materials Research
Canadian institutionsUniversity of FrederictonUniversity of New Brunswick
Fundersnot available
KeywordsAlkali–silica reactionCementitiousPortland cementDurabilityAlkali–aggregate reactionAggregate (composite)Consistency (knowledge bases)Reactivity (psychology)Computer scienceCementConstruction engineeringProcess engineeringEnvironmental scienceMaterials scienceEngineeringArtificial intelligenceNanotechnologyComposite material

Abstract

fetched live from OpenAlex

Abstract Alkali‐silica reaction continues to be a challenging durability issue for portland cement‐based concrete. While myriad of preventive options is known to reduce the risk of ASR, changes in availability and consistency of materials make either prescriptive or performance‐based approaches difficult to develop and then quickly adapt. In general, the research community has supported industry with practical solutions based on empirically derived relationships, mostly from accelerated test methods and to a lesser extent realistic exposure/field structures. It is time to increase the level of science behind our approach. The research team represented in this talk is investigating a new methodology that combines the alkali availability needed to initiate ASR (aggregate specific) with the available alkali from the total cementitious blend. The relationship between reactivity of a supplementary cementitious material and the ASR expansion is also explored. This keynote lecture will: 1) Explore performance‐based testing versus prescriptive approaches and why a hybrid approach should be considered ASR prevention; 2) Evaluate the relationship between accelerated laboratory tests, outdoor exposure blocks and field structures; 3) Examine the use of “non‐traditional” supplementary cementitious materials and/or chemical admixtures to prevent alkali‐silica reaction; 4) Propose future research needs and; 5) Make recommendations for how best to prevent alkali‐silica reactivity following the proposed approach.

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: Bench or experimental · Consensus signal: Bench or experimental
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.513
Threshold uncertainty score0.471

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.017
GPT teacher head0.256
Teacher spread0.239 · 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