Volume stability of hydrated Portland cement phases exposed to aggressive solutions
Bibliographic record
Abstract
The durability of concrete and its constituent phases continue to receive significant international attention. Concrete exposed to aggressive environments such as aqueous chloride or sulfate solutions often sustains damage as a result of excessive volume change. Phenomena associated with the deterioration process generally described by the term sulfate attack have received much recent attention in North America due to litigation. Skalny and Pierce reviewed and discussed the sulfate attack issue with respect to the physico-chemical phenomena involved in both laboratory and field observation. Sulfate attack issues discussed included the correctness of disassociating the purely physical (e,g. alkali-sulfate salt crystallizing in pores) and chemical processes involving decomposition of the cement paste by the penetrating sulfate solution. These processes (physico~chemical in nature) are often ascribed to phenomena that include crystal growth and pressure generation and colloidal swelling. Reaction products such as ettringite and gypsum have been considered to be central to the mechanisms involved. Large volume changes can also result from hydration of anhydrous alkali salts as the specific volume of the hydrated salt is significantly greater. These are considered by many to be non-classical.
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.000 | 0.000 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.000 | 0.000 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.000 | 0.000 |
| Open science | 0.000 | 0.000 |
| Research integrity | 0.000 | 0.000 |
| Insufficient payload (model declined to judge) | 0.001 | 0.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.
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".