-
Re-timing a leak localiser to the alarm: 17 rules, one leak gained, and the oracle day stays out of reach
On BattLeDIM's L-Town, a lag or vote around the detector's alarm picked on 2018 places 4 of 22 detected 2019 leaks within 300 m, against 12 at the oracle day.
-
Take away the oracle hour: a leak localiser keeps about half its hits when a real detector sets the day
On BattLeDIM's L-Town, localising at a real detector's alarm day instead of the oracle hour drops 300 m hits from 15 to 8 of 30 detected injected leaks.
-
Held out: the shape-chosen leak rule finds 25 of 64 unseen L-Town leaks, against 16 for the newest source
On 64 new leaks simulated through BattLeDIM's own model, the steepest-ramp rule places 25 within 300 m against 16 for the newest source (P = 0.022).
-
Slow leaks look like ramps, but timing the ramp against the alarm loses them again
On BattLeDIM's L-Town, a step-or-ramp fit labels every slow leak's source a ramp, yet timing it against the alarm finds 3 of 17 slow leaks, not 6.
-
Let the leak's shape choose: the steepest ramp, else the newest source, finds 15 of 32 L-Town leaks
On BattLeDIM's L-Town, picking the steepest ramp-shaped source, else the newest, places 15 of 32 leaks within 300 m, with 6 slow leaks and 9 bursts.
-
Dating each fitted leak source by its first day did not find the slow leaks
On BattLeDIM's L-Town, a daily tracker that dates fitted leak sources localises 8 of 32 leaks, below a one-week rise rule on the same data (14).
-
Pick the fastest-rising leak source, not the newest: slow leaks found double, two bursts lost
On BattLeDIM's L-Town, choosing the leak source whose flow rises fastest finds 6 of 17 slow leaks instead of 3, but misses two bursts: 14 of 32 in all.
-
Modelling every leak at once finds the slow leaks, then the localiser picks the wrong one
On BattLeDIM's L-Town, a joint fit of all leaks puts an atom near 10 of 17 slow leaks, yet a one-week rise rule localises only 1 of them.
-
The leak tracker was drowning in drift: with demand removed it finds 13 of 32 leaks
On BattLeDIM's L-Town, a daily leak-source tracker keeps 8 sources instead of 20 once demand is removed, finds 13 of 32 leaks and dates 9 of 17 slow ones.
-
Two textbook fixes to leak localisation made it worse
On BattLeDIM L-Town, hourly leak signatures and a flow-balance leak size put 12 of 32 leaks within 300 m, against 15 for a plain 24 h mean.
-
The best published L-Town leak detector, scored against random alarms
SICAMS's published 2019 times find 13 of 19 BattLeDIM leaks; 27 random alarms find 10 (P = 0.057). Run automatically, it gives 26 false alarms.
-
The leak benchmark with the leaks taken out
L-Town simulated with no leaks: two pressure detectors raise 1 alarm in 716 days; a night-flow detector raises 31, credited with 14 of 19 leaks.
-
Count a leak alarm only once the leak is real, and the BattLeDIM ranking flips
Credit a leak alarm only once the leak carries 1 m³/h and pressure CUSUM drops to chance (P = 0.32) while smart-meter night flow beats it (P = 0.001).
-
Minimum night flow misses the small leaks on BattLeDIM
On BattLeDIM, minimum night flow finds 3 of 9 small leaks where pressure CUSUM finds 7. Its night-to-night swing, about 11 m³/h, is as big as the leaks.
-
Nineteen leaks cannot rank six leak detectors
On BattLeDIM, 3 of 6 leak detectors switch between beating chance and not as the match window changes, and no pair differs under a paired test.
-
Swap the tuning year and the leak-detector ranking goes
Tuned on 2019 and tested on 2018, BattLeDIM leak detectors lose their ranking: on 32 held-out leaks none beats chance after correction under a flow gate.
-
Finding the leak: a hydraulic model does no better than the sensor that dropped most
On BattLeDIM L-Town, nominal-model leak localisation puts 31-47% of leaks within 300 m: ten times chance, but no better than the most-affected sensor.
-
Cleaner night flow still misses the small leaks, and pressure's hits on them were luck
A weekday baseline plus 82 smart meters halves BattLeDIM night-flow noise to 5 m³/h, yet it finds 3 of 9 small leaks. Five barely leak for a month.
-
A water-leak detector against random alarms on the BattLeDIM benchmark
On the BattLeDIM L-Town benchmark a pressure-residual detector finds 13 of 19 new leaks. Random alarms find 11. Where it does beat chance is location.
-
Rebuilding a published leak detector so it runs blind
Rebuilt to run blind on BattLeDIM, the LILA leak detector finds 14 of 19 new leaks to chance's 11. One tie-break rule decides if that gap is real.