Subject: The number of Hydraulic Iterations in Various Versions of SWMM 5.
The maximum number of iterations was 4 before SWMM 5.0.021 and 8 iterations after SWMM 5.0.021. In InfoSWMM and H2OMAP SWMM you can have a a minimum of 2 iterations or a maximum of 8 iterations for compatibility to SWMM 5 and backwards compatibly with your earlier InfoSWMM models.
.
Subject: Time Step Selection in SWMM 5
1stThe time step you use in SWMM 5 is controlled from the top by the rainfall interval (Figure 1):
1. All of your time steps should be less than the rainfall interval,
2. The hydrology time step should be less than or equal to the smallest raingage rainfall interval in your network,
3. The hydraulic time step should be less than or equal to the hydrology time step and should be based on the hydraulic needs of the your network. Short length links, pump and weirs may require a smaller maximum hydraulic time step.
2ndThe report time step controls what you see in the graphics output of SWMM 5. If you see a large difference between that you see in the graphics output and the report text file it is because you have a large difference between the report time step and the average time step used during the simulation.
Solution: If there is a large discrepancy in the graphics and report text file then the best solution is to reduce the maximum time hydraulic time step so it is closer to the average time step and also to make the report time step closer to the Maximum time step (Figure 2).
Figure 1: Relationship between the rainfall, hydrology and hydraulic time steps.
Figure 2: Relationship between the minimum, average and maximum simulation time steps and the report time step.
The Startup and Shutoff depths are evaluated 1st followed by any Control Rules. The priority value is just to decide between two or more control rules that are both active at the current time step. The rule with the highest priority will be used or in the case of two rules with the same priority the last control rule evaluated will be used during the current time step.
Subject: Node Surcharge Summary in SWMM 5
Surcharging occurs in SWMM 5 when water rises above the crown of the highest conduit. The RPT file of SWMM 5 lists the surcharging in hours in the Node Surcharge Summary Table (Figure 1) using the definitions for surcharging shown in Figure 2. Figure 3 shows the relationship between the output columns of the table.
Node surcharging occurs at a node if:
1. The node cannot pond and the node depth is above the highest pipe crown elevation connected to the node, or
2. The node can pond and the node depth is above the highest pipe crown elevation connected to the node and
3. The node depth is below the full depth of the node.
Node Flooding occurs if the water surface elevation is at the rim or above the rim elevation of the node.
Figure 1: Node Surcharge Summary Table
Figure 2: Definition of Surcharging at a Node in SWMM 5.
Figure 3: The definition of the Height above Crown and Depth below Rim columns in the Node Surcharge Table.
Note: There is a function called ForceMain in SWMM5/InfoSWMM whose purpose is to compute the Darcy-Weisbach friction factor for a force main using the Swamee and Jain approximation to the Colebrook-White equation.
f = forcemain_getFricFactor(xsect.rBot, d/4.0, 1.0e12);
return sqrt(f/185.0) * pow(d, (1./6.));
double forcemain_getFricFactor(double e, double hrad, double re)
//// Input: e = roughness height (ft)
// hrad = hydraulic radius (ft)
// re = Reynolds number
// Output: returns a Darcy-Weisbach friction factor
// Purpose: computes the Darcy-Weisbach friction factor for a force main
// using the Swamee and Jain approximation to the Colebrook-White equation.
{ double f;
if ( re < 10.0 ) re = 10.0;
if ( re <= 2000.0 ) f = 64.0 / re;
else if ( re < 4000.0 )
{ f = forcemain_getFricFactor(e, hrad, 4000.0);
f = 0.032 + (f - 0.032) * ( re - 2000.0) / 2000.0; }
else { f = e/3.7/(4.0*hrad);
if ( re < 1.0e10 ) f += 5.74/pow(re, 0.9);
f = log10(f);
f = 0.25 / f / f; }
return f;}
From http://en.wikipedia.org/wiki/Darcy_friction_factor_formulae
