A compact workflow showing how the Water Hammer, Hydraulic Jump & Stilling Basin, and Anti‑Scour tools fit together in a typical hydropower headworks / barrage design process.
This is a typical sequence for preliminary headworks design. In real projects you will iterate back and forth, but this gives a clean, explainable structure for reports and reviews.
Choose characteristic discharges and operating scenarios:
Use the water hammer quick‑check to see if transient pressures are compatible with penstock / tunnel design and gate / valve ratings.
Open tool: Water Hammer / Surge – Quick CheckSize the stilling basin so that the hydraulic jump remains within the basin and the energy is dissipated safely before the flow attacks the riverbed.
Open tool: Hydraulic Jump & Stilling Basin – Quick DesignCombine regime scour, local scour and protection stability to fix: foundation depth, floor level, and toe protection.
Open tool: Anti‑Scour / Scour Depth – Multi‑FormulaWith scour depths and basin geometry fixed, the next steps usually are:
Future tools can plug in here: seepage path / uplift quick check, floor stability & thickness, etc.
Use this matrix when you’re in the design office and just want to remember “which tool do I open for this?”
Main question:
“What are the extreme transient heads and pressures in my penstock / tunnel
for a given closure / opening event?”
➜ Tool: water_hammer_quick_check.php
Main question:
“What does the hydraulic jump look like and how long does my stilling basin need to be?”
➜ Tool: hydraulic_jump_stilling_basin.php
➜ Theory: Hydraulic Jump & Stilling Basin – Theory
Main question:
“How deep can the river scour, and what embedment / rock protection do I need?”
➜ Tool: anti_scour_multi_formula.php
➜ Theory: Anti‑Scour – Theory & Notes
Main question:
“Given my floor level and cutoff depths, are uplift and piping under control?”
➜ Placeholder for a future tool – will naturally slot after scour & basin sizing.
The formulas in the tools follow standard open‑channel hydraulics and scour practice. For detailed design, always fall back on primary references and local codes:
Your tools are designed to sit “above” these references: fast checks with transparent equations, then you dive into the manuals when you need full detail or code compliance.