Hydraulic conductivity of bentonite permeated with acid mine drainage
Bibliographic record
Abstract
Bentonite, especially sodium bentonite, is used extensively either by itself or as a component of soil mixtures in many geoenvironmental engineering applications, including the construction of waste-containment barriers. An important aspect of the design of such barriers is the compatibility assessment of the soil barrier with the intended waste. A series of laboratory hydraulic conductivity (K) experiments were conducted to assess the compatibility of a sodium bentonite paste with acid mine drainage (AMD). The K of the water-permeated bentonite was observed to be of the order of 2 × 109cm/s. Permeation of the bentonite with AMD increased K slightly by almost one order of magnitude to an average value of 1 × 108cm/s as a result of the contraction of electrical double layers surrounding clay particles. The application of a confining stress (3050 kPa) to the samples minimized the increase in K. Confining stress likely compressed the samples and reduced the size of the voids created by double-layer contraction, resulting in lower K. Effluent chemical profiles obtained during the K tests indicated the appearance of some cations and elements contained in the AMD permeant, at its original concentration (influent concentration) after a few pore volumes of AMD permeation. Iron and aluminum likely precipitated as oxyhydroxide and oxysulphate minerals. The pH of the effluent decreased from 7.6 during water permeation to 3.0 after only three pore volumes of AMD permeation, reflecting the limited capacity of the bentonite to neutralize acidic solutions. Zinc was slightly attenuated by adsorption (3.15 mequiv./100 g of dry bentonite) but was reported in the effluent, after approximately nine pore volumes. The results are relevant to the design and construction of bentonite slurry walls around acid-generating tailings and acid water containment ponds at mine sites.Key words: hydraulic conductivity, swelling, waste containment, confining stress, heavy metals, ionic strength, saturation index.
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.001 | 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".