Skip to main content

Sluicegate Tutorial with FlowStudio

This walkthrough shows how to use FlowStudio’s sluice gate (rectangular channel) worksheet: upstream pool depth from specific energy, downstream gradually varied flow, and—when the case allows—hydraulic jump placement plus an empirical jump length (SI units).

Open FlowStudio → https://flow.syncster.dev

What you are solving

A bottom sluice in a wide rectangular channel passes a discharge Q. The worksheet assumes a contracted depth at the vena contracta, y2 = Cca, where a is gate opening and Cc is a contraction coefficient (often near 0.6–0.65). From specific energy matching between the upstream pool and the contracta—together with a check against uniform normal depth yn for the approach channel—the sheet finds upstream pool depth y1.

Downstream, it integrates Manning-based gradually varied flow from the gate. If the contracta is supercritical and you set a subcritical tailwater yt (or leave tailwater blank so the sheet can default to yn when that is valid), it locates a Belanger jump where the supercritical profile reaches the depth whose sequent is yt, applies an empirical jump length correlation, then continues subcritical GVF to the end of your reach.

Step 1 — Create the worksheet

Sign in if prompted, then create or open a project. Add a new worksheet and choose Sluice gate (rectangular channel). Open the sheet so you see the intro paragraph, the input grid, and the Compute gate & profile button.


Step 2 — Enter channel, gate, and reach

Enter SI values: bottom width b, Manning n, bed slope S0 (m/m), discharge Q, opening a, contraction Cc, upstream reach length Lu (plotted pool), downstream profile length L, and integration steps (RK4 Δx nominal count). For a reproducible demo you might try, for example: b = 5 m, n = 0.025, S0 = 0.0004, Q = 12 m³/s, a = 0.45 m, Cc = 0.61, Lu = 20 m, L = 200 m, steps = 48—tune to your case.

Leave Tailwater yt blank to let the sheet use normal depth yn as tailwater when that is physically consistent; or type a subcritical tailwater to force a specific jump target.

Step 3 — Compute and read the summary

Click Compute gate & profile. The Summary table lists normal depth yn, critical depth, pool depth y1, contracted depth y2, velocities, Froude numbers, specific energy at the contracta, and—if a jump is applied— jump station xj, pre-jump depth y′, tailwater used, estimated jump length Lj (Chow / Chaudhry correlation), Froude before the jump, and where subcritical GVF resumes (xs). A short note under the title explains the run (afflux, drowned jump, or extend-L messages).


Step 4 — Long-section profile and section view

The long section plots depth vs distance: negative x is the upstream pool at y1, the gate at x = 0, then downstream GVF. If a jump is modeled, you should see supercritical depth approaching xj, a short horizontal segment at tailwater depth over the estimated jump length, then subcritical profile. The cross section at the pool shows width b and depth y1.


Jump length, references, and common pitfalls

  • Jump length Lj uses the empirical form Lj = 220 y′ tanh[(Fr′ − 1)/22] for a horizontal rectangular channel, as summarized in standard references (e.g. Chow; Chaudhry) and engineering summaries such as LMNO — Hydraulic jump. It is not a CFD result; treat it as order-of-magnitude for visualization and teaching.
  • If tailwater is too high relative to the sequent depth at the gate, the sheet warns of a drowned / submerged jump and keeps a supercritical reach only—adjust yt, slope, n, or Q to match your scenario.
  • If Fr2 < 1 at the contracta, no jump splice is applied; check opening, Q, and b.
  • If the note says the jump is not in reach, increase downstream L or change tailwater / slope so the M3 profile can reach the required pre-jump depth.
  • Very small y1/a
may trigger a warning that outflow may not behave as a free sluice—results are indicative.

Wrap-up

You’ve walked through the sluice gate worksheet: energy-based pool depth, downstream GVF, optional Belanger jump with empirical length, and where to read Lj and xs in the Summary and notes. Cross-check against hydraulic texts, physical models, or project standards for design decisions.

Run the sheet live at https://flow.syncster.dev.

Comments

Popular posts from this blog

Cursor AI Review: Is the AI Code Editor Worth It?

I've been using Cursor as my main code editor for a while now, and enough people have asked whether it's worth switching to that a proper review felt overdue. Short version: for me, yes — but with caveats. What is Cursor? Cursor is an AI-first code editor built as a fork of VS Code. That means every extension, theme, and keybinding you already use in VS Code works here, but with AI woven directly into the editing experience instead of bolted on as a plugin. It's made by Anysphere and can run models from OpenAI and Anthropic under the hood. What I like Tab completion is uncanny. Cursor predicts your next edit — not just the rest of the line, but the next change across the file. Once you get used to hitting Tab, going back to a plain editor feels slow. The Composer / Agent mode. You describe a change in plain language and it edits multiple files at once, showing you a diff to accept or reject. For refactors and boilerplate, this saves real time. It unde...

MacBook Pro M5 vs M5 Pro: Which One Should You Actually Buy?

Apple's latest 14-inch MacBook Pro comes in two very different flavors: the base M5 and the step-up M5 Pro . On paper they look similar — same gorgeous Liquid Retina XDR display, same design — but under the hood the gap is bigger than the names suggest. Here's a clear, no-hype breakdown, with concrete use cases so you can match the chip to your work. Quick spec comparison Spec M5 M5 Pro CPU 10-core (4 performance + 6 efficiency) Up to 18-core (6 performance + 12 efficiency) GPU 10-core Up to 20-core Neural Engine 16-core 16-core Memory bandwidth 153 GB/s 307 GB/s (roughly double) Unified memory 16 / 24 / 32 GB 24 / 48 / 64 GB Max storage Up to 4 TB SSD Up to 8 TB SSD Battery (video playback) Up to 24 hours Up to 22 hours Media engines Single encode/ProRes engine More encode/ProRes engines (higher configs) What actually changes between them More cores — the M5 Pro nearly doubles CPU cores and adds GPU cores, so sustained, multi-threaded work finishe...

How I used Google Sheets and Apps Script

Google Sheet is one of the most powerful spreadsheet application that exists online, rivaling with Microsoft's Excel. One of the main strengths is its strong support for collaboration with other users, much easier and popular than collaboration tools with Microsoft Office. Aside from plain spreadsheet, it also supports extensions such as macro. If you are familiar with macros on other office tools, they work almost the same. However, the most extension I use and tinker with is the Apps Scipt . Apps Script Extension One of the challenges I faced recently is how do I track or monitor reports in our department if they are submitted on time or worst, forgotten due to lack of better monitoring tools. So I thought if there can be simple applications that can be deployed or use by a more general user to allow reminding periodically what reports are approaching due dates or those that are past dues. Then I looked for a way, instead of creating a full blown app from scratc...