← Thinking playground

Issue trees · Two network repairs

Leak Tracker

Follow the branches to find the missing water. Spend your limited meters and repair budget where they address the real shortfall.

The pump sends 100 units each round, but the four terminals receive only 76. The courtyard flashes the loudest alert: 60% of its normal supply is missing. You have 2 repair points; restore delivery to 94.

Delivered: 76 / 94 unitsNetwork loss: 24 units
Main pump: 100 units / round Every branch is shown; none are hidden

Lines show the flow: pump → main → terminal. Repairing a main fixes only that pipe, not downstream leaks.

Select a pipe, then measure or repair it. Selecting a pipe costs nothing.

Your issue breakdown

This is your investigation plan, not the pipe network. Do not count a leak under both its parent and child. Unknown readings remain “?”.

All east losses?
All west losses?
Add an investigation branch

The breakdown covers the network without overlap. Connect meters, then use each branch's contribution to decide where to investigate further.

Go to measuring and repairs ↓
Current delivery: 76 / 94 unitsMeters: 4 / 4Repair budget: 2 / 2 points

Select a pipe, then measure or repair it. Selecting a pipe costs nothing.

East main

Find the area's total shortfall, then separate main-pipe loss from downstream loss.

No meter is connected here. Measure before deciding or repair directly; a wrong guess spends your budget.

Meters keep updating after repairs. Pipe prices are known and do not depend on leak size. You can freely compare pipes between actions.

Back to network and delivery ↑