Online Monitoring Framework for Pressure Transient Detection in Water Distribution Networks
Bibliographic record
Abstract
Access to potable drinking water is a necessity and basic human right. Most North Americans obtain treated water through water distribution networks, an essential part of municipal infrastructure that is subject to decay and degradation. Amongst the factors influencing pipe failure are events that trigger abrupt pressure changes, or transients, which can cause pipe breakages in the short term, and general fatigue in the long term. The ability to quantify these transients as they occur is important for effective asset management, and for preventing and mitigating the occurrence of failure. Current practices take a largely reactive approach to event detection, and few systems capable of real-time transient detection have ever been implemented. \n \nThis research addresses the need for an online monitoring framework aimed towards understanding pressure transient effects and behaviour. The proposed system uses an Internet of Things approach, combining pressure sensors with Raspberry Pi computers, as well as open-source tools that transmit and display the data. The data analysis combines computationally inexpensive methods in order to achieve an accurate decision-making tool for both transient detection and abnormal transient risk identification. The techniques used include different filtering and detrending methods, feature extraction for dimensionality reduction, three-sigma statistical process control, and classification using voting methods. The process also includes a second process, based on statistical process control and trained using transient data identified in the original process, in order to assign a risk for a transient to cause damage, as well as identify transients that are particularly severe. \n \nData was collected from a unique laboratory water distribution network as well as a field installation in Guelph, Ontario. The results showed that the framework achieves real-time transient identification with reasonable detection and error rates. Further analysis illustrated the effect of factors such as transient source location, active flow in the pipes, and transient type, on transient propagation and detection. The performance of the framework proves the concept of IoT-based systems for pressure monitoring and event detection in municipal water infrastructure.
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 distilled prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.
Codex and Gemma teacher scores by category
| 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.000 | 0.000 |
| Open science | 0.000 | 0.000 |
| Research integrity | 0.001 | 0.000 |
| Insufficient payload (model declined to judge) | 0.000 | 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 teacher head, 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".