Soil Bentonite Slurry Trench Cutoff Walls: History, Design, and Construction Practices
Bibliographic record
Abstract
Slurry trench cutoff walls have been widely used for over 70 years to control groundwater flow, seepage through dams and levees, and contaminant transport. In the US, soil-bentonite (SB) slurry walls are frequently the best and most economical vertical barrier to stop the horizontal flow of groundwater and minimize contaminant transport. This paper reviews the development of SB cutoff walls from both a construction and design standpoint. Lessons learned regarding trench stability, the type of bentonite, the makeup of the backfill, specifications, quality control, interface connections, longevity, hydraulic conductivity, state-of-stress, and compatibility with contaminants are presented. Items of particular importance in specifications including viscosity of the fresh slurry, viscosity of the in-trench slurry, unit weight of the slurry, slump, gradation, and hydraulic conductivity of the backfill are discussed. Guidance for quality control testing in both the lab and field are provided including recommendations regarding stresses for testing. The paper provides summary opinions regarding the limitations of SB slurry walls. Issues that require special consideration are identified and include excessive depth, limited available working platform width, excessive underground or overhead obstructions, artesian ground water conditions, layers of extremely weak soil, and rock or boulders in the soil profile.
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.001 | 0.001 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.001 | 0.002 |
| Science and technology studies | 0.000 | 0.001 |
| Scholarly communication | 0.001 | 0.001 |
| Open science | 0.001 | 0.000 |
| Research integrity | 0.000 | 0.000 |
| Insufficient payload (model declined to judge) | 0.002 | 0.001 |
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".