The table below displays the list of validation messages that will be displayed in the Output
Window. Click on the message text for further information.
| E0005 |
 RTC definition must not contain spaces
|
Info
|
Network object ID
|
|
Cause
|
The name of an RTC Table or Variable referenced in the RTC definition field of the sections editor for a bank or base linear structure contains spaces.
|
|
Advice
|
Review RTC definition values in sections editor.
|
|
|
| E0006 |
RTC definition for breach must have a measurement type of Depth or Height above datum
|
Info
|
Network object ID
|
|
Cause
|
An RTC Table or Variable has been referenced in the RTC definition field of the sections editor for a bank or base linear structure, but the Output measurement field (for a Table) or Measurement field (for a Variable) of the RTC definition is not set to Depth or Height above datum.
See Modelling Breaches in Banks and Linear Structures.
|
|
Advice
|
Set measurement field of RTC definition to either Depth or Height above datum.
|
|
|
| E0150 |
Bank array has at least one vertex with undefined level
|
Info
|
River Reach / Inline Bank ID
|
|
Cause
|
The section data of a River Reach bank or Inline Bank object has one or more vertices with a missing Bank level value.
|
|
Advice
|
Ensure banks have Bank level values set at all points.
|
|
|
| E2001 |
The network contains no nodes or links or 2D zones
|
Info
|
-
|
|
Cause
|
There are no node or link objects, or 2D zone objects present in the network.
Simulations cannot be run if none of these objects exist.
|
|
Advice
|
Add node, link and/or 2D zone objects to the network.
|
|
|
| E2002 |
Number of 2d elements <number of elements> exceeds the licence limit <licence limit>
|
Info
|
-
|
|
Cause
|
The number of 2D elements in the network exceeds the number of elements that are included in the InfoWorks ICM licence.
|
|
Advice
|
Either reduce the number of 2D elements in the network or increase the element limit included in your licence.
|
|
|
| E2003 |
The number of nodes <number of nodes> exceeds the licence limit <licence limit>
|
Info
|
-
|
|
Cause
|
The number of nodes in the network exceeds the number of nodes that are included in the InfoWorks ICM licence.
|
|
Advice
|
Either reduce the number of nodes in the network or increase the node limit included your licence.
|
|
|
|
E2025
|
Node is not connected to a link
|
Info
|
Node ID
|
|
Cause
|
A node whose Node type is set to Connect 2D is not connected to a link. A Connect 2D node must be connected to a conduit whose Conduit type is set to either Linear Drainage (2D) or Conduit (2D).
|
|
Advice
|
Ensure that the Connect 2D node is connected to a conduit whose type is set to either Linear Drainage (2D) or Conduit (2D). Alternatively, change the Node type setting to another type of node.
|
|
|
|
E2026
|
Manhole floor above manhole roof
|
Info
|
Node ID
|
|
Cause
|
Applicable to nodes whose Type is set to Manhole.
Chamber floor value > Chamber roof value.
|
|
Advice
|
Check the manhole parameters of the reported node.
|
|
|
|
E2026
|
Not in head discharge table
|
Info
|
Node ID
|
|
Cause
|
Applicable to nodes whose Node type is set to Manhole and Flood type is set to Gully or Inlet.
Head discharge table associated with the node has not been defined.
|
|
Advice
|
Define new Head Discharge Table, or select an existing table.
|
|
|
|
E2027
|
Flood depth 2 not above flood depth 1
|
Info
|
Node ID
|
|
Cause
|
Applicable to nodes whose Node type is set to Manhole and whose Flood type is either Storage or Gully where no Storage array has been defined for the gully.
Flood depth 1 value > Flood depth 2 value.
|
|
Advice
|
Check the manhole parameters of the reported node.
|
|
|
|
E2028
|
Not greater than 0.0
|
Info
|
Node ID
|
|
Cause
|
Applicable to nodes of whose Type is set to Storage or Manhole and whose Flood type is set to Gully.
Applicable to rows in the Level/Plan Area Storage Grid except for first and last row:
Plan Area value in the Level / Plan Storage Grid of the node <= 0
|
|
Advice
|
Check Level / Plan Area Storage Grid values.
|
|
|
|
E2033
|
Lowest storage level is below chamber
floor
|
Info
|
Node ID
|
|
Cause
|
Applicable to nodes whose Node type is set to Manhole and Flood type is set to Gully.
The lowest Level value in the Level / Plan Area Storage Grid of the gully node < Chamber floor level.
|
|
Advice
|
Check Level / Plan Area Storage Grid values. Set Relative to Ground option if required.
|
|
|
|
E2034
|
Lowest storage level is above ground
|
Info
|
Node ID
|
|
Cause
|
Applicable to nodes whose Node type is set to Manhole and whose Flood Type is set to Gully.
The lowest Level value in the Level / Plan Area Storage Grid of the gully node > Ground level.
|
|
Advice
|
Check Level / Plan Area Storage Grid values.
|
|
|
|
E2035
|
Vegetation level is above the highest
storage level
|
Info
|
Node ID
|
|
Cause
|
Applicable to nodes whose Node type is set to Pond.
The Vegetation level value is outside of the range defined in the Level / Plan Area / Perimeter Grid of the Pond node.
|
|
Advice
|
Check Level / Plan Area / Perimeter Grid and Vegetation levels.
|
|
|
|
E2036
|
Vegetation level is below the lowest
storage level
|
Info
|
Node ID
|
|
Cause
|
Applicable to nodes whose Node type is set to Pond.
The Vegetation level value is outside of the range defined in the Level / Plan Area / Perimeter Grid of the Pond node.
|
|
Advice
|
Check Level / Plan Area / Perimeter Grid and Vegetation levels.
|
|
|
|
E2037
|
Liner level is below the lowest storage
level
|
Info
|
Node ID
|
|
Cause
|
Applicable to nodes whose Type is set to Pond.
The Liner level value is outside of the range defined in the Level / Plan Area / Perimeter Grid of the Pond node.
|
|
Advice
|
Check Level / Plan Area / Perimeter Grid and Liner levels.
|
|
|
|
E2038
|
Vegetation level is below liner level
|
Info
|
Node ID
|
|
Cause
|
Applicable to nodes whose Node type is set to Pond.
The Vegetation level value is below the Liner level of the Pond node.
|
|
Advice
|
Check Vegetation and Liner levels.
|
|
|
|
E2039
|
Highest pond storage level is above ground
|
Info
|
Node ID
|
|
Cause
|
Applicable to nodes whose Node type is set to Pond.
The highest Level value in the Level / Plan Area / Perimeter Grid > Ground level value of the Pond node.
|
|
Advice
|
Check pond level values and ground level value.
|
|
|
|
E2040
|
More than one subcatchment drains to this
pond
|
Info
|
Node ID
|
|
Cause
|
Applicable to nodes whose Node type is set Pond.
The pond node is the associated node ID for more than one subcatchment.
|
|
Advice
|
Check subcatchments are associated with the correct nodes.
|
|
|
|
E2046
|
No more than two overland links may be connected to this node
|
Info
|
Node ID
|
|
Cause
|
Applicable to nodes whose Node type is set to Manhole and Flood type is set to Inlet.
There are more than two links of System type set to Overland connected to the node identified.
|
|
Advice
|
Check connectivity of inlet node.
|
|
|
|
E2047
|
One or more overland links must be attached to this inlet node
|
Info
|
Node ID
|
|
Cause
|
Applicable to nodes whose Node type is set to Manhole and Flood type is set to Inlet for continuous and flow-efficiency inlets.
There are no links of System type set to Overland connected to the node identified.
|
|
Advice
|
Check connectivity of inlet node.
|
|
|
|
E2048
|
The highest storage level on an inlet cannot be equal to ground level
|
Info
|
Node ID
|
|
Cause
|
Applicable to nodes whose Node type is set to Manhole and whose Flood type is set to Inlet.
The highest Level value in the Storage Level / Plan Area grid is equal to the Ground Level value.
This is not allowed for inlet nodes, as storage type is assumed to be Lost in this case.
|
|
Advice
|
Add an extra Level entry in the Storage Level / Plan Area grid that is 1 mm above ground level.
|
|
|
|
E2050
|
Unconnected to outfall
|
Info
|
Conduit / Ancillary ID
|
|
Cause
|
The branch of the network that the link is connected in to does not lead to an Outfall Node.
|
|
Advice
|
Check the connectivity of the branch of the network containing the reported link.
|
|
|
|
E2051
|
Below attached node's lowest storage
level
|
Info
|
Conduit ID
|
|
Cause
|
Applicable to conduits linked to Nodes of type Storage.
Upstream/Downstream Invert Level of downstream/upstream link < lowest level in connected Storage Node Level / Plan Area grid.
|
|
Advice
|
Check invert levels of connected links and Storage Node Level values.
|
|
|
|
E2051
|
Not in flow efficiency table
|
Info
|
Node ID
|
|
Cause
|
Applicable to nodes whose node type is set to Manhole and whose Flood type is set to Inlet.
The Flow Efficiency Table associated with node has not been defined.
|
|
Advice
|
Define new Flow Efficiency Table, or select an existing table.
|
|
|
|
E2052
|
Below attached node's chamber floor level
|
Info
|
Node ID
|
|
Cause
|
Applicable to conduits linked to Nodes of type Manhole.
US/DS Invert level of conduit < Chamber floor level of connected node.
|
|
Advice
|
Check invert levels of connected links and Node levels.
|
|
|
|
E2053
|
This field must be expressed as a percentage
|
Info
|
Node ID
|
|
Cause
|
Applicable to nodes of whose Node type is set to Manhole and whose Flood type is set to Inlet.
% Clogging value is less than 0 or greater than 100.
|
|
Advice
|
Redefine % Clogging value as a percentage.
|
|
|
|
E2060
|
Less than width/2
|
Info
|
Conduit ID
|
|
Cause
|
Applicable to conduits whose Shape ID is set to UTOP, OU, ARCH, OEGB and CNET.
Cross Section Height (m) < 0.5 x Width (m).
|
|
Advice
|
Check Cross Section parameters of reported conduit.
|
|
|
|
E2061
|
Less than width
|
Info
|
Conduit ID
|
|
Cause
|
Applicable to conduits whose Shape ID is set to OVAL.
Cross Section Height (m) < Width (m).
|
|
Advice
|
Check Cross Section parameters of reported conduit
|
|
|
|
E2062
|
Less than width
|
Info
|
Conduit ID
|
|
Cause
|
Applicable to conduits whose Shape ID is set to EGG.
Cross Section Height (m) < Width (m).
|
|
Advice
|
Check Cross Section parameters of reported conduit.
|
|
|
|
E2063
|
Less than height/2
|
Info
|
Conduit ID
|
|
Cause
|
Applicable to conduits whose Shape ID is set to EGG.
Cross Section Width (m) < 0.5 x Height (m).
|
|
Advice
|
Check Cross Section parameters of reported conduit
|
|
|
|
E2064
|
Less than width
|
Info
|
Conduit ID
|
|
Cause
|
Applicable to conduits whose Shape ID is set to EGG2.
Cross Section Height (m) < Width (m).
|
|
Advice
|
Check Cross Section parameters of reported conduit.
|
|
|
|
E2065
|
Less than (height-width)/2
|
Info
|
Conduit ID
|
|
Cause
|
Applicable to conduits whose Shape ID is set to EGG2.
Cross Section Width < 0.5 x (Height - Width).
Where Height and Width are in m.
|
|
Advice
|
Check Cross Section parameters of reported conduit.
|
|
|
|
E2066
|
Less than width
|
Info
|
Conduit ID
|
|
Cause
|
Applicable to conduits whose Shape ID is set to OEGN.
Cross Section Height (m) < 0.5 x Width (m).
|
|
Advice
|
Check Cross Section parameters of reported conduit.
|
|
|
|
E2067
|
Less than (height-width/2)/2
|
Info
|
Conduit ID
|
|
Cause
|
Applicable to conduits whose Shape ID is set to OEGN.
0.5 x Width < Height - (0.5 x Width).
Where Height and Width are in m.
|
|
Advice
|
Check Cross Section parameters of reported conduit.
|
|
|
|
E2069
|
Less than height-(width/2)
|
Info
|
Conduit ID
|
|
Cause
|
Applicable to conduits whose Shape ID is set to CNET.
0.5 x Width < Height - (0.5 x Width)
Where Height and Width are in m.
|
|
Advice
|
Check Cross Section parameters of reported conduit.
|
|
|
|
E2070
|
Not in shape set
|
Info
|
Conduit ID
|
|
Cause
|
The shape specified in the Shape ID field of the conduit does not exist.
|
|
Advice
|
Define new Shape or select existing Shape.
|
|
|
|
E2072
|
Less than height - width/2
|
Info
|
Conduit ID
|
|
Cause
|
Applicable to conduits whose Shape ID is set to OEGB.
Width < Height - (0.5 x Width)
Where Height and Width are in m.
|
|
Advice
|
Check Cross Section parameters of reported conduit.
|
|
|
|
E2072
|
Fill Material Conductivity is required for
modelling Permeable Media solution-type conduits
|
Info
|
Conduit ID
|
|
Cause
|
Applicable to conduits whose Solution model is set to Permeable.
Fill material conductivity has not been defined.
|
|
Advice
|
Enter a value in the Fill material conductivity field.
|
|
|
|
E2073
|
The base flow depth exceeds the conduit
height. Check simulation parameters
|
Info
|
Conduit ID
|
|
Cause
|
|
Sediment Depth + minimum base flow depth >= Conduit Height
|
1
|
Where minimum base flow depth is the greater of:
|
(conduit height - sediment depth) x Base Flow Factor
Where:
Base Flow Factor is defined in Simulation Parameters
If Gradient > Slope Where Base Flow is Doubled (defined in Simulation Parameters), minimum base flow depth = Equation 2 x 2
|
2
|
and
|
Minimum Base Flow Depth (defined in Simulation Parameters)
|
3
|
|
|
Advice
|
Check Simulation Parameters are as expected.
|
|
|
|
E2073
|
Porosity is required for modelling
Permeable Media solution-type conduits
|
Info
|
Conduit ID
|
|
Cause
|
Applicable to conduits whose Solution model is set to Permeable.
Porosity has not been defined.
|
|
Advice
|
Enter a value in the Porosity field.
|
|
|
|
E2074
|
Hazen-Williams roughness can only be
used on ForceMain pipes
|
Info
|
Conduit ID
|
|
Cause
|
Roughness Type field of conduit is set to HW, but Solution model field is not set to ForceMain.
|
|
Advice
|
Check Solution model and Roughness type fields are as expected.
|
|
|
|
E2075
|
Normal or high headlosses are not allowed
for ForceMain Solution types
|
Info
|
Conduit ID
|
|
Cause
|
Solution Model field of conduit is set to ForceMain and Downstream headloss type or Upstream headloss type field is set to NORMAL or HIGH.
Headloss type must be set to FIXED or NONE when using the ForceMain solution model.
|
|
Advice
|
Check Solution Model and Headloss Type fields are as expected.
|
|
|
|
E2076
|
Below attached node's lowest storage level
|
Info
|
Flap Valve ID
|
|
Cause
|
Applicable to Flap Valves linked to Nodes of type Storage.
Upstream/Downstream Invert Level of downstream/upstream link < lowest level in connected Storage Node Level / Plan Area grid.
|
|
Advice
|
Check invert levels of connected links and Storage Node Level values.
|
|
|
|
E2076
|
Roughness value must be greater than zero
|
Info
|
Conduit ID
|
|
Cause
|
Top or Bottom Roughness value of conduit identified is less than zero.
|
|
Advice
|
Set roughness of conduit to value greater than zero.
|
|
|
|
E2077
|
Below attached node's chamber floor
|
Info
|
Flap Valve ID
|
|
Cause
|
Applicable to Flap Valve objects linked to Nodes of type Manhole.
Invert Level of Flap Valve < Chamber Floor Level of connected node
|
|
Advice
|
Check invert levels of connected links and Node Levels.
|
|
|
|
E2077
|
Springing height must be less than height
|
Info
|
Conduit ID
|
|
Cause
|
Conduit Shape ID is set to SPRUNGARCH and conduit Springing height is greater than conduit Height.
|
|
Advice
|
Check Springing height of conduit.
|
|
|
|
E2078
|
This 2D manhole/2D outfall is not contained within a
2D zone
|
Info
|
Node ID
|
|
Cause
|
2D node is not within a 2D Zone.
2D nodes are:
- Nodes whose Node type is set to Manhole and Flood type is set to 2D or Gully 2D
- Nodes whose Node typeis set to Outfall 2D
|
|
Advice
|
Add a 2D Zone that includes the 2D node within its boundary.
|
|
|
|
E2078
|
Height of arch above springing must be less than half of width
|
Info
|
Conduit ID
|
|
Cause
|
Conduit Shape ID is set to SPRUNGARCH and conduit Height - Springing height is greater than conduit Width/2.
|
|
Advice
|
Check Springing height of conduit.
|
|
|
|
E2079
|
This 2D manhole/2D outfall is not contained within a
2D zone mesh element
|
Info
|
Node ID
|
|
Cause
|
A 2D node is within a 2D Zone, but not within a mesh element.
2D nodes are:
- Nodes whose Node type is set to Manhole and Flood type is set to 2D or Gully 2D
- Nodes whose Node type is set to Outfall 2D
|
|
Advice
|
The 2D node may be within a void in the 2D mesh.
Check that the node location is as expected.
Check that the objects or file used to define voids are as expected.
|
|
|
|
E2080
|
FHWA is only valid as a US/DS headloss type if the US/DS node is a manhole
FHWA is only valid as a US or DS headloss type if the conduit is closed
FHWA is only valid if the solution model of the conduit is FULL
|
Info
|
Conduit ID
|
|
Cause
|
US/DS headloss type has been set to FHWA but the headloss type is not valid in the following conditions:
- connected node has Node type set to type other than Manhole
- conduit has Shape ID that defines an open pipe
- conduit has Solution model set to type other than Full
|
|
Advice
|
Select a suitable headloss type for the conduit.
|
|
|
|
E2082
|
2D node with Chamber floor level >= Ground level
|
Info
|
Node ID
|
|
Cause
|
The node has Flood type of Gully 2D or 2D and the value in the Chamber floor level field is greater than or equal to the value in the Ground level field.
This can cause simulation convergence problems if the level in the 2D zone in which the node is located is lower than the node's chamber floor.
|
|
Advice
|
Check the level parameters of the node.
|
|
|
| E2083 |
The minimum area including voids (Ag) is outside of the accepted range of 0 >= Ag <= W x L
|
Info
|
Node ID
|
|
Cause
|
The node has Inlet type of UPC Grate and the value in the Minimum area including voids field is greater than or equal to zero, or less than or equal to Grate width x Grate length. |
|
Advice
|
Review the Inlet parameter field values. |
|
|
| E2084 |
The area of voids (Ah) is greater than the minimum area including voids (Ag)
|
Info
|
Node ID
|
|
Cause
|
The node has Inlet type of UPC Grate and the value in the Area of voids field is greater than the value in the Minimum area including voids field. |
|
Advice
|
Review the Inlet parameter field values. |
|
|
| E2086 |
A value must be specified for this field when conduit headloss is FHWA
|
Info
|
Node ID
|
|
Cause
|
The Benching method field for the node has not been set and the conduit end that the node is connected to has headloss type set to FHWA.
|
|
Advice
|
Select a Benching method value for the node. |
|
|
|
E2087
|
Flood type is lost; chamber floor height should not be greater than ground level
|
Info
|
Node ID
|
|
Cause
|
The node has Flood type of Lost and the value in the Chamber floor level field is greater than the value in the Ground level field.
|
|
Advice
|
Check the level parameters of the node.
|
|
|
|
E2088
|
The weir behaviour depth is less than or equal to the curb opening height of <opening height value>
|
Info
|
Node ID
|
|
Cause
|
Applicable to nodes with Flood type of Inlet or Inlet 2D and Inlet type of SagC or SagCO.
The Weir behaviour depth field is not greater than the value in the Opening height field.
|
|
Advice
|
Set the Weir behaviour depth to a value greater than the Opening height.
|
|
|
|
E2089
|
Node of type 'Connect 2D' and connection type '2D' must be inside a 2D zone's boundary
|
Info
|
Node
|
|
Cause
|
A Connect 2D type of node with a connection type of 2D is not located within a 2D zone.
|
|
Advice
|
Either move the node so that it is located within a 2D zone or change the type of node in the Node type field or the type of connection in the Connection type field.
|
|
|
|
E2090
|
Node of type 'Connect 2D' and connection type 'Break' must be connected to exactly 2 conduits of type 'Conduit 2D' or 'Linear Drainage 2D'
|
Info
|
Node
|
|
Cause
|
A Break type of Connect 2D node is not currently connected to two conduits which are of the type Conduit (2D) or Linear Drainage (2D).
|
|
Advice
|
Ensure that the Connect 2D node of type Break is connected to two conduits (one at either end) of the type Conduit (2D) or Linear Drainage (2D), or change the type of connection node in the Connection type field, or the type of conduit in the Conduit type field.
|
|
|
|
E2091
|
Node of type 'Connect 2D' can only be connected to conduits of type 'Conduit 2D' or 'Linear Drainage 2D'
|
Info
|
Node (Connectivity)
|
|
Cause
|
A Connect 2D node is not currently connected to a conduit which is of the type Conduit (2D) or Linear Drainage (2D).
|
|
Advice
|
Ensure that the Connect 2D node is connected to a conduit of the type Conduit (2D) or Linear Drainage (2D), or change the type of connection node in the Connection type field, or the type of conduit in the Conduit type field.
|
|
|
|
E2092
|
Linked by 2D conduits(s) to node <node id> which is connected to a different 2D zone
|
Info
|
Node ID
|
|
Cause
|
Either a single conduit of type Conduit (2D) or Linear Drainage (2D), or a chain of them, is connected (at either end) to 2 different Connect 2D nodes of connection type 2D, which are located in different 2D zones.
Note that this message is displayed for each node at either end of the conduit or chain of conduits.
|
|
Advice
|
A single Conduit (2D) or Linear Drainage (2D) type of conduit or a chain must be connected to nodes that are located in the same 2D zone. Therefore, move the applicable nodes so that they are located within the same 2D zone.
|
|
|
|
E2093
|
Linked by 2D conduits(s) to conduit <conduit id> which is connected to a different 2D zone
|
Info
|
Node
|
|
Cause
|
Two or more conduits of the type Linear Drainage (2D), which are connected to Connect 2D nodes with the connection type 2D, are located in different 2D zones.
|
|
Advice
|
Move the conduit(s), and any associated Connect 2D nodes of the type 2D, if applicable, so that they are located within the same 2D zone.
|
|
|
|
E2094
|
Must be either CIRC or RECT for conduit types 'Conduit (2D)' or 'Linear Drainage (2D)'
|
Info
|
Conduit
|
|
Cause
|
The Shape ID field is not set to either CIRC or RECT. Conduits with their Conduit type set to Conduit 2D or Linear Drainage 2D must have a Shape ID set to either CIRC or RECT.
|
|
Advice
|
Either change the Shape ID field to either CIRC or RECT, or change the Conduit type field to Conduit.
|
|
|
|
E2095
|
Must be N (Manning's n) for conduit types 'Conduit (2D)' or 'Linear Drainage (2D)'
|
Info
|
Conduit (Top/Bottom roughness)
|
|
Cause
|
The Roughness type field is not set to N (Manning's n). Conduits with their Conduit type set to Conduit 2D or Linear Drainage 2D must have the Roughness type field is set to N (Manning's n).
|
|
Advice
|
Either change the Roughness type field to N (Manning's n) or change the Conduit type field to Conduit.
|
|
|
|
E2096
|
Top and bottom roughness be Manning's n values must be the equal for conduit types 'Conduit (2D)' or 'Linear Drainage (2D)'
|
Info
|
Conduit (Roughness type)
|
|
Cause
|
The Roughness type field is set to N (Manning's n) and the Conduit type is set to either Conduit 2D or Linear Drainage 2D. But the different values have been specified for the Top roughness and Bottom roughness fields; these should be the same.
|
|
Advice
|
Either specify the same value for the Top roughness and Bottom roughness fields, or change the Conduit type field to Conduit.
|
|
|
|
E2097
|
Slot width must not exceed conduit width
|
Info
|
Conduit
|
|
Cause
|
The specified width for the slot is greater than the width specified for the conduit.
|
|
Advice
|
Either change the value specified in the Slot width field so that it is smaller than width for the conduit (specified in the Width field), or increase the value in the conduit Width field.
|
|
|
|
E2098
|
Conduit of type 'Linear drainage (2D)' must be fully inside a single 2D zone's boundary
|
Info
|
Conduit ID
|
|
Cause
|
One or more conduits of type of Linear drainage (2D) are not located with the same 2D zone.
|
|
Advice
|
Ensure that a single Linear drainage (2D) type of conduit, or all the conduits which comprise a chain of them, are located within the same 2D zone boundary. Move the applicable conduit(s) if necessary.
|
|
|
|
E2099
|
Conduit of type '<conduit type>' must be connected to at least one node of type 'Connect 2D'
|
Info
|
Conduit ID
|
|
Cause
|
A conduit of type Linear drainage (2D) or Conduit 2D is not connected to a node of type Connect 2D but it must be connected to at least one node of that type.
|
|
Advice
|
Ensure that the node selected in the conduit's US Node ID or DS Node ID field is a Connect 2D type of node.
|
|
|
|
E2100
|
Linked by 2D conduits(s) to conduit <conduit id> which is connected to a different 2D zone
|
Info
|
Conduit ID
|
|
Cause
|
Two or more conduits of the type Linear Drainage (2D) are located in different 2D zones.
|
|
Advice
|
Move the conduit(s), and any associated Connect 2D nodes of the type 2D if applicable, so that they are located within the same 2D zone.
|
|
|
|
E2101
|
Less than minimum flow
|
Info
|
Orifice ID
|
|
Cause
|
Applicable to VLDorf link types.
Maximum flow < Minimum Flow.
|
|
Advice
|
Check the Regulator parameters of the reported VLDorf object.
|
|
|
|
E2101
|
Below attached node's lowest storage level
|
Info
|
Orifice ID
|
|
Cause
|
Applicable to Orifice objects linked to Nodes of type Storage.
Invert Level of orifice < lowest level in connected Storage Node Level / Plan Area grid.
|
|
Advice
|
Check invert levels of orifice and Storage Node Level values.
|
|
|
|
E2102
|
Below attached node's chamber floor
|
Info
|
Orifice ID
|
|
Cause
|
Applicable to Orifice objects linked to Nodes of type Manhole.
Invert Level of Orifice < Chamber Floor Level of connected node.
|
|
Advice
|
Check invert levels of connected links and Node Levels.
|
|
|
|
E2103
|
No Bridge inlet/outlet exists with ID <inlet/outlet ID>
|
Info
|
Bridge Opening ID
|
|
Cause
|
An ID has been entered in the Inlet ID / Outlet ID field of the bridge opening, but a bridge inlet/outlet of that name does not exist in the network.
|
|
Advice
|
Review Inlet ID / Outlet ID values.
|
|
|
|
E2104
|
Cannot specify both an Inlet ID and an Inlet Blockage ID
|
Info
|
Bridge Opening - Inlet ID
|
|
Cause
|
An ID has been specified for the Inlet ID and Inlet Blockage ID fields of the bridge opening, but you can only specify one or the other; not both at the same time.
|
|
Advice
|
Select an Inlet ID or an Inlet Blockage ID.
|
|
|
|
E2105
|
Not linked to either Connect 2D node of connection type '2D' or, via a chain of conduits, to a conduit of type 'Linear Drainage (2D)'
|
Info
|
Conduit
|
|
Cause
|
A conduit of type Conduit (2D) is not currently connected to either a Connect 2D node of connection type 2D, or via a chain of conduits to a conduit type of Linear Drainage (2D).
|
|
Advice
|
Check the connections for this conduit or change it's Connection type.
|
|
|
|
E2106
|
The Min space step field cannot exceed the Max space step field defined for the network’s simulation parameters
|
Info
|
Conduit
|
|
Cause
|
The Max space step field specified for this network's simulation parameters is smaller than the Min space step defined for this Conduit 2D type of conduit.
|
|
Advice
|
Change the Min space step for the conduit so that it is smaller than the Max space step set in the simulation parameters. Alternatively, increase the Max space step set in the simulation parameters but this may affect the results for other objects in the network when a simulation is run.
|
|
|
|
E2107
|
Linked by 2D conduits(s) to node <node id> which is connected to a different 2D zone
|
Info
|
Conduit
|
|
Cause
|
Two or more conduits of the type Linear Drainage (2D) are connected to Connect 2D nodes of type 2D which are located in different 2D zones.
|
|
Advice
|
Move the Connect 2D nodes of the type 2D, and any associated Linear Drainage (2D) conduits, if applicable, so that they are located within the same 2D zone.
|
|
|
|
E2108
|
Not linked to a Connect 2D node of connection type '2D'
|
Info
|
Conduit
|
|
Cause
|
A single conduit of type Conduit (2D) is not currently connected to a Connect 2D node of connection type 2D.
|
|
Advice
|
If the conduit is connected to a Connect 2D node then ensure that the Connection type for the node is set to 2D. Otherwise, set the Node type to Connect 2D node and the Connection type to 2D.
|
|
|
|
E2126
|
Not in head discharge table
|
Info
|
Pump ID
|
|
Cause
|
Applicable to pumps of Link type ScrPmp and RotPmp.
Head Discharge object selected in the Head Discharge Table field of the Pump object has not been defined.
|
|
Advice
|
Define new Head Discharge Table or select an existing table.
|
|
|
|
E2126
|
Minimum speed > Nominal Speed > Maximum Speed
|
Info
|
Pump ID
|
|
Cause
|
Applicable to pumps of Link type VfdPmp
This error message may be displayed for the following reasons:
- Minimum Speed is greater than Maximum Speed
- Nominal Speed is less than Minimum Speed
- Nominal Speed is greater than Maximum Speed
Where:
Nominal Speed is defined in the Head Discharge table accessed from the Pump Definition page of the Pump property sheet.
Minimum Speed and Maximum Speed are defined on the Regulator page of the Pump property sheet.
|
|
Advice
|
Review speed values for the pump.
|
|
|
|
E2127
|
Less than minimum flow
|
Info
|
Pump ID
|
|
Cause
|
Applicable to VspPmp link types.
Maximum flow < Minimum Flow.
|
|
Advice
|
Check the Regulator parameters of the reported VspPmp object.
|
|
|
|
E2127
|
Springing height must be less than height
|
Info
|
Bridge Opening ID
|
|
Cause
|
Bridge Opening Shape ID is set to SPRUNGARCH and opening Springing height is greater than opening Height.
|
|
Advice
|
Check Springing height of opening
|
|
|
|
E2128
|
Less than switch off level
|
Info
|
Pump ID
|
|
Cause
|
Switch on level < Switch off level.
|
|
Advice
|
Check the Pump Definition fields of the reported Pump object.
|
|
|
|
E2128
|
Height of arch above springing must be less than half of width
|
Info
|
Bridge Opening ID
|
|
Cause
|
Bridge Opening Shape ID is set to SPRUNGARCH and opening Height - Springing height is greater than opening Width/2.
|
|
Advice
|
Check Springing height of opening.
|
|
|
|
E2151
|
Less than minimum opening
|
Info
|
Sluice ID
|
|
Cause
|
Applicable to VSGate objects.
Regulator parameter Maximum Opening < Minimum Opening.
|
|
Advice
|
Check the Regulator Parameters fields of the VSGate object.
|
|
|
|
E2151
|
Below attached node's lowest storage level
|
Info
|
Sluice ID
|
|
Cause
|
Applicable to Sluice objects linked to Nodes of type Storage.
Invert Level of Sluice < lowest level in connected Storage Node Level / Plan Area grid.
|
|
Advice
|
Check Sluice invert level and Storage Node Level values.
|
|
|
|
E2152
|
Below attached node's chamber floor
|
Info
|
Sluice ID
|
|
Cause
|
Applicable to Sluice objects linked to Nodes of type Manhole.
Invert Level of Sluice < Chamber Floor Level of connected node
|
|
Advice
|
Check invert levels of connected links and Node Levels.
|
|
|
| E2153 |
Must be greater than Depth threshold 1
|
Info
|
Roughness definition
|
|
Cause
|
The value specified for Depth threshold 2 is less than the value specified for Depth threshold 1 but it must be greater.
|
|
Advice
|
Check the Depth threshold 1 and Depth threshold 2 values for the relevant Roughness definition object, and ensure that the value specified for Depth threshold 2 is greater than the value specified for Depth threshold 1.
|
|
|
|
E2176
|
Not in head discharge table
|
Info
|
User Control ID
|
|
Cause
|
Head Discharge object selected in the Head Discharge Table field of the User Control object has not been defined.
|
|
Advice
|
Define new Head Discharge Table or select an existing table.
|
|
|
|
E2176
|
Below attached node's lowest storage level
|
Info
|
User Control ID
|
|
Cause
|
Applicable to User Control objects linked to Nodes of type Storage.
Invert Level of User Control < lowest level in connected Storage Node Level / Plan Area grid.
|
|
Advice
|
Check invert levels of connected links and Storage Node Level values.
|
|
|
|
E2177
|
Below attached node's chamber floor
|
Info
|
User Control ID
|
|
Cause
|
Applicable to User Control objects linked to Nodes of type Manhole.
Invert Level of User Control < Chamber Floor Level of connected node.
|
|
Advice
|
Check invert levels of connected links and Node Levels.
|
|
|
| E2177 |
TVD connector specified for input does not exist
|
Info
|
TVD Connector ID
|
|
Cause
|
The TVD connector specified in one of the Input fields does not exist in the network.
|
|
Advice
|
Review the TVD ID entered in the Input field.
If the ID refers to a TSDB data stream, prefix the ID with a '#'.
|
|
|
|
E2180
|
Connected object not found in network
|
Info
|
TVD Connector ID
|
|
Cause
|
Applicable to TVD Connectors.
Displayed if the Connected object id does not correspond with the ID of a network object of type specified in the Connected object type field.
Displayed if Connected object type is set to hw_rtc and the specified Connected object id does not correspond to an RTC table ID. (When referencing RTC tables, the reference should take the form RegulatorID.TableName for tables defined in regulators in the RTC, or TableName for tables defined in the Global section of the RTC.)
|
|
Advice
|
Review the Connected object type and Connected object id fields.
|
|
|
| E2182 |
Input attribute is invalid or has wrong units
|
Info
|
TVD Connector ID
|
|
Cause
|
The Connection usage field is set to Input and the value in the Input attribute field does not have the same units as the Output units type specified.
|
|
Advice
|
Review the Input attribute and Output units type fields.
|
|
|
| E2183 |
Result attribute is invalid or has wrong units
|
Info
|
TVD Connector ID
|
|
Cause
|
The Connection usage field is set to Comparison and the value in the Comparison result field does not have the same units as the Output units type specified. |
|
Advice
|
Review the Comparison result and Output units type fields. |
|
|
| E2183 |
Object type and result type attribute not allowed for ARAM output
|
Info
|
TVD Connector ID
|
|
Cause
|
The selected Connected object type and the selected Comparison result are not a valid combination for ARMA post-processing. |
|
Advice
|
Review the selection of the Connected object type and the Comparison result fields. The permitted combinations are listed in the TVD Connector Data Fields topic. |
|
|
| E2184 |
TVD connectors require at least one input
|
Info
|
TVD Connector ID
|
|
Cause
|
There are no values defined in any of the input fields.
|
|
Advice
|
Specify an Input (either TVD connector ID or data stream).
|
|
|
| E2187 |
There can be at most one TVD connector with output units of evaporation or temperature
|
Info
|
TVD Connector ID
|
|
Cause
|
More than one TVD connector has Output units type set to EV -evaporation or CF - temperature.
|
|
Advice
|
Currently only one evaporation or temperature profile can be applied to the network using TVD connectors.
|
|
|
| E2188 |
Invalid connector unit for output unit type
|
Info
|
TVD Connector ID
|
|
Cause
|
The type of unit selected in the Connector units field cannot be used with the unit type selected in the Output unit type field.
|
|
Advice
|
Change the item currently selected in either the Connector units or the Output unit type field.
|
|
|
| E2190 |
ARMA model not defined
|
Info
|
ARMA ID
|
|
Cause
|
The name of the specified ARMA model either does not exist or is not fully defined.
|
|
Advice
|
Check that all the data fields for the ARMA model have been specified. Note that the Autoregressive and Moving average parameters can only be specified via the ARMA Property Sheet.
|
|
|
|
E2199
|
Must be FHWA. US/DS node <node id> is DS/US node of conduit <conduit id> which has DS/US headloss type FHWA
|
Info
|
Node ID, Conduit ID
|
|
Cause
|
The end of a conduit with headloss type that is not FHWA is connected to the end of another conduit with headloss type FHWA.
If one conduit has headloss type FHWA at an end connected to a manhole, all the pipes connected to that manhole must have FHWA headloss at the end connected to the manhole.
|
|
Advice
|
Review the headloss type fields of connected pipes.
|
|
|
|
E2201
|
Less than minimum value
|
Info
|
Weir ID
|
|
Cause
|
Applicable to VCWeir and VWWeir objects.
Regulator parameter Maximum Value < Minimum Value.
|
|
Advice
|
Check the Regulator Parameters fields of the Weir object.
|
|
|
|
E2202
|
The total weir width is insufficient
to accommodate the notch(es)
|
Info
|
Weir ID
|
|
Cause
|
Applicable to TRWeir objects.
Notch Width x Number of Notches < Width.
|
|
Advice
|
Check the Weir Definition fields of the TRWeir object.
|
|
|
|
E2202
|
Below attached node's chamber floor
|
Info
|
Weir ID
|
|
Cause
|
Applicable to Weir objects linked to Nodes of type Manhole.
Invert Level of Weir < Chamber Floor Level of connected node.
|
|
Advice
|
Check invert levels of connected links and Node Levels.
|
|
|
|
E2203
|
The notch width is too narrow
|
Info
|
Weir ID
|
|
Cause
|
Applicable to TRWeir objects.
Notch Width < 0.5 x Notch Height.
|
|
Advice
|
Check the Weir Definition fields of the TRWeir object.
|
|
|
|
E2204
|
The total weir width is insufficient
to accommodate the notch(es)
|
Info
|
Weir ID
|
|
Cause
|
Applicable to VNWeir objects.
Notch Height x 2 x tan(Notch Angle/2) x No. of Notches > Weir Width.
|
|
Advice
|
Check the Weir Definition fields of the VNWeir object.
|
|
|
|
E2205
|
Boundary of 2D zone has changed since
meshing was performed
|
Info
|
2D Zone ID
|
|
Cause
|
The 2D Zone boundary was edited after the current 2D mesh was created.
|
|
Advice
|
Re-mesh the 2D Zone using the current polygon boundary.
|
|
|
|
E2206
|
Maximum triangle area has changed since
meshing was performed
|
Info
|
2D Zone ID
|
|
Cause
|
The value in the Maximum Triangle Area field of the 2D Zone is different to the area value used to create the current mesh.
|
|
Advice
|
Either reset the Maximum Triangle Area of the 2D Zone to the value used when the current mesh was created, or re-mesh the 2D Zone using the current Maximum Triangle Area value.
|
|
|
|
E2207
|
Minimum angle has changed since meshing
was performed
|
Info
|
2D Zone ID
|
|
Cause
|
The value in the Minimum Angle field of the 2D Zone is different to the minimum angle value used to create the current mesh.
|
|
Advice
|
Either reset the Minimum Angle of the 2D Zone to the value used when the current mesh was created, or re-mesh the 2D Zone using the current Minimum Angle value.
|
|
|
|
E2208
|
Mesh zone <mesh zone id> has been
deleted/renamed since meshing was performed
|
Info
|
2D Zone ID, Mesh Zone ID
|
|
Cause
|
The Mesh Zone identified was used to create the current mesh in the 2D Zone, but no longer exists.
This error may be caused as a result of renaming of the Mesh Zone.
|
|
Advice
|
Re-mesh the 2D Zone using the current set of mesh zones.
Alternatively, if the Mesh Zone was renamed, reset the Mesh Zone ID to the value used when the 2D mesh was created.
|
|
|
|
E2209
|
Mesh zone <mesh zone id> has had its
maximum triangle area changed since meshing was performed
|
Info
|
2D Zone ID, Mesh Zone ID
|
|
Cause
|
The value in the Maximum Triangle Area field of the Mesh Zone is different to the area used when creating the current mesh in the 2D Zone.
|
|
Advice
|
Either reset the Maximum Triangle Area of the Mesh Zone to the value used when the 2D mesh was created, or re-mesh the 2D Zone using the current Mesh Zone Maximum Triangle Area value.
|
|
|
|
E2210
|
Mesh zone <mesh zone id> has had its
boundary changed since meshing was performed
|
Info
|
2D Zone ID, Mesh Zone ID
|
|
Cause
|
The boundary of a Mesh Zone used to create the 2D Zone mesh was edited after the 2D mesh was created.
|
|
Advice
|
Re-mesh the 2D Zone using the current Mesh Zone boundary.
|
|
|
|
E2211
|
Roughness zone <roughness zone id>
has been deleted/renamed since meshing was performed
|
Info
|
2D Zone ID, Roughness Zone ID
|
|
Cause
|
The Roughness Zone identified was used to create the current mesh in the 2D Zone, but no longer exists.
This error may be caused as a result of renaming of the Roughness Zone.
|
|
Advice
|
Re-mesh the 2D Zone using the current set of Roughness Zones.
Alternatively, if the Roughness Zone was renamed, reset the Roughness Zone ID to the value used when the 2D mesh was created.
|
|
|
|
E2212
|
Roughness zone <roughness zone id>
has had its boundary changed since meshing was performed
|
Info
|
2D Zone ID, Roughness Zone ID
|
|
Cause
|
The boundary of a Roughness Zone used to create the 2D Zone mesh was edited after the 2D mesh was created.
|
|
Advice
|
Re-mesh the 2D Zone using the current Roughness Zone boundary.
|
|
|
|
E2213
|
Polygons belonging to voids category
<category id> have changed since meshing was performed
|
Info
|
2D Zone ID, Polygon Category ID
|
|
Cause
|
The boundary of a Polygon object(s) belonging to the Polygons Category used to identify voids at the time of creating the current 2D mesh, was edited after the mesh was created.
This includes edits to polygons in the voids category that do not intersect the 2D Zone.
(Where voids have been derived from a file or layer, changes to the file or layer are not validated.)
|
|
Advice
|
Re-mesh the 2D Zone using the current Polygon set.
|
|
|
|
E2214
|
Lines belonging to break lines category
<category id> have changed since meshing was performed
|
Info
|
2D Zone ID, Line Category ID
|
|
Cause
|
The geometry of a Line(s) belonging to the Line Category used to identify Break Lines at the time of creating the current 2D mesh, was edited after the mesh was created.
This includes edits to Lines in the Break Lines category that do not intersect the 2D Zone.
(Where Break Lines have been derived from a file or layer, changes to the file or layer are not validated.)
|
|
Advice
|
Re-mesh the 2D Zone using the current Line set.
|
|
|
|
E2215
|
Lines belonging to walls category
<category id> have changed since meshing was performed
|
Info
|
2D Zone ID, Line Category ID
|
|
Cause
|
The geometry of a Line(s) belonging to the Line Category used to identify Walls at the time of creating the current 2D mesh, was edited after the mesh was created.
This includes edits to Lines in the Walls category that do not intersect the 2D Zone.
(Where Walls have been derived from a file or layer, changes to the file or layer are not validated.)
|
|
Advice
|
Re-mesh the 2D Zone using the current Line set.
|
|
|
|
E2216
|
Mesh zone <mesh zone id> has been
added since meshing was performed
|
Info
|
2D Zone ID, Mesh Zone ID
|
|
Cause
|
The Mesh Zone identified has a Maximum Triangle Area defined and intersects a 2D Zone that has been meshed, but was not used to create the current mesh in the 2D Zone.
This error may be caused by renaming of the Mesh Zone.
|
|
Advice
|
Re-mesh the 2D Zone using the current set of mesh zones.
Alternatively, if the Mesh Zone was renamed, reset the Mesh Zone ID to the value used when the 2D mesh was created.
|
|
|
|
E2217
|
Roughness zone <roughness zone id> has been
added since meshing was performed
|
Info
|
2D Zone ID, Roughness Zone ID
|
|
Cause
|
The Roughness Zone identified has a Roughness defined and intersects a 2D Zone that has been meshed, but was not used to create the current mesh in the 2D Zone.
This error may be caused by renaming of the Roughness Zone.
|
|
Advice
|
Re-mesh the 2D Zone using the current set of roughness zones.
Alternatively, if the Roughness Zone was renamed, reset the Roughness Zone ID to the value used when the 2D mesh was created.
|
|
|
|
E2223
|
Infiltration zone (2D) <infiltration zone id>
has been deleted/renamed since meshing was performed
|
Info
|
2D Zone ID, Infiltration Zone ID
|
|
Cause
|
The Infiltration Zone identified was used to create the current mesh in the 2D Zone, but no longer exists.
This error may be caused as a result of renaming of the Infiltration Zone.
|
|
Advice
|
Re-mesh the 2D Zone using the current set of Infiltration Zones.
Alternatively, if the Infiltration Zone was renamed, reset the Infiltration Zone ID to the value used when the 2D mesh was created.
|
|
|
|
E2224
|
Infiltration zone (2D) <infiltration zone id>
has had its boundary changed since meshing was performed
|
Info
|
2D Zone ID, Infiltration Zone ID
|
|
Cause
|
The boundary of an Infiltration Zone used to create the 2D Zone mesh was edited after the 2D mesh was created.
|
|
Advice
|
Re-mesh the 2D Zone using the current Infiltration Zone boundary.
|
|
|
|
E2225
|
Infiltration zone (2D) <infiltration zone id> has been
added since meshing was performed
|
Info
|
2D Zone ID, Infiltration Zone ID
|
|
Cause
|
The Infiltration Zone identified intersects a 2D Zone that has been meshed, but was not used to create the current mesh in the 2D Zone.
This error may be caused by renaming of the Infiltration Zone.
|
|
Advice
|
Re-mesh the 2D Zone using the current set of infiltration zones.
Alternatively, if the Infiltration Zone was renamed, reset the Infiltration Zone ID to the value used when the 2D mesh was created.
|
|
|
|
E2226
|
Infiltration Zone <infiltration zone
id> has had its exclude from 2d meshing flag changed since meshing was
performed
|
Info
|
2D Zone ID, Infiltration Zone ID
|
|
Cause
|
The setting of the Exclude from 2D meshing option of the Infiltration Zone identified has been changed since the current mesh in the 2D Zone was created.
|
|
Advice
|
Re-mesh the 2D Zone using the current infiltration zone settings.
Alternatively, reset the Exclude from 2D meshing option to the value used when the 2D mesh was created.
|
|
|
|
E2228
|
Element <element id>: Less than previous value
|
Info
|
Shape ID
|
|
Cause
|
Applicable to shape objects with the Normalised option checked.
Height values in the Shape geometry editor should be in ascending order. The height value in the entry identified is less than the height value in the previous entry.
|
|
Advice
|
Review the entries in the Shape geometry editor.
|
|
|
|
E2230
|
Mesh has not been created for 2D
zone
|
Info
|
2D Zone ID
|
|
Cause
|
A 2D mesh has not been generated for the 2D Zone.
|
|
Advice
|
Generate a mesh for the 2D Zone.
|
|
|
|
E2231
|
Width must be > 0 for 0 < height
<1
|
Info
|
Shape ID
|
|
Cause
|
Applicable to normalised symmetric user defined shapes:
This message will be displayed if in the Shape Geometry Editor a Width <= 0 is entered against a Height value > 0 or < 1
|
|
Advice
|
Check the values entered in the Shape Geometry Editor.
|
|
|
|
E2232
|
Roughness Zone <roughness zone
id> has had its exclude from 2d meshing flag changed since meshing was
performed
|
Info
|
2D Zone ID, Roughness Zone ID
|
|
Cause
|
The setting of the Exclude from 2D meshing option of the Roughness Zone identified has been changed since the current mesh in the 2D Zone was created.
|
|
Advice
|
Re-mesh the 2D Zone using the current roughness zone settings.
Alternatively, reset the Exclude from 2D meshing option to the value used when the 2D mesh was created.
|
|
|
|
E2233
|
Less than lhs
|
Info
|
Shape ID
|
|
Cause
|
Applicable to asymmetric user defined shapes:
This message will be displayed if in the Shape Description Grid a Right value < the corresponding Left value.
|
|
Advice
|
Check the values entered in the Shape Description Grid.
|
|
|
|
E2234
|
Width must be > 0 for 0 < height
< 1
|
Info
|
Shape ID
|
|
Cause
|
Applicable to asymmetric user defined shapes:
This message will be displayed if in the Shape Description Grid a Left or Right value = 0 is entered against a Height value > 0 or < 1
|
|
Advice
|
Check the values entered in the Shape Description Grid.
|
|
|
|
E2235
|
Porous Wall <porous wall id> has
been deleted/renamed since meshing was performed
|
Info
|
2D Zone ID, Porous Wall ID
|
|
Cause
|
The Porous Wall identified was used to create the current mesh in the 2D Zone, but no longer exists.
This error may be caused as a result of renaming of the Porous Wall.
|
|
Advice
|
Re-mesh the 2D Zone using the current set of Porous Walls.
Alternatively, if the Porous Wall was renamed, reset the Porous Wall ID to the value used when the 2D mesh was created.
|
|
|
|
E2236
|
Porous Wall <porous wall id> has had
its boundary changed since meshing was performed
|
Info
|
2D Zone ID, Porous Wall ID
|
|
Cause
|
The Porous Wall identified intersects a 2D Zone that has been meshed, but was not used to create the current mesh in the 2D Zone.
This error may be caused by renaming of the Porous Wall.
|
|
Advice
|
Re-mesh the 2D Zone using the current set of porous walls.
Alternatively, if the Porous Wall was renamed, reset the Porous Wall ID to the value used when the 2D mesh was created.
|
|
|
|
E2237
|
Porous Wall <porous wall id> has
been added since meshing was performed
|
Info
|
2D Zone ID, Porous Wall ID
|
|
Cause
|
The Porous Wall identified intersects a 2D Zone that has been meshed, but was not used to create the current mesh in the 2D Zone.
This error may be caused by renaming of the Porous Wall.
|
|
Advice
|
Re-mesh the 2D Zone using the current set of porous walls.
Alternatively, if the Porous Wall was renamed, reset the Porous Wall ID to the value used when the 2D mesh was created.
|
|
|
|
E2238
|
2D IC zone <2D IC Zone ID> has
been deleted/renamed since meshing was performed
|
Info
|
2D Zone ID, 2D IC Zone ID
|
|
Cause
|
The 2D IC Zone identified was used to create the current mesh in the 2D Zone, but no longer exists.
This error may be caused as a result of renaming of the 2D IC Zone.
|
|
Advice
|
Re-mesh the 2D Zone using the current set of 2D IC Zones.
Alternatively, if the 2D IC Zone was renamed, reset the 2D IC Zone ID to the value used when the 2D mesh was created.
|
|
|
|
E2239
|
2D IC zone <2D IC Zone ID> has
had its boundary changed since meshing was performed
|
Info
|
2D Zone ID, 2D IC Zone ID
|
|
Cause
|
The boundary of a 2D IC Zone used to create the 2D Zone mesh was edited after the 2D mesh was created.
|
|
Advice
|
Re-mesh the 2D Zone using the current 2D IC Zone boundary.
|
|
|
|
E2240
|
2D IC zone <2D IC Zone ID> has
been added since meshing was performed
|
Info
|
2D Zone ID, 2D IC Zone ID
|
|
Cause
|
The 2D IC Zone identified intersects a 2D Zone that has been meshed, but was not used to create the current mesh in the 2D Zone.
This error may be caused by renaming of the 2D IC Zone.
|
|
Advice
|
Re-mesh the 2D Zone using the current set of 2D IC Zones.
Alternatively, if the 2D IC Zone was renamed, reset the 2D IC Zone ID to the value used when the 2D mesh was created.
|
|
|
|
E2241
|
Must enter a value for either maximum crest or maximum width
|
Info
|
Weirs
|
|
Cause
|
The type of weir is specified either as a Variable Crest Weir (VCWEIR) or a variable width weir (VWWEIR) but a maximum elevation has not been set in either the Maximum crest or the Maximum width fields.
|
|
Advice
|
Ensure that the maximum elevation is set in the Maximum crest field for a VCWEIR or in the Maximum width field for a VWWEIR or a VCWEIR (if the Maximum crest is not set for a VCWEIR, the specified Maximum width will be used instead).
|
|
|
|
E2242
|
Must enter a value for either minimum crest or minimum width
|
Info
|
Weirs
|
|
Cause
|
The type of weir is specified either as a Variable Crest Weir (VCWEIR) or a variable width weir (VWWEIR) but a minimum elevation has not been set in either the Minimum crest or the Minimum width fields.
|
|
Advice
|
Ensure that the minimum elevation is set in the Minimum crest field for a VCWEIR or in the Minimum width field for a VWWEIR or a VCWEIR (if the Minimum crest is not set for a VCWEIR, the specified Minimum width will be used instead).
|
|
|
|
E2246
|
<Field name> Exceeds gate height value / Exceeds maximum opening value
|
Info
|
Weirs
|
|
Cause
|
The type of weir is specified as a Gated Weir (GTWEIR) but the values specified in the Minimum opening, Maximum opening and/or Initial opening fields are greater than the value specified for the Gate height, and/or the value specified in the Minimum opening field is greater than the value for specified for the Maximum opening field.
|
|
Advice
|
Ensure that the values specified for the Minimum opening, Maximum opening and/or Initial opening fields are less than the specified Gate height, and/or the value specified for the Minimum opening field is less than the specified Maximum opening.
|
|
|
|
E2249
|
Porous Polygon <Porous Polygon ID> has been deleted/renamed since meshing was performed
|
Info
|
2D Zone ID, Porous Polygon ID
|
|
Cause
|
The Porous Polygon identified was used to create the current mesh in the 2D Zone, but no longer exists.
This error may be caused as a result of renaming of the Porous Polygon.
|
|
Advice
|
Re-mesh the 2D Zone using the current set of Porous Polygons.
Alternatively, if the Porous Polygon was renamed, reset the Porous Polygon ID to the value used when the 2D mesh was created.
|
|
|
|
E2250
|
Porous Polygon <Porous Polygon ID> has had its boundary changed since meshing was performed
|
Info
|
2D Zone ID, Porous Polygon ID
|
|
Cause
|
The boundary of a Porous Polygon used to create the 2D Zone mesh was edited after the 2D mesh was created.
|
|
Advice
|
Re-mesh the 2D Zone using the current Porous Polygon boundary.
|
|
|
|
E2251
|
Table must contain at least two entries
|
Info
|
Head Discharge ID
|
|
Cause
|
Head / Discharge Grid of the Head Discharge contains < 2 rows.
|
|
Advice
|
Check the Head / Discharge Grid entries of the reported Head Discharge
|
|
|
|
E2252
|
First value must be 0
|
Info
|
Head Discharge ID
|
|
Cause
|
The first value in the Head column of the Head / Discharge Grid of the Head Discharge is not equal to 0.
|
|
Advice
|
Check the Head / Discharge Grid entries of the reported Head Discharge.
|
|
|
|
E2253
|
Less than previous value
|
Info
|
Head Discharge ID
|
|
Cause
|
Applicable to objects with associated Head Discharge curves except for pumps of Link Type = ROTPMP:
Head values in the Head / Discharge Grid are in descending order i.e. type = Head descending (ROTPMP).
|
|
Advice
|
Check that the correct Head / Discharge Grid is associated with the object. Change Head / Discharge Grid to type Head ascending if necessary.
|
|
|
|
E2254
|
More than previous value
|
Info
|
Head Discharge ID
|
|
Cause
|
Applicable to pumps of Link Type = ROTPMP:
Head values in the Head / Discharge Grid are in ascending order i.e. type = Head ascending.
|
|
Advice
|
Check that the correct Head / Discharge Grid is associated with the pump. Change Head / Discharge Grid to type Head descending (ROTPMP) if necessary.
|
|
|
|
E2255
|
Porous Polygon <Porous Polygon ID> has been added since meshing was performed
|
Info
|
2D Zone ID, Porous Polygon ID
|
|
Cause
|
The Porous Polygon identified intersects a 2D Zone that has been meshed, but was not used to create the current mesh in the 2D Simulation Polygon.
This error may be caused by renaming of the Porous Polygon.
|
|
Advice
|
Re-mesh the 2D Zone using the current set of porous polygons.
Alternatively, if the Porous Polygon was renamed, reset the Porous Polygon ID to the value used when the 2D mesh was created.
|
|
|
|
E2256
|
First value must be 0
|
Info
|
Head Discharge ID
|
|
Cause
|
The first value in the Discharge column of the Head / Discharge Grid of the Head Discharge is not equal to 0.
|
|
Advice
|
Check the Head / Discharge Grid entries of the reported Head Discharge.
|
|
|
|
E2257
|
Head must be zero when discharge
is zero
|
Info
|
Head Discharge ID
|
|
Cause
|
Applicable to User Control of Link Type = Vortex.
The Discharge value corresponding with Head = 0 in the Head / Discharge Grid is not equal to 0.
|
|
Advice
|
Check the Head / Discharge Grid entries of the reported Head Discharge.
|
|
|
|
E2258
|
Less than previous value
|
Info
|
Head Discharge ID
|
|
Cause
|
Applicable to objects with associated Head Discharge curves except for pumps of Link Type = ROTPMP:
Discharge values in the Head / Discharge Grid are in descending order i.e. type = Head descending (ROTPMP).
|
|
Advice
|
Check that the correct Head / Discharge Grid is associated with the object. Change Head / Discharge Grid to type Head ascending if necessary.
When modelling a vortex control, modification of the head discharge curve is required to remove the negative gradient in the kickback flow region.
Suggested modification to vortex control curve
|
|
|
|
E2259
|
Subcatchment <subcatchment id> has been deleted/renamed since meshing was performed
|
Info
|
2D Zone ID, Subcatchment ID
|
|
Cause
|
The Subcatchment identified was used to create the current mesh in the 2D Zone, but no longer exists.
(Subcatchments are only used to create a mesh when the 2D Zone option Apply rainfall etc directly to mesh elements is selected and the Apply rainfall etc option is set to outside subcatchments.)
This error may be caused as a result of renaming of the Subcatchment.
|
|
Advice
|
Re-mesh the 2D Zone using the current set of subcatchments.
Alternatively, if the Subcatchment was renamed, reset the Subcatchment ID to the value used when the 2D mesh was created.
|
|
|
|
E2260
|
Subcatchment <subcatchment id> has had its boundary changed since meshing was performed
|
Info
|
2D Zone ID, Subcatchment ID
|
|
Cause
|
The boundary of a Subcatchment used to create the 2D Zone mesh was edited after the 2D mesh was created.
(Subcatchments are only used to create a mesh when the 2D Zone option Apply rainfall etc directly to mesh elements is selected and the Apply rainfall etc option is set to outside subcatchments.)
|
|
Advice
|
Re-mesh the 2D Zone using the current set of Subcatchment boundaries.
|
|
|
|
E2261
|
Subcatchment <subcatchment id> has been added since meshing was performed
|
Info
|
2D Zone ID, Subcatchment ID
|
|
Cause
|
The Subcatchment identified intersects a 2D Zone that has been meshed, but was not used to create the current mesh in the 2D Simulation Polygon.
(Subcatchments are only used to create a mesh when the 2D Zone option Apply rainfall etc directly to mesh elements is selected and the Apply rainfall etc option is set to outside subcatchments.)
This error may be caused by renaming of the Subcatchment.
|
|
Advice
|
Re-mesh the 2D Zone using the current set of Subcatchments.
Alternatively, if the Subcatchment was renamed, reset the Subcatchment ID to the value used when the 2D mesh was created.
|
|
|
|
E2263
|
River reach <river reach id> has been deleted/renamed since meshing was performed
|
Info
|
2D Zone ID, River Reach ID
|
|
Cause
|
The River Reach identified was used to create the current mesh in the 2D Zone, but no longer exists.
This error may be caused as a result of renaming of the nodes to which the River Reach is connected.
|
|
Advice
|
Re-mesh the 2D Zone using the current set of River Reaches.
Alternatively, if the River Reach was renamed, reset the IDs of the connecting nodes to the value used when the 2D mesh was created.
|
|
|
|
E2264
|
River reach <river reach id> has had its boundary changed since meshing was performed
|
Info
|
2D Zone ID, River Reach ID
|
|
Cause
|
The boundary of a River Reach used to create the 2D Zone mesh was edited after the 2D mesh was created.
|
|
Advice
|
Re-mesh the 2D Zone using the current River Reach boundary.
|
|
|
|
E2267
|
River reach <river reach id> has been added since meshing was performed
|
Info
|
2D Zone ID, River Reach ID
|
|
Cause
|
The River Reach identified intersects a 2D Zone that has been meshed, but was not used to create the current mesh in the 2D Zone.
This error may be caused by renaming of the nodes to which the River Reach is connected.
|
|
Advice
|
Re-mesh the 2D Zone using the current set of River Reaches.
Alternatively, if the River Reach was renamed, reset the IDs of the connecting nodes to the value used when the 2D mesh was created.
|
|
|
|
E2268
|
A value must be specified for this field when applying rainfall directly to mesh elements
|
Info
|
2D Zone ID
|
|
Cause
|
The Apply rainfall etc directly to mesh elements option of the 2D Zone has been selected, but a Rainfall Profile value has not been entered.
|
|
Advice
|
Enter a Rainfall Profile value.
|
|
|
|
E2270
|
Bridge <bridge id> has been deleted/renamed since meshing was performed
|
Info
|
2D Zone ID, Bridge ID
|
|
Cause
|
The Bridge identified was used to create the current mesh in the 2D Zone, but no longer exists.
This error may be caused as a result of renaming of the nodes to which the Bridge is connected.
|
|
Advice
|
Re-mesh the 2D Zone using the current set of Bridges.
Alternatively, if the Bridge was renamed, reset the IDs of the connecting nodes to the value used when the 2D mesh was created.
|
|
|
|
E2271
|
Bridge <bridge id> has had its boundary changed since meshing was performed
|
Info
|
2D Zone ID, Bridge ID
|
|
Cause
|
The boundary of a Bridge used to create the 2D Zone mesh was edited after the 2D mesh was created.
|
|
Advice
|
Re-mesh the 2D Zone using the current Bridge boundary.
|
|
|
|
E2272
|
Bridge <bridge id> has been added since meshing was performed
|
Info
|
2D Zone ID, Bridge ID
|
|
Cause
|
The Bridge identified intersects a 2D Zone that has been meshed, but was not used to create the current mesh in the 2D Zone.
This error may be caused by renaming of the nodes to which the Bridge is connected.
|
|
Advice
|
Re-mesh the 2D Zone using the current set of Bridges.
Alternatively, if the Bridge was renamed, reset the IDs of the connecting nodes to the value used when the 2D mesh was created.
|
|
|
|
E2273
|
Storage area <storage area id> has been deleted/renamed since meshing was performed
|
Info
|
2D Zone ID, Storage Area ID
|
|
Cause
|
The Storage Area identified was used to create the current mesh in the 2D Zone, but no longer exists.
This error may be caused as a result of renaming of the Storage Area.
|
|
Advice
|
Re-mesh the 2D Zone using the current set of Storage Areas.
Alternatively, if the Storage Area was renamed, reset the Storage Area ID to the value used when the 2D mesh was created.
|
|
|
|
E2274
|
Storage area <storage area id> has had its boundary changed since meshing was performed
|
Info
|
2D Zone ID, Storage Area ID
|
|
Cause
|
The boundary of a Storage Area used to create the 2D Zone mesh was edited after the 2D mesh was created.
|
|
Advice
|
Re-mesh the 2D Zone using the current Storage Area boundary.
|
|
|
|
E2275
|
Storage area <storage area id> has been added since meshing was performed
|
Info
|
2D Zone ID, Storage Area ID
|
|
Cause
|
The Storage Area identified intersects a 2D Zone that has been meshed, but was not used to create the current mesh in the 2D Zone.
This error may be caused by renaming of the Storage Area.
|
|
Advice
|
Re-mesh the 2D Zone using the current set of Storage Areas.
Alternatively, if the Storage Area was renamed, reset the Storage Area ID to the value used when the 2D mesh was created.
|
|
|
|
E2276
|
More than initial infiltration
|
Info
|
Runoff Surface ID
|
|
Cause
|
Applicable to Runoff Surfaces with Runoff Volume Type = Horton or HortonSWMM.
Limiting infiltration value > Initial infiltration value.
|
|
Advice
|
Check the Infiltration parameters of the reported Runoff Surface.
|
|
|
|
E2279
|
Not greater than 0.000
|
Info
|
Runoff Surface ID
|
|
Cause
|
Applicable to Runoff Surfaces with Runoff Volume Type = HortonSWMM.
Horton drying time value < 0
|
|
Advice
|
Check the Infiltration parameters of the reported Runoff Surface.
|
|
|
|
E2280
|
Less than minimum runoff
|
Info
|
Runoff Surface ID
|
|
Cause
|
Applicable to Runoff Surfaces with Runoff Volume Type = Wallingfrd.
Wal. Proc. Minimum runoff value > Wal. Proc. Maximum runoff value.
|
|
Advice
|
Check the runoff parameters of the reported Runoff Surface.
|
|
|
|
E2281
|
Infiltration zone (2D) <infiltration zone id> has been
added since meshing was performed
|
Info
|
2D Zone ID, Infiltration Zone ID
|
|
Cause
|
The Infiltration Zone identified intersects a 2D Zone that has been meshed, but was not used to create the current mesh in the 2D Zone.
This error may be caused by renaming of the Infiltration Zone.
|
|
Advice
|
Re-mesh the 2D Zone using the current set of infiltration zones.
Alternatively, if the Infiltration Zone was renamed, reset the Infiltration Zone ID to the value used when the 2D mesh was created.
|
|
|
|
E2281
|
This runoff volume type is inappropriate
for impervious surfaces
|
Info
|
Runoff Surface ID
|
|
Cause
|
Applicable to Runoff Surfaces with Runoff Volume Type = Horton, HortonSWMM, NewUK, GreenAmpt, ConstInf and UKWIRPerv.
Surface Type field has been set to Impervious.
|
|
Advice
|
Check the Runoff Surface parameters are as expected.
|
|
|
|
E2282
|
SCS initial loss is only valid on
SCS and CN runoff volumes
|
Info
|
Runoff Surface ID
|
|
Cause
|
Applicable to Runoff Surfaces using Runoff Volume Types other than SCS and CN.
Initial Loss Type field has been set to SCS.
|
|
Advice
|
Check the Runoff Surface parameters are as expected.
|
|
|
|
E2283
|
ReFH runoff volume type must have ReFH runoff routing type
|
Info
|
Runoff Surface ID
|
|
Cause
|
Runoff Volume Type is ReFH but Routing Model is not ReFH or vice versa.
|
|
Advice
|
Check the Runoff Surface parameters are as expected.
|
|
|
|
E2284
|
This runoff volume type is inappropriate
for pervious surfaces
|
Info
|
Runoff Surface ID
|
|
Cause
|
Applicable to Runoff Surfaces with Runoff Volume Type = UKWIRPaved.
Surface Type field has been set to Pervious.
|
|
Advice
|
Check the Runoff Surface parameters are as expected.
|
|
|
|
E2287
|
Minimum element area has changed since meshing was performed
|
Info
|
2D Zone ID
|
|
Cause
|
The value of the Minimum element area field has been changed since the current 2D mesh was created.
|
|
Advice
|
Re-mesh the 2D Zone using the current minimum element area.
|
|
|
|
E2287
|
The 'Cascade' routing model does not support the 'Rel' routing type, except when the number of reservoirs is zero
|
Info
|
Runoff Surface
|
|
Cause
|
The Routing model is set to Cascade, the Runoff routing type is set to Rel and the specified Number of reservoirs is greater than zero, but the Cascade model can only be used with a Rel routing type if the number of reservoirs is set to 0.
|
|
Advice
|
Either select a different Routing model or Runoff routing type, or if you want to use the Cascade model with Runoff routing type set to Rel, change the Number of reservoirs to 0.
|
|
|
|
E2288
|
Mesh zone <mesh zone id> has had its minimum element area changed since meshing was performed
|
Info
|
2D Zone ID, Mesh Zone ID
|
|
Cause
|
The value of the Minimum element area field or the status of the Override 2D zone minimum element area field has been changed since the current 2D mesh was created.
|
|
Advice
|
Re-mesh the 2D Zone using the current mesh zone settings.
|
|
|
|
E2292
|
Terrain-sensitive meshing option has changed since meshing was performed
|
Info
|
2D Zone ID
|
|
Cause
|
The status of the Terrain-sensitive msehing field of the 2D Zone has been changed since the current 2D mesh was created.
|
|
Advice
|
Re-mesh the 2D Zone using the current settings.
|
|
|
|
E2294
|
Maximum height variation must be specified for terrain-sensitive meshing
|
Info
|
2D Zone ID
|
|
Cause
|
The Terrain-sensitive meshing option for the 2D Zone has been checked, but a value has not been entered in the Maximum height variation field.
|
|
Advice
|
Enter a Maximum height variation for the 2D Zone.
|
|
|
|
E2295
|
Linear Structure (2D) <linear structure id> has
been deleted/renamed since meshing was performed
|
Info
|
2D Zone ID, Linear Structure (2D) ID
|
|
Cause
|
The Linear Structure (2D) identified was used to create the current mesh in the 2D Zone, but no longer exists.
This error may be caused as a result of renaming of the Linear Structure (2D).
|
|
Advice
|
Re-mesh the 2D Zone using the current set of Linear Structure (2D) objects.
Alternatively, if the Linear Structure (2D) was renamed, reset the ID to the value used when the 2D mesh was created.
|
|
|
|
E2296
|
Linear Structure (2D) <linear structure id> has had
its boundary changed since meshing was performed
|
Info
|
2D Zone ID, Linear Structure (2D) ID
|
|
Cause
|
The Linear Structure (2D) identified intersects a 2D Zone that has been meshed, but was not used to create the current mesh in the 2D Zone.
This error may be caused by renaming of the Linear Structure (2D).
|
|
Advice
|
Re-mesh the 2D Zone using the current set of Linear Structure (2D) objects.
Alternatively, if the Linear Structure (2D) was renamed, reset the ID to the value used when the 2D mesh was created.
|
|
|
|
E2297
|
Linear Structure (2D) <linear structure id> has
been added since meshing was performed
|
Info
|
2D Zone ID, Linear Structure (2D) ID
|
|
Cause
|
The Linear Structure (2D) identified intersects a 2D Zone that has been meshed, but was not used to create the current mesh in the 2D Zone.
This error may be caused by renaming of the Linear Structure (2D).
|
|
Advice
|
Re-mesh the 2D Zone using the current set of Linear Structure (2D) objects.
Alternatively, if the Linear Structure (2D) was renamed, reset the ID to the value used when the 2D mesh was created.
|
|
|
|
E2298
|
Base linear Structure (2D) <base linear structure id> has
had its sluice/bridge (2D) sub-structures changed since meshing was performed
|
Info
|
2D Zone ID, Base Linear Structure (2D) ID
|
|
Cause
|
May be caused by the following:
- Fields affecting the geometry of a Sluice / Bridge Linear Structure (2D) object associated with the Base Linear Structure (2D) identified have been changed since the 2D Zone was meshed.
- A new Sluice / Bridge Linear Structure (2D) object has been associated with the Base Linear Structure (2D), or an existing associated object has been renamed.
- A Sluice /Bridge Linear Structure (2D) object that was associated with the Base Linear Structure (2D) is no longer associated with the structure, or has been renamed.
|
|
Advice
|
Re-mesh the 2D Zone using the current set of Sluice /Bridge Linear Structure (2D) objects.
|
|
|
|
E2299
|
Mesh zone <mesh zone id> has had its ground level modification type changed since meshing was performed
|
Info
|
Mesh Zone ID
|
|
Cause
|
The Ground level modification field of the Mesh Zone identified has been changed since the current mesh in the 2D Zone was created.
|
|
Advice
|
Re-mesh the 2D Zone using the current mesh zone settings.
|
|
|
|
E2300
|
Mesh zone <mesh zone id> has had its level adjustment changed since meshing was performed
|
Info
|
Mesh Zone ID
|
|
Cause
|
The Raise by or Level field (used for ground level modification) of the Mesh Zone identified has been changed since the current mesh in the 2D Zone was created.
|
|
Advice
|
Re-mesh the 2D Zone using the current mesh zone settings.
|
|
|
|
E2301
|
No corresponding surface index in
land use
|
Info
|
Subcatchment ID
|
|
Cause
|
A value has been specified in a Subcatchment Runoff Area with no corresponding Surface ID defined in the associated Land Use.
|
|
Advice
|
Check that all Surface IDs have been defined in Land Use associated with the reported Subcatchment.
|
|
|
|
E2302
|
Not in land use set
|
Info
|
Subcatchment ID
|
|
Cause
|
Node selected in Subcatchment Land Use ID field does not exist or Land Use ID has not been specified.
|
|
Advice
|
Check that correct Subcatchment Land Use ID has been selected.
|
|
|
|
E2304
|
Time to peak must be greater than or equal to zero
|
Info
|
Subcatchment ID
|
|
Cause
|
Time to peak field on the Runoff Page of the Subcatchment Property Sheet is less than zero and the Routing Model field on the Runoff Surfaces grid is set to Unit, SCS Unit or ReFH.
|
|
Advice
|
Enter a Time to peak value greater than or equal to zero for the Subcatchment.
|
|
|
|
E2305
|
Base time must be greater than or equal to zero
|
Info
|
Subcatchment ID
|
|
Cause
|
Base time field on the Runoff Page of the Subcatchment Property Sheet is less than zero and the Routing Model field on the Runoff Surfaces grid is set to Unit or SCS Unit.
|
|
Advice
|
Enter a Base time value for the Subcatchment.
|
|
|
|
E2306
|
Catchment dimension must be non-zero
|
Info
|
Subcatchment ID
|
|
Cause
|
Applies to Subcatchments where Runoff Surfaces use Routing Model: SWMM, Desbordes or LargeCatch:
The warning message will be displayed if there is a contributing surface area (sum of the Subcatchment Runoff Areas > 0) but the Subcatchment Dimension field <= 0.
|
|
Advice
|
Check the Subcatchment Parameters.
|
|
|
|
E2307
|
Not in node set
|
Info
|
Subcatchment ID
|
|
Cause
|
Node selected in the Subcatchment Node ID or Ground infiltration node field does not exist or Node ID has not been specified.
|
|
Advice
|
Check that correct Subcatchment Node ID has been selected.
|
|
|
|
E2308
|
Nonexistent link <link sufffix> specified to drain to
|
Info
|
Subcatchment
|
|
Cause
|
The subcatchment is specified to drain to a link but the specified link suffix does not exist.
|
|
Advice
|
Check the subcatchment definition is as expected.
|
|
|
|
E2310
|
Subcatchments cannot drain to outfalls
|
Info
|
Subcatchment
|
|
Cause
|
Node selected in Subcatchment Node ID field is of type Outfall.
|
|
Advice
|
Check that the correct node has been selected in the Subcatchment Node ID field.
|
|
|
|
E2311
|
Not in ground infiltration set
|
Info
|
Subcatchment ID
|
|
Cause
|
Ground Infiltration data selected in the Ground Infiltration ID field of the Subcatchment object has not been defined.
|
|
Advice
|
Define new Ground Infiltration data or select an existing Ground Infiltration.
|
|
|
|
E2315
|
An ReFH unit hydrograph must be defined if the routing model is of type ReFH
|
Info
|
Subcatchment ID
|
|
Cause
|
The runoff surface associated with the subcatchment is an ReFH surface, but the Unit hydrograph definition specified is not ReFH.
|
|
Advice
|
Set Unit hydrograph definition to ReFH for ReFH runoff surfaces.
|
|
|
|
E2317
|
Incorrect routing definition for this routing model
|
Info
|
Subcatchment ID
|
|
Cause
|
The Unit hydrograph definition specified for the subcatchment can not be used with the Routing Model selected for the associated runoff surface.
For example, a Routing Model of Snyder Unit can only use a Unit Hydrograph Definition of Snyder.
|
|
Advice
|
Check Subcatchment Unit hydrograph definition and Runoff Surface Routing Model fields are set as expected.
|
|
|
|
E2318
|
Network results line (2D) <results line ID> has
been deleted/renamed since meshing was performed
|
Info
|
2D Zone ID, Network Results Line (2D) ID
|
|
Cause
|
The Network Results Line (2D) identified was used to create the current mesh in the 2D Zone, but no longer exists.
This error may be caused as a result of renaming of the network results line.
|
|
Advice
|
Re-mesh the 2D Zone using the current set of Network Results Lines.
Alternatively, if the results line was renamed, reset the results line ID to the value used when the 2D mesh was created.
|
|
|
|
E2319
|
Network results line (2D) <results line ID> has
had its boundary changed since meshing was performed
|
Info
|
2D Zone ID, Network Results Line (2D) ID
|
|
Cause
|
The boundary of a Network Results Line (2D) used to create the 2D Zone mesh was edited after the 2D mesh was created.
|
|
Advice
|
Re-mesh the 2D Zone using the current Network Results Line boundary.
|
|
|
|
E2319
|
Inline Bank has RTC but invalid 2D Zone
|
Info
|
Inline Bank ID
|
|
Cause
|
RTC Definitions have been specified in the Section data of the Inline Bank and either a 2D Zone ID has not been specified, or a 2D Zone ID that does not exist in the network has been specified.
|
|
Advice
|
Connect the Inline Bank to a 2D Zone by specifying a valid 2D zone ID.
|
|
|
|
E2320
|
Network results line (2D) <results line ID> has
been added since meshing was performed
|
Info
|
2D Zone ID, Network Results Line (2D) ID
|
|
Cause
|
The Network Results Line (2D) identified intersects a 2D Zone that has been meshed, but was not used to create the current mesh in the 2D Zone.
This error may be caused by renaming of the Network Results Line (2D).
|
|
Advice
|
Re-mesh the 2D Zone using the current set of Network Results Lines.
Alternatively, if the line was renamed, reset the ID to the value used when the 2D mesh was created.
|
|
|
|
E2321
|
Network results polygon (2D) <results polygon ID> has
been deleted/renamed since meshing was performed
|
Info
|
2D Zone ID, Network Results Polygon (2D) ID
|
|
Cause
|
The Network Results Polygon (2D) identified was used to create the current mesh in the 2D Zone, but no longer exists.
This error may be caused as a result of renaming of the network results polygon.
|
|
Advice
|
Re-mesh the 2D Zone using the current set of Network Results Polygons.
Alternatively, if the results polygon was renamed, reset the results polygon ID to the value used when the 2D mesh was created.
|
|
|
|
E2322
|
Network results polygon (2D) <results polygon ID> has
had its boundary changed since meshing was performed
|
Info
|
2D Zone ID, Network Results Polygon (2D) ID
|
|
Cause
|
The boundary of a Network Results Polygon (2D) used to create the 2D Zone mesh was edited after the 2D mesh was created.
|
|
Advice
|
Re-mesh the 2D Zone using the current Network Results Polygon boundary.
|
|
|
|
E2323
|
Network results polygon (2D) <results polygon ID> has
been added since meshing was performed
|
Info
|
2D Zone ID, Network Results Polygon (2D) ID
|
|
Cause
|
The Network Results Polygon (2D) identified intersects a 2D Zone that has been meshed, but was not used to create the current mesh in the 2D Zone.
This error may be caused by renaming of the Network Results Polygon (2D).
|
|
Advice
|
Re-mesh the 2D Zone using the current set of Network Results Polygons.
Alternatively, if the polygon was renamed, reset the ID to the value used when the 2D mesh was created.
|
|
|
|
E2326
|
Runoff surfaces have different routing
models
|
Info
|
Land Use ID
|
|
Cause
|
The Runoff Surfaces associated with the Land Use object have different Routing Models.
|
|
Advice
|
Check the correct Runoff Surfaces have been associated with the reported Land Use object.
|
|
|
| E2326 |
Stream name required
|
Info
|
Spatial rain source ID
|
|
Cause
|
The Stream name or category field is blank.
|
|
Advice
|
Specify a TSDB or STDSB data stream or a TVD connector Category.
|
|
|
|
E2327
|
This surface is not defined in runoff
surfaces
|
Info
|
Land Use ID
|
|
Cause
|
The ID of a Runoff Surface that does not exist has been included in the Land Use Surfaces grid.
|
|
Advice
|
Define a new Runoff Surface or select an existing Runoff Surface.
|
|
|
|
E2328
|
A value must be specified for this field
|
Info
|
Subcatchment ID
|
|
Cause
|
The runoff routing model selected for the Runoff Surface for this subcatchment requires a Time to Peak (Tp) value, but a value for Tp has not been specified.
|
|
Advice
|
Specify a value for Tp on the Runoff page of the Subcatchment property sheet.
|
|
|
|
E2329
|
1D Results object associated with invalid upstream node
|
Info
|
Network Results Point (1D) ID
|
|
Cause
|
The node specified in the US node ID field of the Network Results Point (1D) does not exist in the network.
|
|
Advice
|
Specify a valid US node ID.
|
|
|
|
E2329
|
A value must be specified for this field
|
Info
|
Subcatchment ID
|
|
Cause
|
The runoff routing model selected for the Runoff surface for this subcatchment requires a Base time (Tb) value, but a value for Tb has not been specified.
|
|
Advice
|
Specify a value for Tb on the Runoff page of the Subcatchment property sheet.
|
|
|
|
E2329
|
You can only mix New UK runoff volume surfaces with fixed runoff volume surfaces
|
Info
|
Land Use ID
|
|
Cause
|
Runoff Surfaces associated with the reported Land Use include those of Runoff Volume Type = NewUK and Runoff Volume Type other than Fixed
|
|
Advice
|
Check that the correct Runoff Surfaces have been associated with the reported Land Use object.
Check the Runoff Volume Types assigned to associated Runoff Surfaces.
|
|
|
|
E2330
|
A Green-Ampt runoff volume surface
can only be the last defined surface for a land use
|
Info
|
Land Use ID
|
|
Cause
|
More than one Runoff Surface associated with the reported Land Use is of Runoff Volume Type = GreenAmpt
or
A Runoff Surface of Runoff Volume Type = GreenAmpt is associated with the reported Land Use but is not the last surface in the Surfaces Tab of the Runoff Surfaces Property Sheet
|
|
Advice
|
Check that the correct Runoff Surfaces have been associated with the reported Land Use object.
Check the Runoff Volume Types assigned to associated Runoff Surfaces.
|
|
|
|
E2330
|
1D Results object associated with invalid link suffix
|
Info
|
Network Results Point (1D) ID
|
|
Cause
|
The link specified by the US node ID and Link suffix field of the Network Results Point (1D) does not exist in the network.
The node exists, but the link suffix is incorrect.
|
|
Advice
|
Specify a valid Link suffix.
|
|
|
|
E2331
|
1D Results object associated with invalid bridge opening
|
Info
|
Network Results Point (1D) ID
|
|
Cause
|
The bridge opening specified by the Bridge opening ID field of the Network Results Point (1D) does not exist in the network.
|
|
Advice
|
Specify a valid Bridge opening ID.
|
|
|
|
E2332
|
1D Results object must be associated with a link or bridge opening
|
Info
|
Network Results Point (1D) ID
|
|
Cause
|
Neither a Bridge opening ID or US node ID and Link suffix has been specified for the Network Results Point 1D
|
|
Advice
|
Specify a valid Bridge opening ID or valid US node ID and Link suffix.
|
|
|
|
E2332
|
Can only mix Wallingford runoff volume
surfaces with fixed runoff volume surfaces
|
Info
|
Land Use ID
|
|
Cause
|
Runoff Surfaces associated with the reported Land Use include those of Runoff Volume Type = Wallingford and Runoff Volume Type other than Fixed
|
|
Advice
|
Check that the correct Runoff Surfaces have been associated with the reported Land Use object.
Check the Runoff Volume Types assigned to associated Runoff Surfaces.
|
|
|
|
E2333
|
Damage receptor <damage receptor id> has been deleted/renamed since 2d elements were last assigned
|
Info
|
2D Zone ID, Damage Receptor ID
|
|
Cause
|
The Damage Receptor identified was used to assign 2D elements to Damage Receptors, but no longer exists.
This error may be caused as a result of renaming of the Damage Receptor.
|
|
Advice
|
Re-assign the 2D elements using the current set of Damage Receptors.
Alternatively, if the Damage Receptor was renamed, reset the Damage Receptor ID to the value used when the 2D elements were assigned.
|
|
|
|
E2334
|
PDM runoff volume surface must be the first and only runoff surface
|
Info
|
Land Use ID
|
|
Cause
|
Multiple runoff surfaces associated with the reported Land Use including those of Runoff Volume Type = PDM.
A PDM runoff surface must be the only runoff surface associated with a subcatchment.
|
|
Advice
|
Check that the correct Runoff Surfaces have been associated with the reported Land Use object.
Check the Runoff Volume Types assigned to associated Runoff Surfaces.
|
|
|
|
E2335
|
Can only mix UKWIR surfaces with other UKWIR surfaces
|
Info
|
Land Use ID
|
|
Cause
|
Runoff Surfaces associated with the reported Land Use include those of Runoff Volume Type = UKWIRPaved or UKWIRPerv and Runoff Volume Type other than a UKWIR type.
|
|
Advice
|
Check that the correct Runoff Surfaces have been associated with the reported Land Use object.
Check the Runoff Volume Types assigned to associated Runoff Surfaces.
|
|
|
|
E2336
|
Cannot have more than one CNSWMM runoff volume surface
|
Info
|
Land use ID
|
|
Cause
|
Runoff surfaces associated with the reported Land use include more than one whose Runoff volume type is set to CNSWMM.
|
|
Advice
|
Check that there is only one Runoff surface, which is associated with the reported Land use object, that has a Runoff volume type set to CNSWMM.
|
|
|
|
E2337
|
Can only mix CNSWMM runoff volume surfaces with Fixed runoff volume surfaces
|
Info
|
Land use ID
|
|
Cause
|
Runoff surfaces associated with the reported Land Use include those of Runoff volume type = CNSWMM and Runoff volume type other than a Fixed type.
|
|
Advice
|
Check that the correct Runoff surfaces have been associated with the reported Land use object.
Check the runoff volume types assigned to the associated Runoff surfaces.
|
|
|
|
E2340
|
Inline Bank has 2D Zone specified but is not connected to an Outfall node
|
Info
|
Inline Bank ID
|
|
Cause
|
A 2D Zone ID has been specified for the Inline Bank, but the inline bank is not connected to an Outfall node.
Note: to model flow between the 1D network and a 2D mesh, the inline bank must be connected to a node of type Outfall, not Outfall 2D. An inline bank connected to a node of type Outfall 2D will be treated as a 1D link with flow entering the 2D zone at a point.
|
|
Advice
|
Connect the Inline Bank to a node of Node type Outfall.
|
|
|
|
E2341
|
A value must be specified for this field
|
Info
|
Subcatchment ID
|
|
Cause
|
An RefH runoff surface is associated with the subcatchment, but no unit hydrograph Time to peak, tp value has been specified.
|
|
Advice
|
Enter a Time to peak, tp value for the subcatchment.
|
|
|
|
E2342
|
Unit hydrograph peak must be greater than or equal to zero
|
Info
|
Subcatchment ID
|
|
Cause
|
Unit hydrograph Time to peak, tp value specified is less than zero.
|
|
Advice
|
Enter a Time to peak, tp value greater than or equal to zero for the subcatchment.
|
|
|
|
E2343
|
A value must be specified for this field
|
Info
|
Subcatchment ID
|
|
Cause
|
An RefH runoff surface is associated with the subcatchment, but no unit hydrograph Degree of kink value has been specified.
|
|
Advice
|
Enter a Degree of kink value for the subcatchment.
|
|
|
|
E2344
|
Degree of kink must be greater than or equal to zero
|
Info
|
Subcatchment ID
|
|
Cause
|
Unit hydrograph Degree of kink value specified is less than zero.
|
|
Advice
|
Enter a Degree of kink value greater than or equal to zero for the subcatchment.
|
|
|
|
E2348
|
A value must be specified for this field when runoff volume type is SRM or PDM on first runoff surface referenced
|
Info
|
Subcatchment ID
|
|
Cause
|
Runoff surface 1 of the Land Use associated with the reported Subcatchment is set to runoff surface with Runoff Volume Type = SRM or PDM and a value has not been entered in subcatchment SRM field, Baseflow calculation field or Soil moisture deficit field.
|
|
Advice
|
Enter value in subcatchment field causing validation error.
|
|
|
|
E2349
|
Must reference a PDM descriptor when baseflow calculation or soil moisture deficit set to 'PDM' and runoff surface runoff volume type is SRM
|
Info
|
Subcatchment ID
|
|
Cause
|
Runoff surface 1 of the Land Use associated with the reported Subcatchment is set to runoff surface with Runoff Volume Type = SRM and subcatchment Baseflow calculation and/or Soil moisture deficit fields are set to PDM, but a value has not been entered in the PDM descriptor field.
|
|
Advice
|
Enter value in subcatchment PDM descriptor field.
|
|
|
|
E2350
|
Must reference a PDM descriptor when runoff surface runoff volume type is PDM
|
Info
|
Subcatchment ID
|
|
Cause
|
Runoff surface 1 of the Land Use associated with the reported Subcatchment is set to runoff surface with Runoff Volume Type = PDM and a value has not been entered in subcatchment PDM descriptor field.
|
|
Advice
|
Enter value in subcatchment PDM descriptor field.
|
|
|
|
E2351
|
HOST SPR calculations need HOST soil class set
|
Info
|
Subcatchment ID
|
|
Cause
|
SPR calculation is set to HOST_Soils or HOST_FEH, but HOST soil class is not set.
|
|
Advice
|
Enter value in subcatchment HOST soil class field.
|
|
|
|
E2352
|
HOST predominant soils cannot have HOST soil class 28
|
Info
|
Subcatchment ID
|
|
Cause
|
SPR calculation is set to HOST_Soils and HOST soil class is set to 28.
(HOST predominant soils has no SPR defined for HOST=28)
|
|
Advice
|
Enter value in subcatchment HOST soil class field other than 28.
|
|
|
|
E2353
|
Standard percentage runoff must be set
|
Info
|
Subcatchment ID
|
|
Cause
|
Associated runoff surface is of type UKWIR, but Standard percentage runoff has not been set.
|
|
Advice
|
Enter value in subcatchment Standard percentage runoff field.
|
|
|
|
E2354
|
Value must be strictly greater than zero
|
Info
|
Subcatchment ID
|
|
Cause
|
Associated runoff surface has Routing model of type Non-linear, but subcatchment Slope has not been set or is less than zero.
(Slope is used to calculate values of K, p and lag time.)
or
Subcatchment Total area is greater than 2km2, Unit hydrograph definition is set to Rational and Time of concentration method is set to Kraven, but subcatchment Slope, Equivalent Manning's n or Hydraulic radius have been set to value less than or equal to zero.
(Slope, equivalent roughness and hydraulic radius are used to calculate flood wave celerity when catchment area is greater than 2km2.)
|
|
Advice
|
Enter value in subcatchment field.
|
|
|
|
E2355
|
ReFH/ReFH2 parameters are inconsistent with catchment descriptors
|
Info
|
Subcatchment ID
|
|
Cause
|
A catchment descriptor or option such as Country has been edited and is its parameter is no longer consistent with the specified ReFH or ReFH2 model.
or
The catchment descriptors are loaded and are different from the existing descriptors.
or
The parameters are imported from ReFH2 but the descriptors don’t match those on the dialog and they have not been updated.
or
The method for a descriptor is switched to “Design” and the design value is not available (either because it hasn’t been calculated yet or because the method was “User” when the dialog was opened).
|
|
Advice
|
Check that either the correct parameters or the model value is specified in subcatchment field.
|
|
|
|
E2356
|
Can only specify one of Node ID, To subcatchment ID, Lateral Links, 2D point source
|
Info
|
Subcatchment
|
|
Cause
|
More than one of the Drains to options has been specified for the subcatchment.
|
|
Advice
|
Check that the subcatchment only drains to either a Node ID or a To subcatchment ID or a set of Lateral links or a 2D point ID.
|
|
|
|
E2357
|
Must specify either a node , a link, a subcatchment, a 2D point source or a set of lateral links to drain to
|
Info
|
Subcatchment
|
|
Cause
|
The Drains to option for the subcatchment has not been specified.
|
|
Advice
|
Select the applicable option from the Drains to field and ensure that the name of the relevant object this subcatchment is to drain to is specified in the applicable Node ID, Link ID, To subcatchment ID or 2D point source field or in the Lateral links grid.
|
|
|
|
E2358
|
No subcatchment exists with this ID
|
Info
|
Subcatchment
|
|
Cause
|
The specified To subcatchment ID does not correspond to any subcatchment in the network.
|
|
Advice
|
Choose a subcatchment from the drop-down list in the To subcatchment ID field or create a new subcatchment with the required name/ID.
|
|
|
|
E2359
|
Cannot specify own ID as subcatchment to drain to
|
Info
|
Subcatchment
|
|
Cause
|
The name specified in the To subcatchment ID has the same name as the subcatchment. A subcatchment cannot drain into itself.
|
|
Advice
|
Choose a different subcatchment to drain to from the drop-down list in the To subcatchment ID field.
|
|
|
|
E2360
|
Specified ID results in a closed loop of drain to subcatchments
|
Info
|
Subcatchment
|
|
Cause
|
Following the chain of subcatchments specified in successive To subcatchment ID forms a closed loop.
|
|
Advice
|
To break the loop, choose a different subcatchment to drain to from the drop-down list in the To subcatchment ID field.
|
|
|
|
E2362
|
Uses ReFH2 version <number>. Other subcatchments in network use ReFH2 version <number>
|
Info
|
Subcatchment
|
|
Cause
|
The subcatchments in the network use different versions of ReFH2.
|
|
Advice
|
Ensure that all the subcatchments use the same version of ReFH2.
|
|
|
|
E2366
|
Unit hydrograph definition must be 'Name' if runoff surface has routing model 'Name'
|
Info
|
Subcatchment
|
|
Cause
|
The unit hydrograph selected in the Unit hydrograph definition field is different to that used by the routing model specified for the runoff surface. These must be the same.
|
|
Advice
|
Choose the relevant unit hydrograph from the drop-down list in the Unit hydrograph definition field.
|
|
|
|
E2367
|
Runoff surface must have routing model 'Name' if unit hydrograph definition is 'Name'
|
Info
|
Subcatchment
|
|
Cause
|
The routing model specified for the runoff surface uses a different unit hydrograph to that selected in the Unit hydrograph definition field. These must be the same.
|
|
Advice
|
Choose the relevant model from the dropdown list in the Routing model field on the Runoff surface tab in the Subcatchment grid.
Alternatively, access the Routing model field from the subcatchment property sheet by clicking  next to the Land use ID field and selecting the option from the context menu to display the Land use Object Properties sheet. Then click next to the relevant Runoff Surface field on the Land use Object Properties sheet and select the option from the context menu. This displays the Runoff surface Object Properties sheet from which the relevant Routing model can be selected.
|
|
|
|
E2368
|
Must specify a set of lateral links to drain to
|
Info
|
Subcatchment
|
|
Cause
|
You have specified that subcatchment must Drain to Multiple links but have not specified which links should be used.
|
|
Advice
|
Specify which links the subcatchment should drain to in the Lateral links field.
|
|
|
| E2370 |
Groundwater cannot drain to outfalls
|
Info
|
Subcatchment
|
|
Cause
|
The Ground infiltration node is currently set to an outfall type of node but ground water cannot drain to an outfall node.
|
|
Advice
|
Select another ground infiltration node for the ground water to flow to.
|
|
|
| E2374 |
SUDS structures' total area greater than that of the subcatchment
|
Info
|
Subcatchment
|
|
Cause
|
The total area of all the SUDS structures (Area x Number of units) located within this subcatchment is greater than the area of the subcatchment.
|
|
Advice
|
Check the Area and Number of units entries for each SUDS structure.
|
|
|
|
E2376
|
A headloss curve must contain 2-15
entries
|
Info
|
Headloss Curve ID
|
|
Cause
|
Ratio / Value Grid of the Headloss Curve contains < 2 or > 15 rows.
|
|
Advice
|
Check the Ratio / Value Grid entries of the reported Headloss Curve.
|
|
|
|
E2377
|
A headloss curve must contain 2-15
entries
|
Info
|
Headloss Curve ID
|
|
Cause
|
Velocity / Value Grid of the Headloss Curve contains < 2 or > 15 rows.
|
|
Advice
|
Check the Velocity / Value Grid entries of the reported Headloss Curve.
|
|
|
|
E2380
|
When not 'None' must have 'Recharge and Runoff' set to 'Standard' and 'Soil moisture distribution' set to 'Pareto'
|
Info
|
PDM Descriptor ID
|
|
Cause
|
The Interflow field of the PDM descriptor has been set to a value other than None and Recharge and runoff is not set to Standard and/or Soil moisture distribution is not set to Pareto.
|
|
Advice
|
Review the settings for the Interflow, Recharge and runoff and Soil moisture distribution fields.
|
|
|
| E2381 |
A subcatchment with an RTK hydrograph must drain to a node if sim parameter "Use SWMM5 RDII" is selected
|
Info
|
RTK hydrograph
|
|
Cause
|
The Drains to field for the subcatchment is not currently set to Node.
|
|
Advice
|
Check that the Drains to field for the subcatchment is set to Node if SWMM5 RDII is to be used in the simulation.
Alternatively, uncheck the Use SWMM5 RDII option in the simulation parameters if this subcatchment is to drain to an object other than a node. Note that Monthly RTK Hydrographs can only be used in a simulation if the Use SWMM5 RDII option is selected.
|
|
|
|
E2382
|
Unit Hydrograph <ID> associated with multiple rainfall profiles (<Profile numbers>)
|
Info
|
Subcatchment
|
|
Cause
|
Subcatchments cannot use the same RTK hydrograph with different rainfall profiles.
|
|
Advice
|
Ensure that the subcatchments that use the same RTK hydrograph use the same rainfall profile.
|
|
|
|
E2384
|
Another subcatchment also with an RTK hydrograph drains to the same node and SWMM5 RDII is selected
|
Info
|
Node ID
|
|
Cause
|
The Use SWMM5 RDII option is selected in the simulation parameters but this subcatchment drains to the same node as another subcatchment for which an RTK Hydrograph is also specified; only one subcatchment with an RTK Hydrograph defined for it can drain to this node.
|
|
Advice
|
Check the specified Node ID and change if necessary.
Alternatively, uncheck the Use SWMM5 RDII box in the simulation parameters. Note that Monthly RTK Hydrographs can only be used in a simulation if the Use SWMM5 RDII option is selected.
|
|
|
|
E2385
|
<SUDS Structure ID> has product Area X (number of Units) greater than the area of surface(s) it occupies
|
Info
|
SUDS controls
|
|
Cause
|
The total area occupied by a SUDS structure (i.e. SUDS structure area × number of units) exceeds the area of the surface(s) on which they are located.
|
|
Advice
|
Check that the correct values have been entered in the Area and /or Number of units fields, or that the correct Surface has been selected for the SUDS control object.
|
|
|
|
E2388
|
Must not be less than 0.01 when routing model is 'RAFTS'
|
Info
|
Subcatchment
|
|
Cause
|
The value specified for the Equivalent Manning's n field is less than the permitted minimum value of 0.01, when the runoff routing model is set to RAFTS.
|
|
Advice
|
Either change the value for the Equivalent Manning's n field to one that is within the permitted range of 0.01 to 0.1, or choose a different routing model.
|
|
|
|
E2389
|
Must not exceed 0.10 when routing model is 'RAFTS'
|
Info
|
Subcatchment
|
|
Cause
|
The value specified for the Equivalent Manning's n field is more than the permitted maximum value of 0.1, when the runoff routing model is set to RAFTS.
|
|
Advice
|
Change the value for the Equivalent Manning's n field to one that is within the permitted range of 0.01 to 0.1, or choose a different routing model.
|
|
|
|
E2390
|
Value must be greater than zero
|
Info
|
Subcatchment
|
|
Cause
|
The value specified for the Storage factor K is not greater than zero (0).
If the runoff routing model is set to Cascade or Non-linear, then Storage factor K must be greater than zero.
|
|
Advice
|
Change the value for the Storage factor K field to one that is greater than zero (>0), or check that the correct routing model has been specified.
If you want to use the Cascade routing model with a Storage factor K set to 0, then ensure, for all subcatchment surfaces, that either the Number of reservoirs is set to 0, or, the Runoff routing type is set to ABS and the Runoff routing value is greater than zero.
If you want to use the Non-linear routing model with a Storage factor K set to 0, then ensure, for all subcatchment surfaces, that either the Number of reservoirs is set to 0, or, the Runoff routing value is greater than zero.
|
|
|
| E2392 |
When unit hydrograph definition is set to 'Rational' a time of concentration method must be selected
|
Info
|
Subcatchment ID
|
|
Cause
|
No option has been selected for the time of concentration method. When the Unit hydrograph definition is set to Rational, a method for calculating the time of concentration must be specified. |
|
Advice
|
Select a method in the Time of concentration method field for the subcatchment identified in the message. |
|
|
| E2393 |
Element <element_ID>: Assigned node not found
|
Info
|
Subcatchment ID
|
|
Cause
|
A node has been specified in the Drain to node field of the SUDs control structure that is associated with this subcatchment, but this node does not exist.
|
|
Advice
|
Ensure that the applicable node is specified in the Drain to node field of the SUDs control structure properties. If the correct node has been specified, then check that it has been added to the relevant network.
|
|
|
| E2394 |
Element <element_ID>: Assigned subcatchment not found
|
Info
|
Subcatchment ID
|
|
Cause
|
A subcatchment has been specified in the Drain to subcatchment field of the SUDs control structure that is associated with this subcatchment, but this subcatchment does not exist.
|
|
Advice
|
Ensure that the applicable subcatchment is specified in the Drain to subcatchment field of the SUDs control structure properties. If the correct subcatchment has been specified, then check that it has been added to the relevant network.
|
|
|
|
E2395
|
Must specify 2D point source to drain to
|
Info
|
Subcatchment
|
|
Cause
|
The Drains to field is set to 2D point source but you have not specified a 2D point source in the 2D point ID field.
|
|
Advice
|
Specify which 2D point source, in the 2D point ID field, that this subcatchment is to drain to.
|
|
|
|
E2396
|
2D point source to drain to not defined
|
Info
|
Subcatchment
|
|
Cause
|
The Drains to field has been specified as a 2D point source, but the 2D point source, specified in the 2D point ID field does not exist in this network.
|
|
Advice
|
Check that the appropriate 2D point source has been specified in the 2D point ID field, and either change if necessary, or ensure that the relevant 2D point source has been added for this network.
|
|
|
|
E2397
|
For Exceedance flow type '2D mesh' the subcatchment must drain to a node located inside a 2D mesh element.
|
Info
|
Subcatchment
|
|
Cause
|
The Exceedance flow type is set to 2D mesh but the subcatchment does not Drain to a node within a 2D mesh element.
|
|
Advice
|
Check that the Drains to field is set to Node, and that the node is located in a 2D mesh element. This can be any type of node except Outfall or Outfall 2D. Alternatively, change the Exceedance flow type.
|
|
|
|
E2402
|
Unit flow values must either be in ascending or descending order
|
Info
|
Head Unit Flow ID
|
|
Cause
|
The Unit flow values in the Head unit flow table editor must be specified in either ascending or descending order.
|
|
Advice
|
Review the Head and Unit flow values in the Head unit flow editor.
|
|
|
|
E2406
|
Overlaps with sluice/bridge linear structure (2D) <sluice/bridge linear structure (2D) id> on base linear structure <base linear structure (2D) id>
|
Info
|
Sluice/Bridge Linear Structure (2D) ID, Base Linear Structure (2D) ID
|
|
Cause
|
The Sluice/Bridge Linear Structure (2D) has Start length and Length values resulting in an overlap with another Sluice/Bridge Linear Structure (2D) object associated with the identified base linear structure.
|
|
Advice
|
Review the Start length and Length values of the 2D sluice/bridge.
|
|
|
|
E2407
|
Overlaps boundary of 2D zone <2D zone id>
|
Info
|
Bridge Linear Structure (2D) ID
|
|
Cause
|
The Bridge Linear Structure (2D) has Start length and Length values resulting in an overlap with a 2D zone boundary.
|
|
Advice
|
Review the Start length and Length values of the 2D bridge.
|
|
|
|
E2408
|
Must enter crest level values for all section data points
|
Info
|
Bridge Linear Structure (2D) ID
|
|
Cause
|
One or more Invert level values not specified in the Section data editor.
|
|
Advice
|
Enter Invert level values for all section data points.
|
|
|
|
E2409
|
Must enter opening height values for all section data points
|
Info
|
Bridge Linear Structure (2D) ID
|
|
Cause
|
One or more Opening height values not specified in the Section data editor.
|
|
Advice
|
Enter Opening height values for all section data points.
|
|
|
|
E2410
|
Must enter deck thickness values for all section data points
|
Info
|
Bridge Linear Structure (2D) ID
|
|
Cause
|
One or more Deck thickness values not specified in the Section data editor.
|
|
Advice
|
Enter Deck thickness values for all section data points.
|
|
|
|
E2426
|
Value must be strictly greater than zero
|
Info
|
Ground Infiltration ID, Ground Infiltration data field.
|
|
Cause
|
A value less than or equal to zero has been specified in a field of the Ground Infiltration object:
- Soil depth
- Percolation coefficient
- Baseflow coefficient
- Infiltration coefficient
|
|
Advice
|
Enter a value greater than zero in the data field identified.
|
|
|
|
E2426
|
Sediment fraction weights total to a value other than 1
|
Info
|
Sediment Grading ID
|
|
Cause
|
The sum of the sediment fraction weight values in the Sediment Grading is not equal to 1.
|
|
Advice
|
Review sediment fraction weights.
|
|
|
|
E2427
|
Must reference a linear structure (2D)
|
Info
|
Bridge Linear Structure (2D) ID
|
|
Cause
|
A value has not been specified in the Base linear structure (2D) ID field of the Bridge Linear Structure (2D).
|
|
Advice
|
Enter a Base linear structure (2D) ID for the 2D bridge.
|
|
|
|
E2428
|
Referenced linear structure (2D) does not exist in network
|
Info
|
Bridge Linear Structure (2D) ID
|
|
Cause
|
The linear structure specified in the Base linear structure (2D) ID field of the Bridge Linear Structure (2D) does not exist in the network.
|
|
Advice
|
Enter a valid Base linear structure (2D) ID for the 2D bridge.
|
|
|
|
E2436
|
Completely outside 2D zone boundary
|
Info
|
Bridge Linear Structure (2D) ID
|
|
Cause
|
The Bridge Linear Structure (2D) has Start length and Length values resulting in the structure being outside of any 2D zone.
|
|
Advice
|
Review the Start length and Length values of the 2D bridge.
|
|
|
|
E2451
|
Below attached node's lowest storage level
|
Info
|
Flume ID
|
|
Cause
|
Applicable to Flume objects linked to Nodes of type Storage.
Throat Level of downstream/upstream link < lowest level in connected Storage Node Level / Plan Area grid.
|
|
Advice
|
Check throat level of connected Flume and Storage Node Level values.
|
|
|
|
E2452
|
Mesh level zone <mesh level zone ID> has
been deleted/renamed since meshing was performed
|
Info
|
2D Zone ID, Mesh Level Zone ID
|
|
Cause
|
The Mesh Level Zone identified was used to create the current mesh in the 2D Zone, but no longer exists.
This error may be caused as a result of renaming of the Mesh Level Zone.
|
|
Advice
|
Re-mesh the 2D Zone using the current set of Mesh Level Zones.
Alternatively, if the Mesh Level Zone was renamed, reset the Mesh Level Zone ID to the value used when the 2D mesh was created.
|
|
|
|
E2453
|
Mesh level zone <mesh level zone ID> has
had its boundary changed since meshing was performed
|
Info
|
2D Zone ID, Mesh Level Zone ID
|
|
Cause
|
The boundary of a Mesh Level Zone used to create the 2D Zone mesh was edited after the 2D mesh was created.
|
|
Advice
|
Re-mesh the 2D Zone using the current Mesh Level Zone boundary.
|
|
|
|
E2454
|
Mesh level zone <mesh level zone ID> has
been added since meshing was performed
|
Info
|
2D Zone ID, Mesh Level Zone ID
|
|
Cause
|
The Mesh Level Zone identified intersects a 2D Zone that has been meshed, but was not used to create the current mesh in the 2D Zone.
This error may be caused by renaming of the Mesh Level Zone.
|
|
Advice
|
Re-mesh the 2D Zone using the current set of Mesh Level Zones.
Alternatively, if the zone was renamed, reset the ID to the value used when the 2D mesh was created.
|
|
|
|
E2455
|
Mesh level zone <mesh level zone ID> has
had its use lower limit setting changed since meshing was performed
|
Info
|
2D Zone ID, Mesh Level Zone ID
|
|
Cause
|
The setting of the Use lower limit field of the Mesh Level Zone identified was edited after the 2D mesh was created.
|
|
Advice
|
Re-mesh the 2D Zone, or re-level the mesh using the Resample 2D Zone Elevations Dialog.
|
|
|
|
E2456
|
Mesh level zone <mesh level zone ID> has
had its lower limit level changed since meshing was performed
|
Info
|
2D Zone ID, Mesh Level Zone ID
|
|
Cause
|
The value of the Lower limit level field of the Mesh Level Zone identified was edited after the 2D mesh was created.
|
|
Advice
|
Re-mesh the 2D Zone, or re-level the mesh using the Resample 2D Zone Elevations Dialog.
|
|
|
|
E2457
|
Mesh level zone <mesh level zone ID> has
had its use upper limit setting changed since meshing was performed
|
Info
|
2D Zone ID, Mesh Level Zone ID
|
|
Cause
|
The setting of the Use upper limit field of the Mesh Level Zone identified was edited after the 2D mesh was created.
|
|
Advice
|
Re-mesh the 2D Zone, or re-level the mesh using the Resample 2D Zone Elevations Dialog.
|
|
|
|
E2458
|
Mesh level zone <mesh level zone ID> has
had its upper limit level changed since meshing was performed
|
Info
|
2D Zone ID, Mesh Level Zone ID
|
|
Cause
|
The value of the Upper limit level field of the Mesh Level Zone identified was edited after the 2D mesh was created.
|
|
Advice
|
Re-mesh the 2D Zone, or re-level the mesh using the Resample 2D Zone Elevations Dialog.
|
|
|
