Pressure instrument slack flow detection – three methods to determine flow status of a paste reticulation system
Bibliographic record
Abstract
One of the most significant operational problems that paste backfill systems face is detection and mitigation against slack flow. Slack flow occurs when there is an excess of gravity head energy within the reticulation system, resulting in high-velocity conditions that increase wear. It is a primary cause of borehole failure. Hydraulic modelling can predict where slack flow might occur and is a principal component in designing a reticulation system to mitigate against slack flow. However, hydraulic modelling relies on accurate rheological measurements to estimate friction losses and requires a distinct predetermined pipeline route. Both these factors become increasingly hard to evaluate during operation; variation in tailings mineralogy or PSD can cause significant shifts in the rheological characteristics of the paste, and as-built reticulation networks frequently differ from the designed routing and/or pipe class. Furthermore, providing real-time feedback to plant operators via hydraulic grade lines is difficult. In a study conducted by Paterson & Cooke for Boliden’s Garpenberg mine located in central Sweden operating a paste backfill system, three distinct methods were developed to detect slack flow in real-time from underground Pressure Instruments (PI). These methods provided immediate feedback to plant operators on whether the system was in slack flow, regardless of filling location and tailings variability. This paper provides details of each of the three methods, including derivation, implementation, and comparison to operational data.
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.004 |
| Meta-epidemiology (narrow) | 0.001 | 0.001 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.003 | 0.001 |
| Science and technology studies | 0.000 | 0.001 |
| Scholarly communication | 0.001 | 0.001 |
| Open science | 0.001 | 0.001 |
| Research integrity | 0.001 | 0.001 |
| Insufficient payload (model declined to judge) | 0.001 | 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".