Monday, December 12, 2011

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. 

Sunday, December 11, 2011

How to Use Bing Maps in InfoSWMM as a Basemap

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

How to Use Bing Maps in InfoSWMM as a Basemap

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

 Step 2.  Add the Aerial Basemap from Bing Maps.
 
 Step 3.  The Base Map has to be clipped and zoomed.
 

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


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

 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.
 
 Step 7.  You now can add nodes and links and view the locale using Google Street View or other using the Tools Preferences. 
 


Saturday, December 10, 2011

Connecting Infrastructure To The Internet from the Dish


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

Sensitivity Analysis in InfoSWMM and H2OMAP SWMM

Subject:  Sensitivity Analysis in InfoSWMM and H2OMAP SWMM

Sensitivity Analysis in InfoSWMM and H2OMAP SWMM

by dickinsonre
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 theReport 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.
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.
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.
Step 3.   Use the Scenario Manger to choose the right Subcatchment Set for Each Scenario.
Step 4.   Use the Database Editor to Edit and modify the Width of Each Subcatchment Set.
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
Step 6.   Use the Batch Simulation Command to run all of the Scenario's.
                                               
Step 7.   Use Report Manager and the tool Compare Graphs to graph the results of Each Scenario together.
Step 8.   In Report Manager you can produce a table that shows the runoff for each of the different scenarios.


Wednesday, December 7, 2011

How InfoSWMM and H2oMAP SWMM Reads CUHP Hydrographs

How InfoSWMM and H2oMAP SWMM Reads CUHP Hydrographs

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


Figure 1.  Location of Files Command in Run Manager


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


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

Figure 3.  InfoSWMM and H2OMAP SWMM Lateral  Inflow Hydrographs

Figure 4.  CHUP Inflows File Descrpiption in the CUHP manual.
Figure 5. Cover of CUHP 2005 User Manual from 2010

Saturday, December 3, 2011

How to Make Contours in InfoSWMM and H2oMAP SWMM

Subject:  How  to Make Contours in InfoSWMM and H2oMAP SWMM

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.

Mind The Crap From the Dish

Mind The Crap From the Dish

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

Friday, December 2, 2011

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
25.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.
Figure 1.  You can use a Scatter Graph in SWMM 5 to show the relationship between Volume and Depth.



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.

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.

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. 

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.

Thursday, December 1, 2011

InfoSWMM Selection Set and Domain Manager

Subject:  InfoSWMM Selection Set and Domain Manager

InfoSWMM and H2Map SWMM Selection Set and Domain Manager

by dickinsonre
Subject:   InfoSWMM and H2Map SWMM 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

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.


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