| Applies To | |
| Product(s): | SewerCAD, StormCAD, SewerGEMS, CivilStorm |
| Version(s): | 08.11.XX.XX and higher |
| Area: | Calculations |
How is Velocity calculated for a conduit in SewerCAD, StormCAD (GVF-Convex and GVF-Rational solvers) or in SewerGEMS or CivilStorm? (Implicit or Explicit (SWMM) dynamic solvers)
The method used to calculate velocity depends on the product and solver used. StormCAD uses the GVF-Rational solver, SewerCAD uses the GVF-Convex solver, CivilStorm can use either the GVF-Rational, Implicit dynamic or Explicit (SWMM) dynamic solver, and SewerGEMS has all four solvers available.
The solver can be viewed/changed in the calculation options assigned to a given scenario.
See the respective section below for your solver, to understand how velocity is calculated.
With the StormCAD and SewerCAD solvers, there is only one single "Velocity" result field for a conduit or channel. It represents the average velocity and is used to determine the flow travel time. It is computed based on one of the available Velocity Methods, selected in the Calculation Options field called "Average Velocity Method":
Here are the assumptions for each method:
NOTE:
1) Actual Uniform flow velocity - This is obtained by calculating the velocity in the pipe at normal depth. Meaning, it solves the Mannings (or other selected method in the calculation options) for normal depth, based on the flow, slope and other characteristics, to determine the corresponding velocity of flow at that depth. If the normal depth corresponds to a surcharged condition, the full flow velocity is used instead. If the actual calculated depth (from the Gradually Varied Flow solver) is surcharged, then the continuity equation (V=Q/A, with the flow and full pipe area) is used to calculate the velocity.
2) Full flow velocity - This corresponds to the velocity when the pipe is flowing full (depth equal to the top of the pipe). The flow area is equal to the entire cross-sectional area of the pipe. This method takes the Capacity (Full Flow) and divides by the cross-sectional area to find the velocity.
3) Simple Average Velocity - This is simply the average of the velocity at the upstream and downstream end of a conduit. This does not account for any depth changes between the two ends of the pipe as the weighted average velocity method does. The "velocity (In)" and "velocity (out)" used here (and also reported separately for conduits and channels) is based on the flow and flow area corresponding to the depth at the upstream and downstream node, respectively. See note further below. The depth at the node is determined based on the gradually varied flow (GVF) backwater profile calculations (see documentation).
4) Weighted average velocity - With this method, the simple average velocity of each profile segment is considered and given a weight based on its length.
5) Full Depth velocity - This is the relationship with the reported flow and the full cross-sectional area of the conduit.
When using the Implicit solver in SewerGEMS or CivilStorm, there are four velocity result fields:
Each of these velocities is calculated based on the respective depth and flow at the respective point (start, middle or stop) along the conduit or channel (V=Q/A).
The Implicit solver calculates results at multiple points along a conduit or channel, so these are actual separate calculated results. So for example the "Velocity" (and middle velocity) is the actual velocity at the center of the pipe (based on the middle depth and flow), not just an average.
When using the Explicit (SWMM) dynamic solver in SewerGEMS or CivilStorm, there are important differences to keep in mind regarding how velocity is calculated, compared to the Implicit solver. Whereas the Implicit solver calculates multiple points along a pipe and reports the actual calculated start, stop and middle velocity, the SWMM solver divides the network into link-node segments that look like this:
Each link-node segment is the node itself plus half lengths of both the incoming and outgoing pipes (or channels).
For each time step it first solves for the flow into the node and then based on that flow it determines what the depth is in the link-node system (it assumes a constant depth).
So, when using the SWMM solver, the "depth in" and "depth out" result fields (for a conduit or channel) are based on the depths of the adjacent nodes. The "velocity in" and "velocity out" are then computed based on those depths (and the corresponding flows). The "Velocity" result is calculated based on the average depth.
See also: "SWMM Reference Manual Volume II- Hydraulics (pdf)" from the EPA-SWMM website
These differences can cause differences in velocity results between solvers, since they have different assumptions. Notable differences can occur for example if the Implicit solver's middle depth is significantly different than the average of the start and stop depth, since the SWMM solver just uses an average whereas the implicit solver has a separate middle depth calculation.
Consider the below example of a conduit connected to an outfall with a high tailwater. Notice the Implicit solver calculates a relatively steady depth (and velocity) up to the middle of the conduit, whereas the SWMM solver just calculates at each end and uses the average for the middle.
SWMM Implicit
Differences between solvers: GVF-Rational vs. GVF-Convex vs. Implicit vs. Explicit (SWMM)