A Byte of PhysicsLogo

Flow rate and continuity

For incompressible steady flow with no accumulating storage, the same volume per second crosses every pipe section. A narrower section therefore has higher average speed. This is an accounting relation: it does not claim every fluid particle has the same speed across a real pipe profile.

Think like a programmer

Represent volume flow rate as a signed scalar through a named oriented section. Derive each section's average speed from its area rather than manually assigning incompatible speeds. Validate strictly positive area and keep direction in the sign; if a model permits density change or storage, use a balance that names those additional state terms.

Model checklist

Inputs
Cross-sectional areas, signed volume flow rate Q, density assumption, section orientations, time window, and storage/source policy.
State
Derived section-average speeds, flow-rate ledger, and optional density/storage values.
Rule
For steady incompressible one-streamtube flow, divide common Q by each positive area.
Output
Compatible speeds, flow residual, and stated validity conditions.
Check
Aᵢvᵢ equals common Q at every section; halving area doubles speed at fixed Q; reversing orientation reverses reported signs; positive finite area is required.
\[Q=Av\qquad A_1v_1=A_2v_2\]

The equation follows from mass conservation after density is treated as constant and no fluid accumulates between sections. Q has units m³/s, area m², and average speed m/s. If A₂ = A₁/2, then v₂ = 2v₁ at the same Q. A pure helper that takes area and Q makes this relationship executable and prevents a network editor from accepting arbitrary incompatible velocities.

For a control volume, the fuller question is how much mass enters, leaves, is stored, or is created by an explicitly modeled source. A steady incompressible pipe reduces that ledger to matching volume rate. A leaking pipe, filling tank, compressible nozzle, or branching junction therefore needs more data than one area ratio.

Try this experiment

Prediction: Halving a section's area doubles average speed at fixed signed flow rate, while every section retains the same A×v invariant.

Choose Q = 0.06 m³/s, A₁ = 0.03 m², and A₂ = 0.015 m². Predict both speeds before calculation. Then write a test that reconstructs Q from each section, and state which additional ledger term invalidates this simple equality for a filling tank.

Where this model breaks

Compressible flow changes density, and unsteady storage can make inflow and outflow differ temporarily. Real pipes have boundary layers, nonuniform velocity profiles, leakage, turbulence, losses, valves, and branching topology. Near sonic flow or shocks, an incompressible area-speed shortcut is not physically adequate.

Summary

Carry one signed conserved flow rate through a simple steady incompressible pipe model and derive each section's average speed from area. Record orientation and the assumptions that remove storage, density, leak, and profile terms.

Glossary

Self-check

  1. What is conserved through a steady incompressible pipe?
  2. How does narrower area change average speed?
  3. What determines the sign of Q?
  4. When does this simple relation fail?

Sources

Model contract

Treat the lesson as a small function before treating it as a fact to memorize. Give every value a unit, keep only the state needed for the next step, and make the output easy to inspect.

\[\text{observable output} = f(\text{inputs},\,\text{state})\]
Inputs
Quantities you set or measure, with units and useful bounds.
State
Values the program must retain to reproduce the next result.
Rule
The relationship or update that turns inputs and state into a result.
Check
A known limit, unit check, invariant, or measured result that can expose a bad model.

Implement the idea as a model

For Flow Rate and Continuity, write down the quantities you can control, the values your program must retain, and the result a reader could inspect. In Fluids, the useful program is not the drawing: it is the smallest explicit model that makes a prediction you can test.

Guided experiment

Prediction: changing one declared input while holding the others fixed should change only the outputs that the model connects to that input. Choose one input, predict the direction of change, then check a limiting case such as zero, a symmetric arrangement, or a familiar low-speed or small-change approximation.

Where this model breaks

This lesson is a teaching model, not a complete simulator. Before using it outside the stated question, check which interactions, scales, uncertainties, boundary conditions, and measurement limits it leaves out.

Summary

Treat Flow Rate and Continuity as a contract: named inputs and units enter a rule, the rule produces an observable result, and a known limit or invariant checks whether the implementation deserves trust.

Glossary

  • Input: a measured value or chosen parameter supplied to a model.
  • State: the smallest set of values needed to continue or reproduce a model.
  • Validation: comparing an output with a known result, limit, invariant, or measurement.

Self-check

  1. Which values are inputs, and which values must remain state?
  2. What observable result would tell you the model is behaving as expected?
  3. Which assumption would you test first before applying the model to a real system?

Model review: turn Flow Rate and Continuity into a test

Use conserved volumetric flow rate to derive compatible fluid speed across pipe sections.

  1. Name the inputs and units that the fluids model needs.
  2. Separate the state you must keep from values you can calculate when needed.
  3. Write one rule that maps the current state and inputs to an observable result.
  4. Choose a limiting case, unit check, invariant, or known result before trusting an output.
  5. State one assumption you would change before using this simplified model for a real decision.
Share to: