Saturday, December 31, 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

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

LINKS                 ALL
NODES               ALL

Step 3.  Run the Batch file

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.

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

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.

Tuesday, December 27, 2011

RDII or Tri Triangular Unit Hydrograph in InfoSewer

Subject:  RDII or Tri Triangular Unit Hydrograph in InfoSewer

RDII or Tri Triangular Unit Hydrograph in InfoSewer

by dickinsonre
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 unithydrograph, 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
 Figure 2.  The Unit Hydrograph is defined for various values of R, R1,  R2, T1,  T2,  T3, K1,  K2 and  K3. 

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

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.

Saturday, December 24, 2011

How is the Maximum Link Flow Applied in SWMM 5?

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

How is the Maximum Link Flow Applied in SWMM 5?

by dickinsonre
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.
Figure 2. Dynamic Wave Solution link  flow limit.
Figure 3.  The Link  flow in the dynamic wave solution has three checks at each iteration in a time step.

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.
Adverse Slope Convention  in  SWMM 5

Friday, December 16, 2011

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:

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

by dickinsonre
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.
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
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.

Tuesday, December 13, 2011

InfoSWMM and H2OMAP SWMM Facility Manager

InfoSWMM and H2OMap SWMM Facility Manager

by dickinsonre
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.


Monday, December 12, 2011

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

How to Make Contours in InfoSWMM and H2oMAP SWMM

by dickinsonre
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 haveInfoSWMM 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).
Figure 1.  Contour Tool in the Contour Tab of the Attribute Browser.
Figure 2.  Contour to DEM command in the InfoSWMM Subcatchment Manager will convert the created Contour to an Elevation or DEM file.
Figure 3.  Convert the Value Field and  NOT the level Field of the contour.
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.

SWMM 5 Error Messages

Engine Error Number
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. 

AI Rivers of Wisdom about ICM SWMM

Here's the text "Rivers of Wisdom" formatted with one sentence per line: [Verse 1] 🌊 Beneath the ancient oak, where shadows p...