Error messages

Updated on 14 Aug 2024
64 Minutes to read

Article summary

Did you find this summary helpful?

Thank you for your feedback

This section lists the diagnostics messages that may be produced by the Flood Modeller 1D simulation engine.

Three types of message may occur:

Fatal error messages resulting in the termination of the run (E1000 - E1999)
Warning messages that do not result in run termination but that should be checked (W2001 - W2999)
Notes which assist in the interpretation of the model results (N3001 - N3999)

In the 1D diagnostic file (extension *.exy), Error and Diagnostic panel, each message produced by a simulation is listed with a severity code to enable users to quickly assess any major problems. Possible codes are 1 to 5, where code 1 represents fatal errors, code 5 represents notes and codes 2,3 and 4 represent warnings. The three classes that warnings are sub-divided into are; warnings likely to affect, warnings that may affect and warning unlikely to affect results.

Possible causes are given as well as, where appropriate, the remedial action that should be taken to attempt to cure the error.

If you require further technical help please contact the support team.

Error Messages E1000-E1099

Error code	Message	Troubleshooting / details - what do I do to resolve!
E1003	Bernoulli loss - no. of data sets must not be > 30 or < 1	The number of Bernoulli Loss data sets (stage, area, loss value) must be between 1 and 30
E1004	Data read error	An error has been detected in 'unit' at line number 'l'. Possible causes include: The number of data sets does not equal the specified number in the above unit; A tab has been included in a data field; A decimal place is included in an integer field; Character type data in a numeric type field (check 'o', 'l', 'z'); Unexpected increase or decrease in tabulated values (e.g. time decreasing in HTBDY data); Number of data fields detected not as stated in the documentation (i.e. missing data); INITIAL CONDITIONS omitted from the datafile.
E1005	Unit unacceptable as first data unit	A 'unit' is not allowed as the first unit in a datafile.
E1006	No. of stage/gate opening datasets < 2	A minimum of 2 pairs of stage and gate opening data are necessary in unit 'unit'.
E1007	Maximum no of gates exceeded	A maximum of 50 gates is allowed in a single vertical sluice unit, or 100 for a radial gate unit.
E1008	Maximum number of nodes is exceeded	The maximum number of nodes for the licence of Flood Modeller has been exceeded.
E1009	Maximum number of units is exceeded	The maximum number of units for the licence of Flood Modeller has been exceeded.
E1011	Unidentified unit	This indicates a possible typing error with a unit type identifier at line 'l'. Check that for the preceding unit the number of data sets is equal to the number specified.
E1013	The EGGFORM option is not yet available, try using a CIRCULAR conduit with a suitable diameter	Eggform conduits are not permitted.
E1014	Supercritical flow between 'label1' and 'label2'. You should use the option for dealing with Froude numbers greater than 1	Supercritical flow has been detected.
E1017	Negative flow - the direct method cannot handle backflow	During iterations the direct steady state method has calculated backflow over a structure. If backflow is not physically realistic then the error may be avoided by changing the flow splits in the initial conditions. Otherwise use the pseudo time stepping steady state method.
E1018	Maximum no. of iterations exceeded	The direct steady state method was unable to solve the equations at the structure at 'label'. The error may be avoided by changing the initial conditions, reviewing the structure data or by using the pseudo time stepping steady state method.
E1019	No solution found in Direct Method	The direct steady state method was unable to solve the equations at the structure at 'label'. The error may be avoided by changing the initial conditions, reviewing the structure data or by using the pseudo time stepping steady state method.
E1020	Water level exceeded maximum section data level dflood	Check model, extend section data or increase dflood. This error message most likely appears at the start of the simulation (i.e. straight away after the crash) and suggests that the initial conditions need improving. The user can look into extending section data and increasing dflood parameter, but if these operations are not successful or are not practical, then the following can be carried out: - increase the minimum flow of the model; - incrementally build the model and generate the initial conditions as you progress (this would also help to identify any troublesome areas of the model); -run the model in steady state to generate the initial conditions. If there are a number of structures or junctions in the model, then the recommendation could be to manually add an initial estimate of the split of the flows (For example, if there is a bride unit and a spill, 100% of the flow can be assigned to the bridge).
E1022	Not a recognised type number	The type number given is as follows: - 'x' Please contact the support team with full details of the problem
E1022	Error writing OTTA file	Mistake on the website. 1022 should be 1023. Do not select the 'Write Otta File' option.
E1023	Generic ERROR - see zzd file / complementary error code	ERROR in unit type 'unit' which is attached to the following labels:- 'label1' 'label2' Specifies the unit type and labels for the preceding error message. Error details are provided in the preceding error message.
E1027	Value of rsmd should not be less than 10	FSR parameter RSMD (residual soil moisture deficit) must be greater than or equal to 10
E1028	Maximum number of unit hydrograph ordinates exceeded	For a user specified unit hydrograph, the maximum number of ordinates is 1000. Also, check that it is positive.
E1029	Error - data interval too small for unit hydrograph calculation or Time to Peak	The number of unit hydrograph ordinates calculated (Tb/dt) exceeded 1000 - either the time base of the unit hydrograph is too large or the data interval is too small.
E1033	Incorrect percentage runoff code of 'x' in subroutine prcal	This indicates an error in setting Percentage Runoff (PR) flag or data for hydrological boundaries - check input data.
E1036	Storm return period of 'x' too small to estimate rainfall depth.	Storm return period must be at least 2-year for FSR and 1-year for FEH boundaries.
E1038	Areal reduction factor equation very inaccurate for durations less than 0.5 hr	A storm duration of at least half an hour is required for ARF calculations.
E1039	Water level below invert.	This indicates poor initial conditions, a data error or the onset of an instability.
E1042	HTBDY - No of data pairs must be > 1	Make sure that at least one H:T pair has been specified in the boundary.
E1044	Previous unit was not a RIVER or CONDUIT	The units immediately upstream and downstream of an INTERPOLATED section must be rivers or conduits (not a mixture).
E1045	It is not allowed to have interpolated sections here	It is not allowed to have interpolated sections between the following sort of geometrical conduits: Rectangular, Circular, Sprungarch, Fullarch. You should use REPLICATE instead of INTERPOLATE Labels involved: 'label1' 'label2' Regular-shaped (geometric) conduits may not be INTERPOLATED, but can be REPLICATED.
E1046	You must have a RIVER or CONDUIT downstream of INTERPOLATED sections	The units immediately upstream and downstream of an INTERPOLATED section must be rivers or conduits (not a mixture).
E1051	Format error in numerical data. JUNCTION data error	Check for typing errors in the junction labels at the line specified.
E1056	The direct method cannot be used with automatic controllers	The control module may not be used with the direct method - use logical rules (in MANUAL mode) for control, or pseudo-time stepping for steady-state runs.
E1057	Inconsistencies found in node labels	Number of errors found in node labels is 'x'. This message gives the total number of errors found following the network check. A description of the errors and the labels involved is displayed prior to this message. Possible causes of the errors include: Not obeying the labelling rules given in the documentation (e.g. labels existing not associated with two units; rivers not connected correctly); Incorrectly typed labels; Tabs in-between labels; Labels not left-justified in field widths of 12 (or 8 for old data files), or a mixture of the two; A steady results file has been used to provide initial conditions but the node labels have been altered; Incorrect node count on line 2 of the data file; Initial conditions section (separate file, or part of the of the dat file) is not complete, or contains too many labels.
E1065	Variable outside linearization range	The range of the data ('x1' to 'x') within the specified unit needs to be increased to include the current value of the variable 'x'. This message may also indicate the onset of instability if the value of 'x' is unrealistic. However, extending the range may be sufficient to overcome a temporary instability (e.g. allowing negative flow in a QHBDY).
E1066	Variable outside interpolation range	The range of the data ('x1' to 'x') within the specified unit needs to be increased to include the current value of the variable 'x'. This message may also indicate the onset of instability if the value of 'x' is unrealistic. However, extending the range may be sufficient to overcome a temporary instability (e.g. adding a Preissmann slot or increasing dflood).
E1072	rn must be greater than 1	The index (exponent) of head in the weir equation (user-input for general and notional weirs) must be greater than unity.
E1073	cd outside allowed range	The coefficient of discharge (user-input for general and notional weirs) must be greater than zero and less than 3.
E1074	cv outside allowed range	The coefficient of velocity must be greater than unity for a notional weir.
E1075	Weir breadth must be positive.	The breadth of the weir must be greater than zero.
E1079	Maximum no. of network iterations exceeded	The direct steady state solver was unable to solve the network in the specified number of iterations (default 25). A solution may be obtainable by improving the flow split estimates in the initial conditions or by using the pseudo time stepping steady method. The direct method temporary results are available by selecting this option from the Diagnostics tab on the 1D Simulation interface, and provide information of possible problem units; this also produces intermediate initial conditions in the zzd file which may also be imported and used as alternative splits. The number of direct method iterations can also be increased via the Backward compatibility tab on the 1D simulation interface, although it is unusual for a simulation to achieve convergence after more than 25 iterations.
E1080	Number of data points is less than 2.	A minimum of 2 data sets are required to define the river, bridge or conduit section or rainfall boundary data.
E1081	Number of data points is greater than maximum allowed.	A maximum of X data sets are allowed for defining the river, bridge or conduit section.
E1091	FULL ARCH CONDUIT. The height of the crown specified is too high.	A conduit arch takes the form of a section of a circle; therefore, its maximum height is restricted to half its width.
E1094	Reverse flows not valid in syphon spillways	Check that the downstream head can not realistically exceed the upstream head; if not, check the model schematisation, or an instability may be occurring. If it can, then consider an alternative way to model the situation.
E1095	Decreasing cross section distance found	The cross chainage data for a river section must not be less than that of the data line above (overhangs are not allowed)
E1096	Panel contains zero and non-zero Manning's n	Panels (those parts of the section separated by '*'s) must not contain a mixture of zero and non-zero 'n' values. Check the data for the RIVER SECTION which includes line 'l'.
E1097	Cross-section contains all zero Manning's n	All the 'n' values in the section are zero (zero conveyance) - this is not allowed.
E1098	Number of height points exceeds maximum	The maximum number of data points (400) + inserted extra points allowed for defining the river, bridge or conduit section has been exceeded.

Error Messages E1100-E1199

Error code	Message	Info / troubleshooting / details - what do I do to resolve!
E1100	Model is diverging. No solution has been found with the current time step	A very large (>10^16) matrix coefficient has been found - this indicates the onset of an instability. This is the earliest unit within the data file at which this error has been found - the source of the instability may be at this unit, or nearby. - improve initial conditions - decrease time step
E1105	Time-dependent data in unit doesn't cover the start time of the model duration	Model start time is before the first time specified in the time series for this unit. Extend the time data to cover the required run length. Check that the number of data sets is equal to that specified (n1).
E1106	Time-dependent data in unit doesn't cover the start time of the model duration	Model end time is after the last time specified in the time series for this unit. Extend the time data to cover the required run length or use EXTEND or REPEAT flags. Check that the number of data sets is equal to that specified (n1).
E1108	Tolerance for the direct method cannot be negative	A negative direct method tolerance has been specified in the datafile (General System Parameters) or 1D Simulation interface (Parameters tab).
E1109	Tolerance for the direct method cannot be greater than 0.1	A direct method tolerance greater than the maximum of 0.1 has been specified in the datafile (General System Parameters) or 1D Simulation interface (Parameters tab).
E1111	None of the labels in the initial conditions have been tagged.	Add a 'y' in the initial conditions section (column 14 [or 10 for old files] of the initial conditions section via a text editor) to indicate at which labels results are required. None of the labels in the initial conditions have been tagged. Add a 'y' in column 10 of the initial conditions to indicate at which labels results are required.
E1112	Number of labels in initial conditions does not match number in data file	The number of labels in the initial conditions does not equal the number specified in line 2 of the General System Parameters. If the cause of this error is not apparent then set the number of labels equal to those in the initial conditions and reply 'y' to the 'network check' prompt to obtain details of the labels involved. This error will also occur if the steady results file has been used to provide the initial conditions and the node labels have been changed following the earlier run.
E1113	Generic data read error	An error has been detected in line 'l' of the initial conditions. Check for non-numerical data after column 14 (10 for old files) of the initial conditions.
E1114	Data error in zzs file	An error has been detected in line 'l' of the '.zzs' file which is being used to provide initial conditions. Check for non-numerical data after column 14 (10 for old files) in the steady state results. If the data reads '**********', this indicates the calculated value was out of range.
E1115	Generic data read error	Check the data file for bad data (e.g. tabs and non-numerical data where numerical data is expected). Consult the Data Fields section in the Help for the unit in question for the expected format.
E1117	Data error. Lower Froude Number greater or equal to higher value	The higher Froude number specified (Parameters tab on the 1D Simulation interface, or line 2 of the General System Parameters) must be equal to or greater than the specified lower Froude number. The convective acceleration term in the momentum equation is altered between these two values when approaching critical flow.
E1118	Error in reader	Check that the number of nodes in the model is neither greater than the maximum licence allowed of 1000 nor negative. A premature end of file will also generate this error.
E1119	Previous unit was not a RIVER or CONDUIT	A replicate unit must be preceded by a river or conduit unit.
E1120	REPLICATE/INTERPOLATE must be preceded by a RIVER or REPLICATE with dx>0	The replicated or interpolated unit indicated followed a channel unit with zero chainage. This is not allowed - this unit is now at the beginning of a reach and there is nothing to replicate or interpolate. In the absence of any other data, you may choose to copy the section data from the section immediately upstream.
E1121	There is a spill label assigned to the last river unit in a reach.	A spill applies between the section to which it is attached, and the next section downstream. In this case, there is no downstream section.
E1123	Unit type may not be connected to reservoir at specified label	A reservoir is connected to another reservoir, junction or RNDSC - this is not allowed. Put a BERNOULLI LOSS, SPILL or RIVER/CONDUIT between the units as appropriate.
E1128	You must have at least two consecutive RIVERs or CONDUITs to form a unit.	Check that the unit following line 'l' is either a RIVER, CONDUIT, REPLICATE or INTERPOLATE section and that the keyword is correctly spelt. Also check that the distance to next cross section is nonzero for the current unit, which is the first in a reach.
E1129	It is not possible to find a solution with the current time step	A very large matrix coefficient has been found - this indicates instability. This is the earliest unit within the data file at which this error has been found - the source of the instability may be at this unit, or nearby.
E1131	Water level outside channel boundary	The direct steady solver has calculated a water level outside the channel boundary: check the channel data at 'label1' and 'label2'; improve the flow split estimates in the initial conditions; or use the pseudo time stepping method. This indicates an instability at this unit or just downstream (upstream if flow is supercritical, using the Direct Method Transcritical Solver); try examining the data here or add extra interpolated sections.
E1133	Extra added sections gave insufficient accuracy	This may be due to the water level exceeding the max level of section data. Try extending the section data. The direct steady method failed to solve the flow equations to sufficient accuracy. Check and/or extend the channel data at 'label1' and 'label2'; improve the flow split estimates in initial conditions; use the pseudo time stepping method. This error may also occur if extra BERNOULLI LOSS units are required; e.g. between a RIVER and CONDUIT unit. This indicates an instability at this unit or just downstream (upstream if flow is supercritical, using the Direct Method Transcritical Solver); try examining the data here or add extra interpolated sections.
E1139	no. of stage/gate opening datasets > 4.	Obsolescent tidal sluice units RNTRS/RNDSC only - the number of stage/gate opening data pairs must be between 2 and 10 inclusive.
E1159	Length of crest in direction of flow must be > 0.1 - rnweir data error	Increase the length of the round-nosed, broad-crested weir crest in the direction of flow to a minimum of 0.1m.
E1168	Unit not yet available with the direct method - run terminated	The units listed above this message are not available for the direct steady state method. Either substitute alternative units or use the pseudo time stepping method. This should not apply to any currently supported units.
E1169	Pump is in stopped mode; This mode is incompatible with the direct method.	The direct method cannot handle zero flow through in-line structures.
E1179	Remote upstream control not yet available. For use with the direct method.	Use pseudo-timestepping for steady runs, or time or logical control (in MANUAL mode) to control.
E1184	Third label required for WATER3 option for remote control mode	For 'water' mode the label for remote water level control must be specified after the two normal unit labels; alternatively, use logical rules.
E1185	Values given must be greater than zero	Either the operating rate or maximum opening has been set to zero, or the maximum setting is set less than the minimum.
E1188	No gate opening given for MANUAL operation	MANUAL mode has been chosen, but no setting has been given. Set a value in the control table.
E1189	No initial gate opening given for AUTO operation	Gates starting in AUTO mode used to require an initial setting (obtained from the control table). NB This should no longer be possible
E1195	Matrix structurally singular. iflag = -1	It may be caused by invalid model connectivity, inappropriate zero flow or zero coefficients otherwise obtained, e.g. by bad data not otherwise picked up. Details of labels involved can be obtained by responding 'y' to the 'network check' prompt.
E1196	Matrix numerically singular. iflag = -2	This message indicates mathematical indeterminacy, caused by the solution matrix being singular (non-invertible). This may be caused by an unexpected or temporary area of zero flow altering the structure of the matrix. This can often be resolved by setting the Matrix Dummy Coefficient (Parameters tab on the 1D Simulation interface) to a small number, e.g. 0.001 or lower. This will preserve the intended structure of the matrix and make it less likely to be singular, whilst having a negligible effect on the solution. No information on error source given Can be associated with structure mode shifts
E1197	Row or column index out of range. iflag = -12	This error indicates an inconsistency in the model network connectivity. Details of labels involved can be obtained by responding 'y' to the 'network check' prompt.
E1198	Dir = 'x' reverse flow direction hn1 = 'y' hn2 = 'z' node = 'n'	The direct steady method has calculated a flow reversed on a spill and has not been able to continue computations. A solution may be obtainable by improving the flow split estimates in the initial conditions or by using the pseudo time stepping steady method.
E1199	Error in spill at line 'l'. bank chainage must increase for each data pair	If a vertical spill section is required use a small increment to the chainage (eg 0.01m).

Error Messages E1200-E1299

Error code	Message	Info / troubleshooting / details - what do I do to resolve!
E1200	Maximum gate opening MUST be less than radius plus height of pivot	This opening is not physically possible - check the maximum gate settings and gate dimensions.
E1201	Gate opening MUST be less than radius plus height of pivot	This opening is not physically possible - check the maximum gate settings and gate dimensions.
E1202	Gate radius MUST be greater than height of pivot	A radial sluice unit must be dimensioned so that the gate can fully shut if required, this the radius must be greater than or equal to the height of pivot above weir crest. Check the dimensions of the gate, or consider an alternative method (e.g. an orifice unit in parallel or a nonzero minimum setting) if permanent undershooting is required.
E1203	Number of data points in SPILL unit must be must be greater than 1	Check the spill data and add more data points.
E1210	Negative flow specified at a Q:T boundary - this is not permitted	Change the schematisation to allow a positive Q:T or use the pseudo time stepping steady method
E1211	Perturbation matrix is singular	The direct steady method has detected a mathematical singularity - this is often caused by zero flows. A solution may be obtainable by: removing the zero flow reach slightly opening closed sluice gates using the pseudo time stepping steady method
E1219	cv outside allowed range	The coefficient of velocity specified for a general purpose weir unit must be between unity and 1.5 inclusive.
E1221	rlimit outside allowed range	The modular limit specified for a general purpose weir unit must be between zero and unity inclusive.
E1230	Suter pump - numerical data outside allowable range	Allowable number of characteristics per stage is between 1 and 50 inclusive.
E1234	Generic error - see zzd file for further information	Generic error code used for problems that would cause Flood Modeller to crash, usually due to a potential mathematical error. For example, the code would appear if the breadth of a weir was set to a negative value The solution is dependent on the particular error, which is detailed further in the error text.
E1237	SAAR must be positive for event rainfall calculation	Consult the appropriate handbook or software (e.g. FEH) for an appropriate SAAR (Standard Average Annual Rainfall) value.
E1238	Event Rainfall flag is expected to be OBSER, FEHER, FSRER, or PMFER	The correct rainfall flag will be set by choosing the correct option in the User Interface. If editing in a text editor, consult the Data Fields section for the Hydrological Boundary for the correct format.
E1239	Positive non-zero value is expected for the OBSERVED event rainfall	An observed event rainfall has been entered, but no rainfall depth set. This must be entered, and should be equal to the sum of the rainfall profiles (if user-input profile chosen; Tip: enter the rainfall profile in the table and select OK - the warning message will advise of the sum of the rainfall values, which can then be entered in the rainfall depth box).
E1241	Catchment Wetness Index flag is expected to be OBSCW, FSRCW or PMFCW	The correct CWI flag will be set by choosing the correct option in the User Interface. If editing in a text editor, consult the Data Fields section for the Hydrological Boundary for the correct format.
E1243	Percentage Runoff Flag is expected to be BSPR, FEHPR, FSRPR or F16PR	The correct PR flag will be set by choosing the correct option in the User Interface. If editing in a text editor, consult the Data Fields section for the Hydrological Boundary for the correct format.
E1244	Error in OBSERVED percentage runoff, it must not be > 100.0	An FSR/FEH boundary has been used with Observed PR (percentage runoff), which was set greater than 100. Check the data input.
E1245	Error in OBSERVED percentage runoff, it must not be <0.0	An FSR/FEH boundary has been used with Observed PR (percentage runoff), which was not set, or was set negative. Check the data input.
E1246	Time to Peak Flag is expected to be OBSTP, FEHTP, F16TP, FSRTP or R124TP	The correct Tp flag will be set by choosing the correct option in the User Interface. If editing in a text editor, consult the Data Fields section for the Hydrological Boundary for the correct format.
E1247	Positive non-zero value is expected for the OBSERVED Time to Peak, TP	An FSR/FEH boundary has been used with Observed Tp (time-to-peak), which was not set, or was set negative. This is not allowed. Check the data input.
E1248	Positive non-zero value is expected for the Calibration factor of TP	An FSR/FEH boundary has been used with a zero or negative Tp (time-to-peak) calibration factor. Since this is a multiplicative factor, it must be positive. Check the data input.
E1249	Base Flow Flag is expected to be OBSBF or F16BF	The correct BF flag will be set by choosing the correct option in the User Interface. If editing in a text editor, consult the Data Fields section for the Hydrological Boundary for the correct format.
E1250	Positive non-zero value is expected for the catchment area, carea	Consult the appropriate handbook or software (e.g. FEH) for the appropriate catchment area.
E1253	Unit Hydrograph Flag is expected to be OBSUH, FSRUH, UBRUH or SCSUH	The correct UH flag will be set by choosing the correct option in the User Interface. If editing in a text editor, consult the Data Fields section for the Hydrological Boundary for the correct format.
E1255	Rainfall Profile Flag is expected to be OBSRP, WINPMP or SUMPMP	The correct rainfall profile flag will be set by choosing the correct option in the User Interface. If editing in a text editor, consult the Data Fields section for the Hydrological Boundary for the correct format.
E1256	Number of rainfall values outside range	Check that the number of rainfall values in an observed rainfall profile is greater than zero. The maximum is 4601 - check that this is not exceeded; if it is, consider increasing your time interval, splitting up your simulations or select an alternative hydrological method.
E1258	ERROR in calculated percentage runoff at subroutine prcal, it is > 100.0	Percentage runoff is calculated from a combination of SPR and dynamic PR. An unrealistically high value of CWI or total precipitation, or a high value of SPR may cause this to exceed 100. Check these values and refer to the documentation for further
E1262	Error in routine interp in fsrqt - value out of range	The FSR (and FEH) methods interpolate values for Storm Return Period (from Flood Return Period), CWI (from SAAR) and two year growth factor (from m5 rainfall). It is likely that one of these values is out of range.
E1266	Calculated no of unit hydro. Ordinates is greater than max allowed	The number of hydrograph ordinates after convolution has exceeded the maximum, due to either too many unit hydrograph ordinates or rainfall profile values.
E1267	For SUMRP unequal return periods are unacceptable. This can, however, be forced by using the parameter FORCE.	For FSR/FEH boundaries, the summer flood and storm periods should be set equal. This can be relaxed by not selecting 'FORCE' equal return periods.
E1268	Invalid Velocity Flag specified	Velocity calculations in MUSKINGUM units should be calculated using the keyword VQ POWER LAW, VQ RATING or VQ SECTION.
E1269	Power law constants cannot be negative	The constants in the Power Law relationship, a, b, V0 and Q0, may not be negative.
E1285	Reservoir/Pond level is lower than or the same as the previous level	The elevations in a reservoir or pond unit should be entered in ascending order. Otherwise, inconsistencies in interpolating areas/volumes may occur. Check input data.

Error Messages E1300-E1399

Error code	Message	Info / troubleshooting / details - what do I do to resolve!
E1301	No flow boundaries have been defined therefore direct steady method is not applicable	The direct method requires a QT-type boundary at each upstream branch end of the model
E1302	No head boundaries have been defined therefore direct steady method is not applicable	The direct method requires a HT/QH-type boundary at each downstream branch end of the model
E1324	Number of q:h data pairs exceeds the maximum permitted	A QHBDY or QH control unit may contain a maximum of 500 Q:H data pairs.
E1330	Efficiency values must be greater than zero and less than or equal to one	User input value of optimal efficiency, 'e', for the PUMP unit must be positive and no greater than 1.
E1331	Optimal head and flow values must both be positive	User input values of optimal flow, 'q', and head, 'h', for the PUMP unit must be positive.
E1332	Number of switch data sets must be > 1	This applies to the PUMP unit - ensure that the number of time control values is at least two.
E1333	Invalid switch type keyword	Control method for pumps must be TIME, LOGICAL or CONTROLLER
E1334	Unrecognised pump mode keyword	Valid PUMP modes can be only ON, OFF, STOPPED or OPEN
E1336	Missing control label for controller switch type	When using controller mode (PUMP unit), the controller label field must be used
E1338	Time multiples must be positive	Invalid time unit keyword, 't', entered, or user defined time multiplier 'i' is zero/negative (PUMP, SLUICE or GATED WEIR units)
E1339	Unrecognised pump mode	A bad pump mode 'm' has been set. Valid modes are 0-2 and 10-14. This should not be possible, but could occur if the initial condition mode is invalid.
E1340	Number of Suter points must be between 1 and 133	The number of calculated points, 'n', on the pump curve exceeds the maximum. This may be caused by too many user-input points. A maximum of 89 extra points are extrapolated using Suter's method, leaving at least 44 user-input data sets available.
E1341	No corresponding pump mode given for MANUAL operation at model time	No operating mode was given in the PUMP control table when in MANUAL mode.
E1343	Number of head, flow, efficiency data sets must be between 1 and 50.	The number of user-input flow-head-efficiency data sets exceeds the maximum (now 133). Note that the effective maximum is considerably less, otherwise error E1340 is likely to be flagged.
E1344	Error reading data in datafile.	Data read error in flow-head-efficiency table for PUMP unit. Most likely caused by non-numeric characters present in the field
E1345	Head, flow and efficiency cannot all be simultaneously greater than zero.	Head and flow values have been input as greater than zero; efficiency is greater than 1. This is not permitted.
E1346	Invalid number of switch data sets	Number of time control data sets, 'n', in the pump unit is less than one - at least one must be added to the control table.
E1347	Unknown switch type: type code	Control method for pumps must be TIME, LOGICAL or CONTROLLER
E1348	Unable to find control unit for controller mode	No control unit existed associated with the controller label 'c'. (PUMP unit)
E1349	Unknown instruction code for logical switching	Instruction to operate a pump in logical rules must be 'PUMP'. Instruction 'a' supplied.

Error Messages E1400-E1499

Error code	Message	Info / troubleshooting / details - what do I do to resolve!
E1401	Skew angle of bridge > 45 ; Must be in range 0 < =angle < =45.	Skew angle for USBPR bridge must be less than 45 degrees. Check input data.
E1402	Width of bridge< =0.0. Data error in bridge unit	Distance between faces of dualled bridge (Arch or USBPR) is input as zero - this is not allowed. Check "Bridge Width" input data.
E1403	Invalid bridge abutment code. Should be 1, 2 or 3. Data error in bridge attached to 'label1', 'label2'	Check USBPR bridge 'Abutment Type' input data.
E1404	Pier coefficient out of range. Must be >=0.0 and < =8.0. Data error in bridge	Invalid pier calibration number (USBPR bridge - Pier Data). Must be between 0 and 8.
E1405	Invalid bridge pier description. 'x'(Number of piers), 'y' (type of shape of bridge soffit), 'z' (type of bridge pier cross sectional type). Data error in bridge attached to 'label1', 'label2'.	Invalid shape description (USBPR bridge - Pier Data). See USBPR section in Help for valid combinations.
E1406	Number of bridge piers >0 , with Width of bridge piers < =0.	Pier width must be positive if piers are specified (USBPR bridge - Pier data)
E1410	Too many culverts in bridge attached to 'label1','label2'.	Maximum number of flood relief culverts in a USBPR bridge is 20.
E1411	Culvert drowning coefficient must be <1. Data error in bridge attached to 'label1','label2'	Check USBPR bridge Flood Relief Culvert data
E1412	Culvert invert level is greater than soffit level. Data error in bridge attached to 'label1','label2'.	Check USBPR bridge Flood Relief Culvert data
E1421	Number of arches < 0	The number of arches in a bridge unit has been set negative - check the data file at line 'l'.
E1422	Number of arches exceeds the maximum	The current maximum number of arches in a bridge unit is 25.
E1423	USBPR Bridge error on arch data 'x' (number of arch) x coord of left side of arch must coincide with cross chainage point	USBPR Bridge error on arch 'x' (number of arch) x coord of left side of arch must coincide with cross chainage point. The cross chainage value for the bridge opening must also be present in the bridge section data (i.e. the arch must be sprung from a point directly in vertical line with a cross-section data point).
E1431	Too many markers in bridge channel section	Left and right embankment markers have been specified more than once for the same bridge section - this is not allowed.
E1432	Left or Right markers wrong in bridge section.	Left and right embankment markers are the wrong way round, or only one of them has been set.

Error Messages E1500-E1599

E1510	Unrecognised direction keyword keyword should be UPSTREAM or DOWNSTREAM	Only UPSTREAM and DOWNSTREAM are allowed keywords for the CULVERT BEND/ GENERAL HEAD LOSS unit.
E1511	Invalid loss coefficient: Loss coefficient must be value between 0 and 10.	The loss coefficient for the CULVERT BEND/ GENERAL HEAD LOSS unit must be in the range 0-10; advisory warnings appear if the value is above 1 (general) or 0.5 (bend)
E1512	Upstream section for a BEND/LOSS unit in upstream control must be a RIVER or CONDUIT unit.	The CULVERT BEND/ GENERAL HEAD LOSS unit needs to be able to calculate flow areas at the unit in the control direction, so this unit must be a channel section. Use remote nodes if this is not connected directly to such a unit.
E1513	Invalid loss coefficient: Loss coefficient should be value between 0 and 1.	Invalid value given for the loss coefficient for a CULVERT OUTLET unit
E1514	Unit upstream of a CULVERT OUTLET unit must be RIVER or CONDUIT unit.	The CULVERT OUTLET unit must be at the downstream end of a properly formed reach of CONDUIT units. This is so that flow areas and velocities within the culvert barrel can be calculated. Use remote nodes if this is not connected directly to such a unit.
E1515	Unrecognised conduit type code. Should be A or B	This code determines the equations used in submerged inlet control. Only Type A or Type B is valid. Please refer to the Culvert Inlet topic for more information.
E1516	Value of unsubmerged inlet control loss coefficient should be between 0 and 1; current value is x	Invalid value given for the unsubmerged inlet control loss coefficient for a CULVERT INLET unit.
E1517	Value of exponent for inlet control should be between 0 and 3; current value is:x	Invalid value given for the unsubmerged inlet control for a CULVERT INLET unit.
E1518	Value of submerged inlet control loss coefficient should be between 0 and 0.1; current value is x.	Invalid value given for the submerged inlet control loss coefficient for a CULVERT INLET unit.
E1519	Value of submerged inlet control adjustment factor should be between 0 and 1; current value is x	Invalid value given for the submerged inlet control adjustment factor for a CULVERT INLET unit
E1520	Value of outlet control loss coefficient should be between 0 and 1; current value is x	Invalid value given for the outlet control loss coefficient for a CULVERT INLET unit
E1521	Value of trash screen width should be greater than 0; current value is x	Invalid value given for the trash screen width for a CULVERT INLET unit.
E1522	Value of trash screen bar proportion should be between 0 and 1; current value is x.	Invalid value given for the trash screen bar proportion for a CULVERT INLET unit. This number represents the proportion of the total trash screen area that is occupied by the bars.
E1523	Value of trash screen blockage ratio should be between 0 and 1; current value is x.	Invalid value given for the trash screen blockage ratio for a CULVERT INLET unit. This number represents the proportion of the trash screens total area that is blocked by debris.
E1524	Value of trash screen head loss coefficient should be greater than 0; current value is x	Invalid value given for the trash screen head loss coefficient for a CULVERT INLET unit.
E1525	Unit downstream of a CULVERT INLET unit must be a RIVER or CONDUIT unit.	The CULVERT INLET unit must be at the upstream end of a properly formed reach of CONDUIT units. This is so that flow areas and velocities within the culvert barrel can be calculated. Use remote nodes if this is not connected directly to such a unit.
E1526	Maximum number of trans-critical points exceeded	The maximum number of trans-critical points (super-subcritical and sub-supercritical transitions) for the Direct Method Trans-critical Solver is 50. The 51st such point occurred between nodes l1 and l2.
E1528	Junction at l1 appears to be neither a join nor a split	This should not be possible. If it occurs, check the connectivity of the junction at node l1.
E1529	Unable to find unit number in list of river reaches	This should not be possible. If it occurs, check the nth unit of the model (labels l1 and l2) - this should be a channel unit.
E1530	Internal error - invalid trans-critical point	This should not be possible. If it occurs, please the support team.
E1532	Upstream/downstream nodes of unit are not rivers/conduits.	Direct supercritical method cannot handle this try adding a dummy reach at either end. Supercritical flow has occurred in the Direct Method Trans-critical Solver at two consecutive non-channel units at node l1 - a dummy reach needs to be inserted between them for the method to work.
E1533	Cannot find label	The adjoining unit at the end of a reach cannot be found. Check the connectivity at label l1.
E1534	Save interval (or timestep) must be positive	A zero or negative save interval (interval at which results are saved) or timestep has been entered - check the 1D Simulation interface or the ief file.
E1536	Upstream/downstream/remote/constriction section label does not exist.	The remote node label (or reference node label for a blockage unit) does not exist - check that it exists in the network. Pay attention to case (1D node labels are case sensitive).
E1537	Upstream and/or downstream river units at bridge not found	Upstream label used = l1; downstream label used = l2; use remote nodes if river units are not adjacent to the bridge. Check the connectivity of the bridge unit in question - a bridge must be connected directly (1st/2nd labels) or remotely (3rd/4th labels) to channel units, from which to obtain areas, and hence velocities. If the nodes up/downstream are not channel units, use remote nodes.
E1538	Culvert flow failed to converge	Could not find a solution for the flood relief culvert flow within a bridge.
E1539	Perturbation failed	Direct method could not find a solution at the qh control or pond unit. Try adjusting the flow splits in the initial conditions.
E1540	No nodes found	No nodes present in the model - this message can appear only if the 'write Unit Data Store' option is chosen, and should not in fact be possible.
E1541	Country must be ENGLAND, IRELAND, SCOTLAND or WALES	The FSSR16 unit must specify either ENGLAND, IRELAND, SCOTLAND or WALES as the country - the method applies only to UK/Ireland. For other countries, the US SCS method may be considered.
E1542	Value of s1085 must be positive for time to peak calculation	S1085 (stream slope measurement) must be positive - used in time to peak calculation for FSSR16 unit.
E1543	Value of MSL must be positive for time to peak calculation	MSL (main stream length measurement) must be positive - used in time to peak calculation for FSSR16 unit.
E1543	Value of DPSBAR/DPLBAR must be positive for time to peak calculation, or PROPWET must be between 0 and 1.	Invalid catchment descriptor as used in an FEH unit - either DPLBAR, DPSBAR are zero or negative, or PROPWET is outside the range 0-1 (see individual error text for details)
E1544	SOIL must be between 0 and 1.0	Obsolescent FSR unit only - invalid SOIL value entered.
E1545	Time step must be positive	Time interval for hydrological boundary is entered as zero or negative. Check the unit form or data file.
E1546	Urban fraction/extent cannot be <0 or> 1	Invalid value entered for Urban Fraction (FSSR16) or URBEXT (FEH/ReFH) - must be between 0 and 1.
E1547	Storm duration of x is less than or equal to zero	A zero or negative storm duration has been entered for a hydrological boundary.
E1548	[Time] interpolation error	Error in the multipurpose interpolation routine used for hydrological boundaries caused by the reference table (for the independent variable) having two equal values.
E1549	INTERPOLATE unit must have a positive chainage	An INTERPOLATE unit has been entered with zero or negative chainage (distance to next cross section) - this is not permitted - an INTERPOLATE unit cannot terminate a reach.
E1550	A reach has more than 100 interpolated sections (split the reach using a RIVER)	There can not be more than 100 consecutive INTERPOLATE units. If more are needed, then replace one with a RIVER unit with appropriate section.
E1551	Numb=0 in INTERPOLATE	This should not be possible - this should equal the number of consecutive INTERPOLATE units.
E1552	Total chainage must be positive	The total [cumulative] chainage of consecutive INTERPOLATE units is zero or negative - this is not allowed.
E1555	Unit type may not be connected to junction	A junction may not be connected directly to another junction or a reservoir. Combine the nodes into a larger junction or insert a dummy reach/unit between the two.
E1562	dx must be positive	A dx value has been assigned, and discovered in the 2d or sediment module. This should have been trapped previously.
E1564	X number of data points is less than 2	Less than two points have been entered in the wave speed/attenuation data table (VPMC only) or the VQ rating table in any Muskingum unit.
E1565	X number of data points greater than maximum	The maximum number of points (currently 452) has been exceeded in the wave speed/attenuation data table (VPMC only) or the VQ rating table in any Muskingum unit.
E1566	Lateral inflows cannot be used with MUSKINGUM units	Lateral inflows are not allowed with MUSKINGUM fixed (i.e. not VPMC, XSEC or RSEC) units. NB This error code also appears if a lateral inflow is connected to the last section of a reach.
E1567	Zero wave speed or chainage Ensure that the reach is not dry	This error occurs in calculating Muskingum VPMC routing parameters. It may be alleviated by selecting a nonzero smoothing factor, so that the wave speed is always positive.
E1568	Slope must be positive	This may occur in a MUSX-XSEC unit (channel slope), or a Flat-V weir unit (V-slope), neither of which is allowed to have a zero slope.
E1569	Channel section data error. At least 2 section points and a positive slope are required for velocity calculation	This occurs in a MUSK-XSEC unit with a VQ SECTION velocity calculation if there are less than two section points or a zero/negative slope (a positive slope is required for normal depth).
E1570	Attempt to read results from before start of run. Start your run with structure in MANUAL mode	When using rules based on previous results (OLD), the historic time referred to by the OLD function preceded the model start time, and the condition is therefore not available. One must use the affected units in MANUAL mode (or use alternative rules for this period) for a time greater than or equal to the greatest time amount looked back, i.e. if OLD* references a condition 900s ago, the rules must not take effect until 15 minutes into the simulation.
E1571	Error attempting to read earlier result	Generic read error from zzn file in accessing results for rules based on previous results (OLD*). The zzn file may be corrupt.
E1572	Unrecognised operation type	Invalid operator for rules based on previous results (OLD*). Valid operators are OLDH (head), OLDF (flow), OLDM (mode) and OLDS (unit state). Check the rules syntax.
E1573	Weir discharge coefficient must be greater than 0	Weir discharge coefficient was set zero or negative in a PUMP (in open mode), ORIFICE or SYPHON unit.
E1574	Surcharged discharge coefficient must be greater than 0	Surcharged discharge coefficient was set zero or negative in a PUMP (in open mode), ORIFICE or SYPHON unit.
E1575	Pump bore area must be greater than 0	Bore area was set zero or negative in a PUMP (in open mode), ORIFICE or SYPHON unit.
E1576	Soffit must be higher than invert	The soffit level was set higher than or equal to the invert level in a PUMP (in open mode), ORIFICE or SYPHON unit - this is not allowed.
E1577	Bridge soffit is more than 10m above cross section. Please extend your section data or modify the arch dimensions	The soffit of the bridge is not allowed to exceed the bridge section data by more than the input parameter dfloodb (default 10m). This is to allow section properties to be interpolated at a reasonable resolution. One can add extra depth to the section data by adding extra points at the left and right extremities and extending them vertically.
E1578	icount is zero - arch error	This should not be possible - this should be the number of section data points contained underneath an arch. Check that the arch is sprung from a point directly above existing section data.
E1579	Conduit section should start with x=0 at invert centre line	The first and last point of a (symmetrical) CONDUIT SECTION must both be at x=0. If required, one can use the Modify tool in the unit form to add/subtract a constant value from a table of (x-)values.
E1580	Unrecognised time factor keyword	An invalid time factor keyword or a zero/negative time multiplier was entered for the time units. Common valid keywords are 'SECONDS', 'MINUTES', 'HOURS', 'DAYS'. See the data fields section for the relevant unit for a full list.
E1581	Flood Modeller has detected a different label length in the initial conditions file from the value in operation in the datafile. This is not allowed	This can occur if using a model data file (default label length 12) with initial conditions from an old model (label length 8), or vice versa. It is recommended to convert all models to label length 12. To convert a model data file from length 8 to length 12, start with a blank file in the User Interface, use the Load 1D Network in the Home tab and save. The new imported model will automatically become a 12-character length label model. To convert an initial conditions file from length 8 to length 12, ensure that the header reads 'label12', as opposed to 'label', and insert four blank spaces between each node label and the 'y' tag; note that the 'y' tag should now be in the 14th column.
E1582	Maximum number of pond data lines exceeded (max=50)	A maximum of 50 elevation/area data pairs are currently allowed in the POND unit.
E1583	INTERPOLATE must be preceded by a RIVER or REPLICATE with a positive chainage	The preceding channel unit has a chainage (distance to next cross section) value of zero. This is not allowed (nothing to interpolate). Check the connectivity of your model, and that a positive chainage was entered in the preceding section unit.
E1584	Non-channel unit found in the middle of a reach. Reach must end with dx = 0	The last section unit in the reach had a nonzero distance to next cross section value. The last section of a reach (i.e. before a structure, boundary or junction is encountered) must have a distance to next cross section value of zero.
E1585	Length of weir in direction of flow is more than 100 x width of crest. This is not acceptable	The length of the weir has exceeded the breadth by a factor of 100 or greater. This invalidates the limits of applicability, and is also unlikely. Check that the correct dimensions for each has been entered.
E1586	Crest length must be positive	A zero or negative length has been entered for the weir - check inputs.
E1587	Unknown controller operation mode	Control sub-mode within LOGICAL or CONTROLLER mode must be either 'AUTO' or 'MANUAL'. Check inputs.
E1588	Unknown sluice gate operation mode	Invalid control mode detected - must be 'TIME', 'LOGICAL', 'CONTROLLER', 'WATER1', 'WATER2' or 'WATER3'.
E1589	No time data available in switch data set for current model time	The model time is not covered by the times in the control table. Ensure that the times within encompass all the simulation run time. Use the EXTEND flag if necessary.
E1590	Unable to find controller label for controller mode	Controller label referenced by unit in CONTROLLER mode is not found in the control file.
E1591	Unknown controller operation mode	Invalid control mode found - should be CONTROLLER or LOGICAL (MANUAL or AUTO).
E1592	Error in floodplain section at line n. Chainage must be positive for friction flow	Friction flow has been specified for a FLOODPLAIN SECTION unit, but the chainage was entered as zero. A positive chainage is required for the slope, in order to calculate friction flow.
E1593	First matrix element is zero	This occurs in the spline interpolation module, and is most likely caused by a non-increasing independent variable. Check that all these values are in strictly ascending order.
E1594	Xset points are not all distinct	This occurs in the spline interpolation module by having non-distinct values of the independent variable close to the current point in question (x3). The range of the independent variable is x1-x2, and there are n points in the table. This information may assist in identifying the table being interpolated.
E1595	Gate orientation must be FORWARD or REVERSE	Invalid keyword entered for the GATED WEIR unit orientation - this must be 'FORWARD' or 'REVERSE'. Check inputs.
E1596	ctc must be greater than 0	Discharge coefficient for throat control in a GATED WEIR unit has been entered as zero/negative. Check inputs.
E1597	cgt must be greater than 0	Discharge coefficient for gate control in a GATED WEIR unit has been entered as zero/negative. Check inputs.
E1598	crev must be greater than 0	Discharge coefficient for reverse flow in a GATED WEIR unit has been entered as zero/negative. Check inputs.
E1599	dr must be greater than 0	Modular limit in a GATED WEIR unit has been entered as zero/negative. Check inputs.

Error Messages E1600-E1699

Error code	Message	Info / troubleshooting / details - what do I do to resolve!
E1600	Only one gate is allowed in gated weir	Currently in a GATED WEIR unit, only one gate is allowed per unit. To connect more gates in parallel, copy the unit and connect multiple units at their upstream and downstream ends via junctions.
E1601	Gate height must be greater than zero	Gate height in a GATED WEIR unit has been entered as zero/negative. Check inputs.
E1602	Gate crest higher than max. gate height	Input or calculated gate crest level has exceeded the maximum level of the gate for a GATED WEIR unit. Check user input opening values, and also maximum gate opening.
E1603	Crest is lower than sill	Input or calculated gate crest level is below the sill for a GATED WEIR unit. Check user input opening values, and also minimum gate opening.
E1605	Unit version number n is not supported in this version of Flood Modeller	The version number for the Unit in the data file is newer than the version of Flood Modeller being run. You'll need to download a newer version of Flood Modeller.
E1606	Negative breach width xm is invalid	User has entered a negative width of x in the BREACH units. Check inputs.
E1607	Negative breach side slope x is invalid.	User has entered a negative slope of x in the BREACH units. Check inputs.
E1608	Error in breach: unable to fit breach, check the breach and associated spill section	An extension of the breach geometry (either at the left or right end) does not reach the spill geometry, thus a breach cannot be formed from the original spill unit. Check the dimensions of the breach and spill unit.
E1610	Invalid blockage proportion x. Proportion p must have 0.0 < = P <=1.0	An invalid blockage proportion has been entered. Note that the valid range is 0 to 1. Check inputs.
E1611	Upstream/Downstream/Constriction unit of a blockage (connected or remote) must be RIVER, CONDUIT or BRIDGE unit.	In order to calculate velocities, units connected to a blockage unit must have an area, i.e. be section units. If this is not the case for the units connected directly, appropriate units may be connected remotely (3rd, 4th and 5th labels) from which to obtain areas.
E1612	Invalid loss coefficient: Loss coefficient must be at least 0.	A negative value for the loss coefficient has been entered for the blockage unit. Check inputs.
E1613	OPEN pump operation is specified but parameters for OPEN operation are not set	Pump mode has been specified as being in OPEN mode, but the input or calculated mode is not 'OPEN' (or a valid open mode numeric 10-14).
E1614	Selected node l1 for OLD rules has been removed from the output list	The node label l1 is not in the results list. Check that the node exists in the model and that its tag is set to 'y' in the initial conditions.
E1620	Unit not supported in this version of Flood Modeller	The version number for the Unit in the data file is newer than the version of Flood Modeller being run. You'll need to download a newer version of Flood Modeller.
E1621	Invalid lateral inflow weight factor (= x) entered for connecting unit	Error in lateral inflow unit - the area or reach weight factors must be positive and sum up to one, therefore a negative value or a value exceeding one is not permitted.
E1622	User defined weight factors do not sum to 1.0	Error in lateral inflow unit - the area or reach weight factors must be positive and sum up to one (or less than one if only partially using weight factors).
E1623	Unrecognised connecting boundary node entered	The node attached as the inflow to the lateral inflow unit must be an inflow or rainfall-type boundary.
E1624	Link to lateral inflow not recognised	Check connectivity of the lateral inflow unit and lateral nodes.
E1625	Reservoir connected to reach - weighted lateral inflow	A lateral inflow into a reservoir unit may not be weighted by reach length - change the weighting method in the lateral inflow unit to area or user defined, or override for this node only using a user defined (custom) weighting.
E1627	Connected Muskingum has zero reach length	A lateral inflow has been connected to a Muskingum unit of zero length, i.e. the last section in a reach. This is not allowed, since the inflow is applied to the length immediately downstream of the section. One needs to attach the lateral inflow to the section at the upstream end, or remove it.
E1628	Weight factor type not recognised	The weight factor keyword must be one of 'REACH', 'AREA' or 'USER', to denote whether the weighting of the lateral inflow is determined by relative length of reach, surface area (e.g. for rainfall) or user-specified, respectively. Check inputs.
E1629	Muskingum section connected to area distributed lateral	A lateral inflow connected to a Muskingum unit cannot be weighted by area - this is because the width, and hence surface area of a Muskingum unit is not generally known.
E1630	This Muskingum type will not receive lateral inflows	Lateral inflows are not allowed with MUSKINGUM fixed (i.e. not VPMC, XSEC or RSEC) units.
E1631	Zero reach length river section connected to lateral inflow	A lateral inflow has been connected to a channel unit of zero length, i.e. the last section in a reach. This is not allowed, since the inflow is applied to the length immediately downstream of the section. One needs to attach the lateral inflow to the section at the upstream end, or remove it.
E1640	Number of data pairs must be greater than zero	No rainfall/time data pairs have been entered in the table for a Rainfall-Evaporation boundary (REBDY) unit.
E1641	No input data types recognised	Rainfall-type boundary does not have any of the following specified: Rainfall, Evaporation, Evapotranspiration or Infiltration. Data for at least one of these must be present.
E1642	No data in l1 at line n before/after x hrs	The rainfall input data does not exist at the specified simulation time. Ensure that the rainfall data encompasses the start and end time of the simulation, using the EXTEND/REPEAT functionality if desired.
E1643	2 data points with same time	Two rainfall data points have been input with the same time. This is not allowed. Check input data.
E1644	Time values are not increasing	The data in an REBDY are not in ascending time order. Check input data.
E1669	Zero or Negative slope encountered in Normal depth boundary This is not permitted	A positive slope is required in order to calculate normal depth. This can be overcome by entering a user-defined slope value, or using a remote slope node (4th label) so that the mean slope is positive (i.e. downhill).
E1672	Remote label not found or not connected to a channel section	The remote node label (3rd label) in an NCDBDY unit, if specified, must be of a channel type, from which to calculate conveyance.
E1673	No valid path found from upstream to downstream slope extents	The upstream slope extent (4th label) in an NCDBDY must be connected by a single direct route to the downstream section. If there are alternative routes (e.g. the network is branched in between) or the route is complex, the user may be advised to enter a user-specified slope value.
E1674	No section data specified or available for normal/critical depth boundary	Section data has been specified for the geometry of an NCDBDY but is empty, or the node is not a channel unit. Make sure the data is entered if specified, or that the node (or remote node) is coincident with a channel unit
E1675	Zero area or width in Critical depth boundary	A zero area or width has been detected in the NCDBDY critical depth boundary. Critical depth is not possible. This may be because the channel has run dry, or a conduit is running full.
E1676	No sign change detected in normal depth equation. Normal depth could not be calculated	No solution could be found for the normal depth equation. Normal depth may be higher than the top of the section data. Check the section data and extend if necessary; this may also be a sign of model instability.
E1678	Data error at line n. Dry lower depth greater or equal to dry higher depth	The lower depth limit used to relax the convective acceleration term in the momentum equation has been entered as higher than the upper limit. Check the input run parameters (low flow options).
E1680	Maximum number 50 of lateral connections for quality run exceeded	A maximum of 50 lateral inflow connections are permitted for a hydraulic simulation for 1D Quality. This is due to the maximum capacity in the 1D Quality connectivity.
E1681	Data error at line n. no RAD FILE tag found	The 'RAD FILE' line is not present in the GENERAL section at the top of the data file. This is required for CES simulations. Ensure the data file is saved as being v2.2. compatible, or later.
E1682	Data error at line n. no GENERAL tag found	The 'GENERAL' line is not present in the GENERAL section at the top of the data file. This is required for CES simulations. Ensure the data file is saved as being v2.2. compatible, or later.
E1683	Failed CES dll function call to SetRoughnessFile	Failed to load the SetRoughnessFile function in convey.dll. Check that the Flood Modeller and CES versions are compatible, and that convey.dll is present in the FloodModeller/bin folder or on the system path.
E1684	Failed CES dll function call to GetRoughnessLoadingErrors	Failed to load the GetRoughnessLoadingErrors function in convey.dll. Check that the Flood Modeller and CES versions are compatible, and that convey.dll is present in the FloodModeller/bin folder or on the system path.
E1685	Failed CES dll function call to AddSection	Failed to load the Add Section function in convey.dll. Check that the Flood Modeller and CES versions are compatible, and that convey.dll is present in the Flood Modeller/bin folder or on the system path.
E1686	Failed CES dll function call to Populate Section for section id	Failed to load the Populate Section function in convey.dll. Check that the Flood Modeller and CES versions are compatible, and that convey.dll is present in the Flood Modeller/bin folder or on the system path.
E1687	Failed CES dll function call to Add Section Roughness for section id	Failed to load the Add Section Roughness function in convey.dll. Check that the Flood Modeller and CES versions are compatible, and that convey.dll is present in the Flood Modeller/bin folder or on the system path.
E1688	CES dlls have not been initialised	Failed to load the CES dlls convey.dll and/or conveycalcs.dll. Check that the Flood Modeller and CES versions are compatible, and that the files convey.dll and conveycalcs.dll are present in the Flood Modeller/bin folder or on the system path.
E1689	Failed CES dll function call to Calculate Conveyance for section id	Failed to load the Calculate Conveyance function in convey.dll. Check that the Flood Modeller and CES versions are compatible, and that convey.dll is present in the Flood Modeller/bin folder or on the system path.
E1690	Failed CES dll function call to Get Depth Intervals	Failed to load the Get Depth Intervals function in convey.dll. Check that the Flood Modeller and CES versions are compatible, and that convey.dll is present in the Flood Modeller/bin folder or on the system path.
E1691	Failed CES dll function call to Get Eddy Viscosity	Failed to load the Get Eddy Viscosity function in convey.dll. Check that the Flood Modeller and CES versions are compatible, and that convey.dll is present in the Flood Modeller/bin folder or on the system path.
E1692	Failed CES dll function call to Get Min Depth	Failed to load the Get Min Depth function in convey.dll. Check that the Flood Modeller and Flood Modeller versions are compatible, and that convey.dll is present in the Flood Modeller/bin folder or on the system path.
E1693	Failed CES dll function call to Get No Panels	Failed to load the Get No Panels function in convey.dll. Check that the Flood Modeller and Flood Modeller versions are compatible, and that convey.dll is present in the Flood Modeller/bin folder or on the system path.
E1694	Failed CES dll function call to GetRelaxation	Failed to load the Get Relaxation function in convey.dll. Check that the Flood Modeller and CES versions are compatible, and that convey.dll is present in the Flood Modeller/bin folder folder or on the system path.
E1695	Failed CES dll function call to Get Temperature	Failed to load the Get Temperature function in convey.dll. Check that the Flood Modeller and CES versions are compatible, and that convey.dll is present in the Flood Modeller/bin folder or on the system path.
E1696	Failed CES dll function call to Get Max Iterations	Failed to load the Get Max Iterations function in convey.dll. Check that the Flood Modeller and CES versions are compatible, and that convey.dll is present in the Flood Modeller/bin folder or on the system path.
E1697	Failed CES dll function call to Set Relaxation	Failed to load the Set Relaxation function in convey.dll. Check that the Flood Modeller and CES versions are compatible, and that convey.dll is present in the Flood Modeller/bin folder or on the system path.
E1698	Failed CES dll function call to Set Depth Intervals	Failed to load the Set Depth Intervals function in convey.dll. Check that the Flood Modeller and CES versions are compatible, and that convey.dll is present in the Flood Modeller/bin folder or on the system path.
E1699	Failed CES dll function call to SetEddyViscosity	Failed to load the SetEddyViscosity function in convey.dll. Check that the Flood Modeller and CES versions are compatible, and that convey.dll is present in the FloodModeller/bin folder or on the system path.

Error Messages E1700-E1799

Error code	Message	Info / troubleshooting / details - what do I do to resolve!
E1700	Failed CES dll function call to Set Min Depth	Failed to load the Set Min Depth function in convey.dll. Check that the Flood Modeller and CES versions are compatible, and that convey.dll is present in the Flood Modeller/bin folder folder or on the system path.
E1701	Failed CES dll function call to Set No Panels	Failed to load the Set No Panels function in convey.dll. Check that the Flood Modeller and CES versions are compatible, and that convey.dll is present in the Flood Modeller/bin folder or on the system path.
E1702	Failed CES dll function call to Set Max Iterations	Failed to load the Set Max Iterations function in convey.dll. Check that the Flood Modeller and CES versions are compatible, and that convey.dll is present in the Flood Modeller/bin folder or on the system path.
E1703	Failed CES dll function call to SetTemperature	Failed to load the SetTemperature function in convey.dll. Check that the Flood Modeller and CES versions are compatible, and that convey.dll is present in the FloodModeller/bin folder or on the system path.
E1704	Failed CES dll function call to GetHytMultiplier	Failed to load the GetHytMultiplier function in convey.dll. Check that the Flood Modeller and CES versions are compatible, and that convey.dll is present in the FloodModeller/bin folder folder or on the system path.
E1705	Failed CES dll function call to SetHytMultiplier	Failed to load the SetHytMultiplier function in convey.dll. Check that the Flood Modeller and CES versions are compatible, and that convey.dll is present in the FloodModeller/bin folder or on the system path.
E1706	Failed function call to fn_requestoutputs_at_timestage for section	Failed to load the RequestOutputsAtTimeTStageD function in convey.dll. Check that the Flood Modeller and CES versions are compatible, and that convey.dll is present in the FloodModeller/bin folder or on the system path.
E1707	Failed function call to fn_get_isis_tables for section	Failed to load the GetIsisTables2 function in convey.dll. Check that the Flood Modeller and CES versions are compatible, and that convey.dll is present in the FloodModeller/bin folder or on the system path.
E1708	Failed CES dll function call to FnGetMinMax_Output_Elevations for section id	Failed to load the GetMinMaxOutputElevations function in convey.dll. Check that the Flood Modeller and CES versions are compatible, and that convey.dll is present in the FloodModeller/bin folder or on the system path.
E1709	Failed CES dll function call to fngetmaxarea for section	Failed to load the GetMaxArea function in convey.dll. Check that the Flood Modeller and CES versions are compatible, and that convey.dll is present in the FloodModeller/bin folder or on the system path.
E1720	Too many substrings in rule	The depth of rule l1 is too large - try simplifying the rule, splitting into more than one if appropriate.
E1721	Parse error in rule	Error in parsing the rule data in l1. Check the syntax - check that the node label is spelt correctly (case-sensitive), the operators used are valid and for correct bracketing
E1722	Logical storage capacity exceded in rule l1	Rule l1 is too large - try simplifying the rule, splitting into more than one if appropriate.
E1723	Error in rule l1	A non-numeric value was read from Rule l1 when a numeric value was expected. Check the rule syntax.
E1724	Failed CES dll function call to SetConvTolerance	An error occurred whilst calling the CES dll in setting the convergence tolerance. Check that the CES_CONVERGENCE_TOLERANCE value in the ief file is entered correctly and is valid. Check also that the Flood Modeller and CES versions are compatible, and that convey.dll is present in the FloodModeller/bin folder or on the system path.
E1725	Failed CES dll function call to GetConvTolerance	An error occurred whilst calling the CES dll in obtaining the convergence tolerance. Check that the Flood Modeller and CES versions are compatible, and that convey.dll is present in the FloodModeller/bin folder or on the system path.
E1726	Failed CES dll function call to SetConveyanceType	An error occurred whilst calling the CES dll in setting the conveyance type. The value for CES_ROUGHNESS in the ief file should be 'LOWER', 'UPPER', or 'RECOMMENDED'. Check also that the Flood Modeller and CES versions are compatible, and that convey.dll is present in the FloodModeller/bin folder or on the system path.
E1727	Rule l1 has already been defined. Note that only the first 10 characters of the name are significant.	A duplicate rule name has been detected in the same unit. Note that only the first 10 characters of the rule name (e.g. 'Rule 1' are read).
E1728	Rule ALL is not valid. It could be confused with the keyword ALL in the TIME RULE DATA SET.	Naming a rule beginning with the characters 'ALL...' is not permitted. The keyword 'ALL' is reserved for the time-rule-data set table to denote all rules to apply. Rename the rule.
E1729	Fatal error in 2D solver	The program has terminated due to a fatal error in the 2d solver (e.g. TUFLOW); check the diagnostics for the 2d solver for more information.
E1730	Indeterminate flow direction in qxbdy	This should not be possible - the orientation of QXBDY could not be determined. Check the model connectivity.

Error Messages E1800-E1899

Error code	Message	Info / troubleshooting / details - what do I do to resolve!
E1800	Unknown bank type for section id	An invalid bank type has been entered in CES Section node 'label1'. Valid types are 'RO', 'RI', 'RS', 'LO', 'LI', 'LS' or blank. Check data for node 'label1'
E1801	Sinuosity can only provided on a left bank in section id	A sinousity value in the CES section data table is only valid if coincident with a left bank marker. Check data for node 'label1'
E1802	Even number of bank markers required for section id	Each left bank marker in a CES section data table must have a corresponding right bank marker. Check data for node 'label1'
E1803	Put roughness chainage in ascending order for section id	The roughness table in a CES section unit must be entered in ascending cross-chainage order. Check data for node 'label1'
E1804	Put section chainage in ascending order for section id	The cross section data table in a CES section unit must be entered in ascending cross-chainage order. Check data for node 'label1'
E1805	RO bank marker must follow LI for section id	A left bank marker in a CES section data table must have a corresponding (and opposite - outer must match with inner) right bank marker. No other bank marker may be in between the two. Check data for node 'label1'
E1806	RI bank marker must follow LO for section id	A left bank marker in a CES section data table must have a corresponding (and opposite - outer must match with inner) right bank marker. No other bank marker may be in between the two. Check data for node 'label1'
E1807	LI bank marker must follow RO for section id	A left bank marker in a CES section data table must have a corresponding (and opposite - outer must match with inner) right bank marker. No other bank marker may be in between the two. Check data for node 'label1'
E1808	LO bank marker must follow RI for section id	A left bank marker in a CES section data table must have a corresponding (and opposite - outer must match with inner) right bank marker. No other bank marker may be in between the two. Check data for node 'label1'
E1809	RS bank marker must follow LS for section id	A left straight bank marker in a CES section data table must have a corresponding right straight bank marker. No other bank marker may be in between the two. Check data for node 'label1'
E1809	RS bank marker must follow LS for section id	A left straight bank marker in a CES section data table must have a corresponding right straight bank marker. No other bank marker may be in between the two. Check data for node 'label1'
E1810	LS bank marker must follow RS for section id	A left straight bank marker in a CES section data table must have a corresponding right straight bank marker. No other bank marker may be in between the two. Check data for node 'label1'
E1811	Date out of range in section	The date of the simulation is invalid for the CES component - check the run times in the ief file are set and are covered by the time series data in the roughness (*.rad) file for all roughness zones in the CES Section node 'label1'.
E1813	No section data to calculate conveyance for section id	Error returned in call to CES to calculate conveyance. Check the cross-section data has been fully entered for CES Section node 'label1'.
E1814	No roughness data to calculate conveyance for section id	Error returned in call to CES to calculate conveyance. Check the roughness data has been fully entered for CES Section node 'label1'.
E1815	Roughness zone not found in roughness file for section id	Error returned in call to CES to calculate conveyance. Check the roughness zones entered in the roughness data for CES Section node 'label1' are all contained in the corresponding roughness (*.rad) file. Check the General section for the rad file being used.
E1818	[No message]	This error should never appear. No roughness file has been found, and CES sections are being used.
E1819	Data error at line X. failed to load roughness file.	The roughness file (.rad) specified in the General section could not be loaded, and CES sections are present in the model. Check that the .rad exists on the specified path, and is valid.
E1820	Non unique section name found for section id/replicate	The CES (or replicated CES) Section name 'labell1' has already been processed from the data file. Two channel sections of the same name in the same data file are not allowed. Check data and remove/rename one of the node labels.
E1821	Start date is out of the range specified in the roughness file for section id	The start date/time of the simulation is invalid for the CES component - check that real dates/times in the ief file are set and the start time is covered by the time series data in the roughness (*.rad) file for all roughness zones in the CES Section node 'label1'.
E1822	Finish date is out of the range specified in the roughness file for section id	The finish date/time of the simulation is invalid for the CES component - check that real dates/times in the ief file are set and the finish time is covered by the time series data in the roughness (*.rad) file for all roughness zones in the CES Section node 'label1'.
E1824	Section not found	CES section node 'label1' was not found when attempting to process the CES properties. This error should have been previously trapped, but check the connectivity and CES section data for this label.
E1825	At least two bank markers required for section id	At least one pair of left/right bank markers are required for each CES Section. Check section data for CES Section node 'label1'
E1827	Failed CES dll function call to FnAddInterpolate for interpolated section, cannot find upstream section for section id	The upstream CES section associated with node 'label1' was not found when attempting to process the CES properties. Check the connectivity and CES section data for this label.
E1828	Failed CES dll function call to FnAddInterpolate for interpolated section, cannot find downstream section for section id	The downstream CES section associated with node 'label1' was not found when attempting to process the CES properties. Check the connectivity and CES section data for this label.
E1830	Cannot find urban unit.	A connectivity error has occurred involving an Urban unit. Check connectivity for all Urban units.
E1831	This urban throughflow unit is not associated with an urban unit.	An urban throughflow unit must be associated with an urban unit. Check the urban units' connectivity.
E1832	The data store cannot accurately store the urban unit's number.	This error should not occur. Please contact the support team.

Error Messages E1900-E1999

Error code	Message	Info / troubleshooting / details - what do I do to resolve!
E1900	Cannot allocate memory, status = n	A memory allocation error has occurred. This may be because the model is too large, or the machine's memory is low.
E1926	CES units must be present either side of a chain of interpolates; labels involved are l1 and l2	If interpolating between CES Section units, ensure that a CES Section unit is both immediately before and after the consecutive INTERPOLATE units. Ensure that none of the INTERPOLATE units has a distance to next cross-section of zero.
E1926	Geometric conduits must be attached to another of the same type; labels involved are l1 and l2	A geometric conduit (e.g. circular, rectangular, arch or sprungarch) must be connected to one of the same type, though the dimesnions may change. If you need to change the type, insert a junction or other unit (e.g. loss) between the two, remembering that at such a break, the last unit before the junction, etc. must have a distance to next section of zero. Note that for the direct method, any change in dimensions along a reach will be ignored.
E1999	Error opening/closing file f1	An input/output error occurred with file f1. Check that the file in question is not read-only, and is not in use by another application. Check the Windows Task Manager for any processes that have crashed, but not properly stopped.
E1999	Can not have PMF Catchment Wetness Index flag with non-PMF profile	The flag for CWI has been set to 'PMFCW' for a non-PMF event in the FEH unit. Check the data file for the unit in question. Set the flag to 'FEHCW' to use standard FEH CWI, or 'OBSCW' and use an observed CWI.
E1999	Error in calculating ARF(5D)*EM-5D in CWI calculations for PMF	The storm duration for an FEH PMF must be less than 120 hours in order to perform the CWI calculation (values of EM-5D are only given up to 600hrs). Use a manual (observed) CWI value or a short storm duration.
E1999	Storm/catchment area must be positive	The catchment area was entered as zero or negative for an FEH/FSR unit, and caused an error in calculating the ARF. Note this error should have been previously trapped, and that storm area defaults to catchment area if entered as zero or negative.
E1999	Storm duration must be positive	A zero or negative storm duration was entered for the FEH unit. This is not allowed - check the input data for this unit.
E1999	Interpolate unit unacceptable as first data unit	An interpolate unit was specified as the first unit in the data file. This is not valid, since there is no previous unit from which to interpolate.
E1999	Replicate unit unacceptable as first data unit	A replicate unit was specified as the first unit in the data file. This is not valid, since there is no previous unit to replicate.
E1999	Invalid time/date format	An invalid date/time format was specified times entered in DATES format in an REBDY or GAUGE unit. The correct format for the time field is hh:mm; the correct format for the date field is dd/mm/yyyy. The time field is before the date field; both field widths are 10. Check data file input.
E1999	Storm duration (x hours) is too large/too small/not an odd integer multiple of dt	For a valid PMF calculation in an FEH unit, the storm duration must be between 1 minute and 600 hours. It must also be an odd integer multiple of the time interval in order for the PMF profile to be symmetrical, centred around a single peak value.
E1999	RPFLAG (f1) should be set to WINRP or SUMRP for PMF calculation	The rainfall profile flag (f1) in an FEH boundary unit must be set to 'SUMRP' or 'WINRP' for a PMF calculation. Check the data file; note that mixed case is not allowed.
E1999	SAAR (x) is less than the minimum allowed for PMF calculation	The SAAR value must be at least 500mm for an FEH PMF calculation - this is because the EM ratios are not specified for a SAAR value of less than 500mm.
E1999	Negative rainfall detected in PMF calculation.	A negative rainfall has been calculated for a time interval during an FEH PMF calculation.

Was this article helpful?

What's Next

Warning messages

Table of contents

Error Messages E1000-E1099
Error Messages E1100-E1199
Error Messages E1200-E1299
Error Messages E1300-E1399
Error Messages E1400-E1499
Error Messages E1500-E1599
Error Messages E1600-E1699
Error Messages E1700-E1799
Error Messages E1800-E1899
Error Messages E1900-E1999