Bibliographic record
Abstract
This paper presents the background and lessons learned from a 23-year old shotcrete repair of two corrosion-damaged concrete bridges. The two CPR Railroad Overpasses (northbound and southbound structures) at Cayley were exposed to highway de-icing salts and had developed severe curb corrosion and spalling in 1981 at age 21 years. The curbs were extensively repaired in the summer of 1982 with site-batched latex-modified dry-mix shotcrete. The work consisted of chipping to remove 220.6 lineal metres (91.3% of total length) of corrosion damaged curb face to an average depth of 150 mm. The scope of work left behind a significant amount of adjacent chloride contaminated non-repaired curb concrete. The repairs are in good condition and remain in service in 2005. No spalling of the non-repaired curb concrete, as might be expected due to the ring anode effect after leaving adjacent concrete un-repaired, has occurred. The repairs have been monitored for corrosion with inspection and copper sulfate electrode (CSE, ASTM C-876) testing on a five year cycle since 1983. The CSE results show that the post-repair readings on both structures declined progressively following repair in 1982 until approximately 1995, when they reached their minimum values and began to increase. The most recent tests in 2004 showed a northbound bridge curb average of –297 mV, which is 78 mV lower than when repaired in 1982. The average 2004 reading on the southbound bridge curbs was –290 mV, still 65 mV lower than in 1982. The repaired curbs are in sound structural condition with no visible damage or debonding, few cracks and little staining after 23 years of service. The test data suggests that the repairs will provide significant additional service life, and a total service life of 35 years is expected. The repair details included the use of galvanized welded wire mesh, manual chipping for concrete removal, followed by sandblasting, shotcreting into forms along the longitudinal edges for trueness. The repair perimeter was not saw cut. The paper presents current condition data and discusses how various repair features contributed to it.
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.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.005 | 0.015 |
| Meta-epidemiology (narrow) | 0.001 | 0.001 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.001 | 0.001 |
| Science and technology studies | 0.003 | 0.003 |
| Scholarly communication | 0.004 | 0.004 |
| Open science | 0.004 | 0.004 |
| Research integrity | 0.005 | 0.005 |
| Insufficient payload (model declined to judge) | 0.006 | 0.004 |
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.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".