Archive for December, 2011

How to use SWMM 5 DOS to make an Output Table in the RPT file

 

Subject:   How to use SWMM 5 DOS to make an Output Table in the RPT file

 

You can make tables of the node,  link  and  Subcatchment output data in SWMM 5 if you use the DOS SWMM 5 program but not the Windows DLL.   Step 1 is to create the DOS batch file, Step 2 is to select the nodes, links and subcatchments, Step 3 is to run the batch file and Step 4 is to view the RPT tables or extract the data to Excel.  You can do this directly in the InfoSWMM and H2OMAP SWMM graphical user interfaces by using Run Manager, Step 5 to select the nodes, links and subcatchments and Step 6 to view the tables in the browser.

 

Step 1.   Make a Batch File to call the DOS SWMM 5

 

swmm5.exe Example1.inp  D:\swmm5.0.022\bob.rpt

 

pause

 

Step 2.  Add the nodes,  links and  subcatchments tables you want to generate in the RPT file

 

[REPORT]

 

CONTROLS         NO

 

LINKS                 ALL

 

NODES               ALL

 

SUBCATCHMENTS ALL

 

Step 3.  Run the Batch file

 

Image003

 

 

 

Step 4.  Extract the Tables from the RPT File of SWMM 5

 

<<< Node 17 >>>

 

  ———————————————————————————

 

                           Inflow  Flooding     Depth      Head       TSS      Lead

 

  Date        Time            CFS       CFS      feet      feet      MG/L      UG/L

 

  ———————————————————————————

 

  JAN-01-1998 01:00:00      0.000     0.000     0.000   980.000     0.000     0.000

 

  JAN-01-1998 02:00:00      5.910     0.000     0.608   980.608    26.065     5.213

 

  JAN-01-1998 03:00:00     11.935     0.000     0.887   980.887    22.826     4.565

 

  JAN-01-1998 04:00:00     18.291     0.000     1.143   981.143    21.176     4.235

 

  JAN-01-1998 05:00:00     12.640     0.000     0.916   980.916    22.426     4.485

 

  JAN-01-1998 06:00:00      3.925     0.000     0.493   980.493    27.578     5.516

 

  JAN-01-1998 07:00:00      0.388     0.000     0.161   980.161    38.134     7.627

 

  JAN-01-1998 08:00:00      0.067     0.000     0.071   980.071    26.937     5.387

 

  JAN-01-1998 09:00:00      0.029     0.000     0.048   980.048     1.878     0.376

 

 

 

Step 5.  InfoSWMM and H2OMAP SWMM dialog for selecting nodes, links and subcatchments for generating a detailed RPT file table.

 

Image002

 

Step 6.  Sample InfoSWMM and H2OMAP SWMM RPT Tables if Report Options is used.

 

Image004

InfoSWMM and H2OMAP SWMM are different graphical  user interfaces with similar  tools to the current  version of SWMM 5.  They both use a C++ engine built around the C code engine of SWMM 5.  Most of these blogs apply to SWMM 5, InfoSWMM and H2OMAP SWMM.

 


Leave a Comment

Making a Model in SWMM 5

Image002

Leave a Comment

RDII or Tri Triangular Unit Hydrograph in InfoSewer

Subject:  RDII or Tri Triangular Unit Hydrograph in InfoSewer

The RDII method in InfoSewer is similar to the RDII or RTK  method in  InfoSWMM with some differences.    The RTK data for triangles 1, 2 and 3 are defined in the Unit Hydrograph but instead of individual R values, the overall R is set and the Percent R1,  R2 and R3 are defined based on the total  R.  R3 is calculated internally as 100 – R1 – R2.   Each loading manhole with RDII flow has a total  area, a hyetograph and a Unit Hydrograph.  The hyetograph has to be set at multiples of the unit hydrograph, so you can define the time or X columns with integers and then use the Block Edit command to change X to minutes by multiplying  by the Unit Hydrograph time (Figure 1).   You can use only one component if you set R1 or R2 to 100 percent or R3 to 100 percent by setting R1 and R2 to 0 percent (Figure 2).  The overall area of the Unit Hydrograph is divided amongst the loading manhole using the Subbasin Area (Figure 3).   The storm flows generated can be viewed using a Group Graph (Figure 4).

Figure 1.   Hyetograph Curve for the RDII Unit Hydrograph

Image005

Figure 2.  The Unit Hydrograph is defined for various values of R, R1,  R2, T1,  T2,  T3, K1,  K2 and  K3.

Image003

Figure 3.  The Unit Hydrograph and Hyetograph are tied to a particular loading manhole using a Subbasin Area.

 

Image004


Figure 4.  The Unit Hydrographs that are generated can be viewed using a Group loading Manhole Graph.  The R1, R2 and R3 have only one triangle.

Image002

 

Leave a Comment

How is the Maximum Link Flow Applied in SWMM 5?

Subject:  How is the Maximum Link Flow Applied in SWMM 5?

The maximum flow limit for a link applies to the kinematic wave and the dynamic wave solution.   The inflow to the link  in the kinematic wave solution is limited (Figure 1) but the calculated link flow is limited in the dynamic wave solution after the link flow (Figure 2):

1.       Is checked using the Culvert Inlet Equations (optional)

2.      The normal flow equation is checked (internally optional depending on the Normal flow options) and

3.      The Picard iteration solution under relaxation parameter (always 0.5) is applied (Figure 3).

Figure 1.  Kinematic Wave Solution Limits the Inflow to  the Link Maximum limit.

Image008

Figure 2. Dynamic Wave Solution link  flow limit.

Image009

Figure 3.  The Link  flow in the dynamic wave solution has three checks at each iteration in a time step.

Image010

Leave a Comment

Adverse Slope Convention in SWMM 5

Subject:  Adverse Slope Convention  in  SWMM 5

If the slope of a link  is negative and the solution  is dynamic wave then the following data will be switched in link.c in SWMM 5.  All upstream data for the  link  is switched to the downstream end of the link  and  vice versa.   The means that if the flow  is from the original upstream node to the downstream node the flow  will  be negative in the output of  SWMM 5.

Negative flow in SWMM 5 means:

1.   The link has an adverse or negative slope,

2.   The link  has reverse flow if the link slope is positive. 

Image002

Leave a Comment

Weather InfoGraphics


Leave a Comment

How to make a shape file from a Output Relate in InfoSWMM

Note:   How to make a shape file from a Output Relate in InfoSWMM:

 Step 1.  Make an Output Relate for the Conduit Summary Table using the Operation Tab in Attribute Browser.

 

 

Image002

 

Step 2:  Using the GIS Gateway you can save q/Q and d/D to a shape file that can then be added to the Arc GIS Table of  Contents

 

Image004

 

 

Step 3.   You now have a Shape File for the value of q/Q or Flow over Full Flow.  You can also use the Symbology Tab in Data Properties to color and/or make bar charts and bubble charts from the summary q/Q and d/D values during the simulation for each link.

 

 

Image005

 

Leave a Comment

InfoSWMM and H2oMAP SWMM Facility Manager

The InfoSWMM Facility Manager offers the knowledgeable engineer complete control what elements are simulated in her or his model.  You can make active or inactivate elements based the type of Network Element, A Network Path, A Mouse Drawn Map Selection, The Domain, A selection set, a DB Query, a Query Set and a Special Query.  You can make the simulated network smaller or larger depending on your simulation or calibration requirements.  For example, you can have a whole basin network but model only a branch or a subset of the network if you are using the Calibrator or Designer Addons.

 Image003 Image002

Leave a Comment

How to Find the Proportional loading to a link or manhole in InfoSewer

Subject:  How to Find the Proportional loading to a link  or manhole in InfoSewer

You can use the Upstream Trace tool in InfoSewer to find the upstream nodes and links from any link in InfoSewer.   Once you have the upstream traced network then add the traced upstream nodes and links to the  domain.  Once you have the domain then these steps will allow you to calculate the proportion of flows from each upstream node and map the proportion using Map Display.

 

Step 1.  Use the Tool Trace Upstream Network to find and make a Domain out of the Traced upstream Network

 

Image002

 

Step 2.  The Traced Upstream Network

 

Image003

 

Step 3.  Use the created domain in Output Report Tabular Reports

 

Image004

 

Step 4.  Copy the ID and Total Flow from the Loading Manhole Report

 

Image005

 

Step 5.  Use the Domain in the DB Table Manhole Infomation

 

Image006

 

Step 6.  Create a new information field called Proportion for example

 

Image007

 

Step 7.  Map the new data field proportion using Map Display

 

Image008

 

Step 8.  Now you have a Map Display of the Proportional loading to a link  or manhole in InfoSewer

 

Image008

 

Step 9.  40 percent of the flow comes from one node an the other 60 percent comes from the other node to the link with a d/D over 0.5.

 

Image009

 

 

 

Leave a Comment

SWMM 5 Error Messages

Engine Error Number Description
ERROR 101: memory allocation error.                                                                                             
ERROR 103: cannot solve KW equations for Link                                                                                   
ERROR 105: cannot open ODE solver.                                                                                              
ERROR 107: cannot compute a valid time step.                                                                                    
ERROR 108: ambiguous outlet ID name for Subcatchment                                                                            
ERROR 109: invalid parameter values for Aquifer                                                                                 
ERROR 110: ground elevation is below water table for Subcatchment                                                               
ERROR 111: invalid length for Conduit                                                                                           
ERROR 112: elevation drop exceeds length for Conduit                                                                            
ERROR 113: invalid roughness for Conduit                                                                                        
ERROR 114: invalid number of barrels for Conduit                                                                                
ERROR 115: adverse slope for Conduit                                                                                            
ERROR 117: no cross section defined for Link                                                                                    
ERROR 119: invalid cross section for Link                                                                                       
ERROR 121: missing or invalid pump curve assigned to Pump                                                                       
ERROR 131: the following links form cyclic loops in the drainage system:                                                        
ERROR 133: Node %s has more than one outlet link.                                                                               
ERROR 134: Node %s has illegal DUMMY link connections.                                                                          
ERROR 135: Divider %s does not have two outlet links.                                                                           
ERROR 136: Divider %s has invalid diversion link.                                                                               
ERROR 137: Weir Divider %s has invalid parameters.                                                                              
ERROR 138: Node %s has initial depth greater than maximum depth.                                                                
ERROR 139: Regulator %s is the outlet of a non-storage node.                                                                    
ERROR 141: Outfall %s has more than 1 inlet link or an outlet link.                                                            
ERROR 143: Regulator %s has invalid cross-section shape.                                                                        
ERROR 145: Drainage system has no acceptable outlet nodes.                                                                      
ERROR 151: a Unit Hydrograph in set %s has invalid time base.                                                                   
ERROR 153: a Unit Hydrograph in set %s has invalid response ratios.                                                             
ERROR 155: invalid sewer area for RDII at node                                                                                  
ERROR 156: inconsistent data file name for Rain Gage                                                                            
ERROR 157: inconsistent rainfall format for Rain Gage                                                                           
ERROR 158: time series for Rain Gage %s is also used by another object.                                                         
ERROR 159: recording interval greater than time series interval for Rain Gage                                                   
ERROR 161: cyclic dependency in treatment functions at node                                                                     
ERROR 171: Curve %s has invalid or out of sequence data.                                                                        
ERROR 173: Time Series %s has its data out of sequence.                                                                         
ERROR 181: invalid Snow Melt Climatology parameters.                                                                            
ERROR 182: invalid parameters for Snow Pack                                                                                     
ERROR 183: no type specified for LID                                                                                            
ERROR 184: missing layer for LID                                                                                                
ERROR 185: invalid parameter value for LID                                                                                      
ERROR 186: invalid parameter value for LID placed in Subcatchment                                                               
ERROR 187: LID area exceeds total area for Subcatchment                                                                         
ERROR 188: LID capture area exceeds total impervious area for Subcatchment                                                      
ERROR 191: simulation start date comes after ending date.                                                                       
ERROR 193: report start date comes after ending date.                                                                           
ERROR 195: reporting time step or duration is less than routing time step.                                                      
ERROR 200: one or more errors in input file.                                                                                    
ERROR 201: too many characters in input line                                                                                    
ERROR 203: too few items                                                                                                       
ERROR 205: invalid keyword %s                                                                                                   
ERROR 207: duplicate ID name %s                                                                                                 
ERROR 209: undefined object %s                                                                                                  
ERROR 211: invalid number %s                                                                                                    
ERROR 213: invalid date/time %s                                                                                                 
ERROR 217: control rule clause out of sequence                                                                                  
ERROR 219: data provided for unidentified transect                                                                              
ERROR 221: transect station out of sequence                                                                                     
ERROR 223: Transect %s has too few stations.                                                                                    
ERROR 225: Transect %s has too many stations.                                                                                  
ERROR 227: Transect %s has no Manning’s N.                                                                                      
ERROR 229: Transect %s has invalid overbank locations.                                                                          
ERROR 231: Transect %s has no depth.                                                                                            
ERROR 233: invalid treatment function expression                                                                                
ERROR 301: files share same names.                                                                                              
ERROR 303: cannot open input file.                                                                                              
ERROR 305: cannot open report file.                                                                                             
ERROR 307: cannot open binary results file.                                                                                     
ERROR 309: error writing to binary results file.                                                                                
ERROR 311: error reading from binary results file.                                                                              
ERROR 313: cannot open scratch rainfall interface file.                                                                         
ERROR 315: cannot open rainfall interface file                                                                                  
ERROR 317: cannot open rainfall data file                                                                                       
ERROR 318: date out of sequence in rainfall data file                                                                           
ERROR 319: invalid format for rainfall interface file.                                                                         
ERROR 321: no data in rainfall interface file for gage                                                                          
ERROR 323: cannot open runoff interface file                                                                                    
ERROR 325: incompatible data found in runoff interface file.                                                                    
ERROR 327: attempting to read beyond end of runoff interface file.                                                              
ERROR 329: error in reading from runoff interface file.                                                                         
ERROR 330: hotstart interface files have same names.                                                                            
ERROR 331: cannot open hotstart interface file                                                                                  
ERROR 333: incompatible data found in hotstart interface file.                                                                  
ERROR 335: error in reading from hotstart interface file.                                                                       
ERROR 336: no climate file specified for evaporation and/or wind speed.                                                         
ERROR 337: cannot open climate file                                                                                             
ERROR 338: error in reading from climate file                                                                                   
ERROR 339: attempt to read beyond end of climate file                                                                           
ERROR 341: cannot open scratch RDII interface file.                                                                             
ERROR 343: cannot open RDII interface file                                                                                      
ERROR 345: invalid format for RDII interface file.                                                                              
ERROR 351: cannot open routing interface file                                                                                   
ERROR 353: invalid format for routing interface file                                                                            
ERROR 355: mis-matched names in routing interface file                                                                          
ERROR 357: inflows and outflows interface files have same name.                                                                 
ERROR 361: could not open external file used for Time Series                                                                    
ERROR 363: invalid data in external file used for Time Series                                                                   
ERROR 401: general system error.                                                                                                
ERROR 402: cannot open new project while current project still open.                                                            
ERROR 403: project not open or last run not ended.                                                                              
ERROR 405: amount of output produced will exceed maximum file size;either reduce Ending Date or increase Reporting Time Step. 

Leave a Comment

How to Use Bing Maps in InfoSWMM as a Basemap

Note:   How to Use Bing Maps in InfoSWMM as a Basemap

A great feature of Arc GIS 10 is the ability to use background maps from Bing for your model.  A few steps are necessary to set up the coordinates, import the basemap, clip the basemap and set the new extents:

Step 1.  Set the Current Coordinate System for the intended network.

Image002

Step 2.  Add the Aerial Basemap from Bing Maps.

Image003

Step 3.  The Base Map has to be clipped and zoomed.

Image004

 Step 4.  Zoom to your network and clip the rest of the Map out of the Maximum Extents.

 Image006

 Step 5.  Set the Maximum Extents of your Network using the Data Frame Tab in Data Frame Properties.

 Image005

 Step 6.  You can also set the background color for the area outside of the clipped Base Map if you so desire using the Frame Tab.

 Image007

 Step 7.  You now can add nodes and links and view the locale using Google Street View or other using the Tools Prefences.

 Image009

 Image008

Leave a Comment

Connecting Infrastructure To The Internet from the Dish

Connecting Infrastructure To The Internet from the Dish

Image002

Engineers can now link a building’s rainwater catchment system to weather predictions from the Internet. Alerted city services can then empty water storage basins so that stormwater doesn’t flood our sewers:

It may sound like a trivial problem, but the EPA estimates that the U.S. has $13 billion invested in wastewater infrastructure alone. More importantly, the majority of America’s largest cities–more than 700 in all–dump millions of gallons of raw sewage into our waterways every time it rains, because their sewer and stormwater systems were designed a century ago. …

Giving building planners the assurance that they’ll always have access to a free water supply means they can actually use it. And putting these on enough buildings could go a long way to solving the problem of combined sewer and stormwater systems being overwhelmed when it rains.

(Photo: Residents try to unblock a sewage grate to free floodwater on Coney Island after Hurricane Irene hit New York, August 28, 2011. By Emmanuel Dunand/AFP/Getty Images)

 

http://andrewsullivan.thedailybeast.com/2011/12/connecting-infrastructure-to-the-internet.html

Leave a Comment

Sensitivity Analysis in InfoSWMM and H2OMAP SWMM

Subject:  Sensitivity Analysis in InfoSWMM and H2OMAP SWMM

 It is easy to perform sensitivity analysis in InfoSWMM and H2oMAP SWMM using the Scenario Manager, Dataset manager, Block Edit in the Database Editor, Batch Simulation and the Report Manager.  For example, we will do a sensitivity analysis for the Subcatchment Width (one the physical parameters in the Subcatchment analysis of SWMM 5 – see Figure 1).  The width is normally the area divided by the overland path length but there are many common means of calculating the width.   

Figure 1.  Physical Data used in the Calculation of Surface Runoff using the Non Linear Reservoir Routing method in SWMM 5.

 

Image004

 

Image012

 

Figure 2.  The base scenario for our sensitivity analysis.

 

There are seven main steps in the sensitivity analysis of the width:

 

Step 1.   Use the Scenario Explorer to make Child Scenarios from the Base Scenario.  For ease of understanding we will name each of the Child Scenario’s the percent change in the width parameter.  Thus, W-50, will be the Base Width Plus 50 percent.

 

 

Image001

 

Step 2.   Use the Dataset Manager to create different Subcatchment Sets that will be used for each of the Scenario’s.  Again for ease of understanding we will use the name S_W+50 etc for the Sets to match the change in the Width Parameter.

 

Image005

 

Step 3.   Use the Scenario Manger to choose the right Subcatchment Set for Each Scenario.

 

Image007

 

Step 4.   Use the Database Editor to Edit and modify the Width of Each Subcatchment Set.

 

Image008

 

Step 5.   Use the Block Edit tool to multiply the Base Width Value by the needed value, 1.25, 1.50, 0.75, 0.50

 

Image009

 

Step 6.   Use the Batch Simulation Command to run all of the Scenario’s.

 

Image010

 

 

Step 7.   Use Report Manager and the tool Compare Graphs to graph the results of Each Scenario together.

 

Image011

 

Step 8.   In Report Manager you can produce a table that shows the runoff for each of the different scenarios.

 

Image013

 

Leave a Comment

How InfoSWMM and H2oMAP SWMM Reads CUHP Hydrographs

Note:  The Colorado Urban Hydrograph Procedure (CHUP) 2010 version generates a SWMM 5 Inflows Files containing a time series of flow inflows for 1 to many nodes (Figure 4 and Figure 5).    The created Inflows file (Figure 2) can be imported into InfoSWMM and H2MAP SWMM without any alteration by using the Files command in Run Manager (Figure 1) and graphed using the Output Manager of InfoSWMM and H2OMAP SWMM (Figure 3).

 Image004

 Figure 1.  Location of Files Command in Run Manager

The inflows will be read  from the Inflows file, which has this format:

Image005

Figure 2.  Header format of the CUHP Exported Hydrograph File

InfoSWMM and H2oMAP SWMM will match the Node Names in the Inflows file to the network node names and import and interpolate the inflows based on the Inflows time step and your hydraulic time step to generate Lateral  Inflow Hydrographs

Image006

Figure 3.  InfoSWMM and H2OMAP SWMM Lateral  Inflow Hydrographs

Image002

Figure 4.  CHUP Inflows File Descrpiption in the CUHP manual.

Image003

Figure 5. Cover of CUHP 2005 User Manual from 2010

Leave a Comment

How to Make Contours in InfoSWMM and H2oMAP SWMM

Subject:  How  to Make Contours in InfoSWMM and H2oMAP SWMM

It is easy to make contours out of node input data or node output data in InfoSWMM and H2oMAP SWMM using the Contour Tool in the Contour Tab of the Attribute Browser.  You can control the resolution and the type of smoothing for the created contour (Figure 1).  If you have InfoSWMM Suite you can use the Contour to DEM command in the Subcatchment Manager to convert the created Contour to an Elevation or DEM file (Figure 2 and Figure 3).   The Layer properties for the created elevation can be altered in Arc GIS to make a better visual depiction of the elevation (Figure 4).

Image005

Figure 1.  Contour Tool in the Contour Tab of the Attribute Browser.

Image002

Figure 2.  Contour to DEM command in the InfoSWMM Subcatchment Manager will convert the created Contour to an Elevation or DEM file.

Image003

Figure 3.  Convert the Value Field and  NOT the level Field of the contour.

Image004

Figure 4.  The Arc GIS Layer properties can be used to alter the default color ramp and the number of classes used in the color ramp.

,

Leave a Comment

Mind The Crap From the Dish

Mind The Crap From the Dish

Image002

Sally Aldee fell in the Thames and gashed her leg, a prospect that horrified every medical professional she met. She subsequently traced the river’s pollution from Victorian times to today:

The river – which by the way was both the source of the city’s drinking water and the repository for all its poop – became choleric and pestilent. In the summer of 1858, the fumes became so bad they got a name. The “Great Stink” forced members of Parliament to write the legislation that gave the all-clear to Joseph Bazalgette, London’s chief engineer of public works, to build the two massive interceptor sewers that catch London’s sewage and run-off before they’re belched into the Thames. To this day, these brick and mortar Victorian artifacts comprise the backbone of London’s sewer system. …

http://andrewsullivan.thedailybeast.com/2011/12/mind-the-crap.html

Leave a Comment

Storage Volume vs Depth Equation in SWMM 5

Subject:  Storage Volume vs Depth Equation in SWMM 5

 A storage node in SWMM 5 can have either a functional form or a tabular depth/area table.  The area functional form of a storage node is:

 Area           =      A * Depth^B + C  and the Volume has the form in  node.c of the SWMM 5 of

 Volume     =      A/(B+1)*Depth^(1+B) + C*Depth

 For example if C is 25 square meters, A is 20 and the exponent B is 0.5 we get the following values for area and volume and you can also plot a Scatter Plot of Volume vs Depth in SWMM 5 (Figure 1).

 

Depth

Area

Volume

Meters

M^2

M^3

0

0.00

0.00

1

45.00

38.33

2

78.28

87.71

3

109.64

144.28

4

140.00

206.67

5

169.72

274.07

6

198.99

345.96

7

227.92

421.94

8

256.57

501.70

9

285.00

585.00

10

313.25

671.64

11

341.33

761.44

12

369.28

854.26

 Table 1.  Area and Volume for a Storage Node in SWMM 5.

 Image004

Figure 1.  You can use a Scatter Graph in SWMM 5 to show the relationship between Volume and Depth.

 

Leave a Comment

Lambda Calculus in the SWMM 5 Dynamic Wave Solution

Subject:  Lambda Calculus in the SWMM 5 Dynamic Wave Solution

SWMM 5 uses the method of Successive under-relaxation to solve the Node Continuity Equation and the Link Momentum/Continuity Equation for a time step.  The dynamic wave solution in dynwave.c will use up to 8 iterations to reach convergence before moving onto the next time step.  The differences between the link flows and node depths are typically small (in a non pumping system) and normally converge within a few iterations unless you are using too large a time step.  The number of iterations is a minimum of two with the 1st iteration NOT using the under-relaxation parameter omega. The solution method can be term successive approximation, fixed iteration or Picard Iteration, fixed-point combinatory, iterated function and Lambda Calculus. In computer science, iterated functions occur as a special case of recursive functions, which in turn anchor the study of such broad topics as lambda calculus, or narrower ones, such as the denotational semantics  of computer programs (http://en.wikipedia.org/wiki/Iterated_function). 

In the SWMM 5 application of this various named iteration process there are three main concepts for starting, iterating and stopping the iteration process during one time step:

·         The 1st guess of the new node depth or link flow is the current link flow (Figure 3) and the new estimated node depths and link flows are used at each iteration to estimate the new time step depth or flow.  For example, in the node depth (H) equation dH/dt = dQ/A the value of dQ or the change in flow and the value of A or Area is updated at each iteration based on the last iteration’s value of all node depths and link flows.  

·         A bound or a bracket on each node depth or link flow iteration value is used by averaging the last iteration value with the new iteration value.  This places a boundary on how fast a node depth or link flow can change per iteration – it is always ½ of the change during the iteration (Figure 1).  

·         The Stopping Tolerance (Figure 2) determines how many iterations it takes to reach convergence and move out of the iteration process for this time step to the next time step.

Image005

Figure 1.  Under relaxation with an omega value of ½ is done on iterations 2 through a possible 8 in SWMM 5. This is not done for iteration 1.

Image008

Figure 2.  if the change in the Node Depth is less than the stopping tolerance in SWMM 5 the node is considered converged.  The stopping tolerance has a default value of 0.005 feet in SWMM 5.0.022. 

Image002

Figure 3.  The differences between the link flows and node depths are typically small (in a non pumping system) and normally converge within a few iterations unless you are using too large a time step.  The number of iterations is a minimum of two with the 1st iteration NOT using the under-relaxation parameter omega.

Leave a Comment

InfoSWMM Selection Set and Domain Manager

Subject:  InfoSWMM Selection Set and Domain Manager

You can use the Domain to easily make selection sets using these two steps.  You make a Domain which is the areas of the network you are interested in at the current time and then save your Domain of Interest in a Selection Set.

Step 1:  Go to Domain Manager and use Map Selection, Query or the Network to make a domain

Image001

Step 2.  Go to Selection Sets in the Operation Tab of the  Attribute Browser and make a New Set and load the domain into your set.

Image002

Leave a Comment

Follow

Get every new post delivered to your Inbox.

Join 53 other followers