Groundwater sulphate management in the lower Wolfe Creek catchment at Copper Mountain Mine : characterization and short-term mitigation testing
Bibliographic record
Abstract
The Copper Mountain Mine is situated in the Similkameen River valley in southern British Columbia, Canada. Sulphate and other parameter concentrations, resulting from tailings and waste rock sources, have been increasing over time in a drainage to the east of the mine named Wolfe Creek. The creek is predominantly groundwater fed, with the main source of recharge to the aquifer that feeds the creek being reclaim water that drains through the Tailings Management Facility (TMF). Concentrations of sulphate in the creek are nearing compliance station limits and mitigation through groundwater interception is required to reduce loading and ultimately concentrations in Wolfe Creek. A phased mitigation strategy has been developed, with the first phase comprising significant characterization and the installation of trial pumping wells in 2023. The second phase consisted of the testing of various short-term mitigation techniques, including the pumping wells and various configurations of interception ditches and trenches. The testing activities were implemented in 2024. The first two phases have significantly advanced the working hydrogeological conceptual model which is being used to develop medium to long-term interception options that are being tested using a numerical model. The removal of sulphate load through groundwater interception will result in reduced flows to the creek, which in turn will likely affect downstream flows, reducing them to pre-startup conditions during operations rather than in post-closure. A wetland is present downgradient of the TMF which may also become affected through load removal. Therefore, sulphate management needs to be carefully balanced with flow and load interception in the valley to manage the flow needs of the downstream environment. As this project is ongoing, this paper focuses on the mitigation strategy, characterization efforts and results, conceptual model, and considerations for sulphate management.
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.001 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.001 | 0.001 |
| Science and technology studies | 0.001 | 0.001 |
| Scholarly communication | 0.001 | 0.000 |
| Open science | 0.001 | 0.000 |
| Research integrity | 0.001 | 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".