MétaCan
Menu
Back to cohort
Record W2014254613 · doi:10.1680/macr.2007.59.7.495

The influence of binder type, cracking and cover on corrosion rates of steel in chloride-contaminated concrete

2007· article· en· W2014254613 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

VenueMagazine of Concrete Research · 2007
Typearticle
Languageen
FieldEngineering
TopicConcrete Corrosion and Durability
Canadian institutionsUniversity of Fredericton
Fundersnot available
KeywordsCorrosionMaterials scienceSilica fumeGround granulated blast-furnace slagCementitiousCrackingPortland cementMetallurgyConcrete coverCementChlorideSlag (welding)Service lifeComposite material

Abstract

fetched live from OpenAlex

Cracking of reinforced concrete can result in substantial reduction in service life owing to rapid initiation of steel corrosion. Supplementary cementitious materials (SCMs) can alter not only the pore solution chemistry but also the environment surrounding the steel and lead to significant reductions in corrosion rate. The impact of binder type on corrosion rate was assessed using seven concrete mixtures comprising ordinary Portland cement (PC) and blends of PC with ground granulated blast-furnace slag, fly ash, condensed silica fume and a ternary blend. Corrosion rates were measured in prismatic specimens with crack widths of 0·2 mm or 0·7 mm. For 20 mm cover, all the SCMs resulted in at least a 50% reduction in corrosion rate compared with the PC control. Increase in crack width from 0·2 mm to 0·7 mm increased corrosion rate in all cases, but had far less impact than that of the SCMs. Increase in cover depth from 20 mm to 40 mm had substantial benefits for PC specimens, reducing corrosion rates by more than half; the same benefits were not observed in specimens using SCMs. This was ascribed to corrosion rates of SCM concretes being controlled primarily by resistivity of the system, while rates in PC specimens were controlled mainly by oxygen availability and thus cover depth.

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

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0040.001
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.001
Science and technology studies0.0000.001
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.032
GPT teacher head0.325
Teacher spread0.293 · 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