MétaCan
Menu
Back to cohort
Record W4220828649 · doi:10.1063/5.0076320

Beyond the chloride threshold concept for predicting corrosion of steel in concrete

2022· article· en· W4220828649 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.
fundA Canadian funder is recorded on the work.

Bibliographic record

VenueApplied Physics Reviews · 2022
Typearticle
Languageen
FieldEngineering
TopicConcrete Corrosion and Durability
Canadian institutionsUniversity of Waterloo
FundersH2020 European Research CouncilNatural Sciences and Engineering Research Council of CanadaSchweizerischer Nationalfonds zur Förderung der Wissenschaftlichen ForschungNational Science Foundation
KeywordsCorrosionChlorideReinforced concreteMoment (physics)CementMaterials scienceService lifeProcess (computing)Computer scienceMetallurgyComposite materialPhysics

Abstract

fetched live from OpenAlex

All existing models to forecast the corrosion performance of reinforced concrete structures exposed to chloride environments are based on one common theoretical concept, namely, a chloride threshold, as a sharply defined trigger for corrosion, followed by a period of active corrosion. We critically review the resulting treatment of corrosion initiation and propagation as two distinct, successive stages. We conclude that this concept presents a major barrier for developing reliable corrosion forecast models, and that a new approach is needed. In reality, steel corrosion in concrete is a continuous process, that is, rarely separable into uncoupled, sequential phases. We propose that the focus be placed on the quantification of the time- and space-variant corrosion rate from the moment steel is placed in concrete until it reaches the end of the service life. To achieve this, a multi-scale and multi-disciplinary approach is required to combine the scientific and practical contributions from materials science, corrosion science, cement/concrete research, and structural engineering.

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 categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Bench or experimental · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.478
Threshold uncertainty score0.507

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.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.024
GPT teacher head0.246
Teacher spread0.222 · 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