Potential drought-driven metal(loid) release in Junction Creek: effects of legacy contamination and the impacts of lime treatment
Bibliographic record
Abstract
Acid mine drainage (AMD) is a serious environmental problem at legacy and active mine sites around the world. Climate associated drought and rewetting events can increase the severity of AMD impacts through oxidation and release of stored metal(loid)s and acidity from contaminated sediments. The area surrounding Sudbury, Ontario, with its massive mining and smelting complexes, appears especially vulnerable to such drought-driven effects. I used a paired subwatershed approach to assess the impact of drought-rewetting cycles in two subwatersheds of Junction Creek, a heavily contaminated system flowing through the centre of Sudbury. For this study I chose the Frood tributary which contains a large mine site and waste rock storage area, as well as the less contaminated Maley tributary as a reference site. Laboratory drying and rewetting experiments with sediment-cores collected from the Nickledale wetland in the Frood branch surprisingly showed no post-drought re-acidification. However, highest concentrations of many metal(loid)s were observed in the longest (60-day) drought treatment, suggesting a drought effect may still occur. Pre-drought lime treatments showed reduced concentrations of many metal(loid)s in-solution following re-wetting. However, sediment metal(loid) concentrations suggest that liming applications may cause release of some metal(loid)s through ion exchange processes. Analysis of available long-term monitoring (2004-2020) data showed annual fluxes in metal(loid) concentrations in both subwatersheds, but the expected strong seasonality of the metal export was best observed at the reference Maley site rather than at the industrial Frood site. Additionally, it was observed that surface water As concentrations were in fact highest at the reference site. Overall, this study provides preliminary data demonstrating that the remedial work at the mine impacted site has reduced the vulnerability of this subwatershed to the climate-driven impacts.
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.001 | 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".