Error code

Resolution

In the Basin module configuration the option "Initial Conditions -> Continue from previous simulation" was selected but the simulation you are trying to run is a "cold start" run, meaning it does not have any information available to start from. This option should be set to True when, for example, you run a simulation for the month of January and then want to run a continuation of that simulation for the month of February and you want to pick up the initial conditions from the final results of the January run. OpenFlows FLOOD always write a "restart" file by default, so you can always restart and continue your model simulation. If you set this option to False, then the simulation will start with the default initial conditions, and the error will not appear. 

ModuleEnterData - ScanLine - ERR01. 

Found: at the end of line.

Line: NETWORK_FILE   : 

The path to the Drainage Network file (.dnt) was not defined in the Drainage Network module input options, under Main options -> Network file

forrtl: error (65): Floating invalid

An exception occurred in the model calculation yielding a floating point error message. For MOHID Water numerical engine, this is normally an issue related with the definition of the model integration time step. See more information in the related article: How to setup the model time step in MOHID Water engine

ERROR: Instability in THOMAS3D - ModuleFunctions - ERR10

The MOHID Water numerical engine solution became unstable and the simulation has made a controlled stop. Possible reasons for this to happen are irregular setup of the computational grid and bathymetry values, or an irregular choice of model integration time step. See more information in the related article: How to setup the model time step in MOHID Water engine

forrtl: warning (528): IEEE_UNDERFLOW

This is just a warning and can be disregarded if it is appearing at the end of OpenFlows FLOOD simulation log file. Some algorithms in OpenFlows FLOOD computational engines might signal this, mostly due to optimization procedures.

StartTimeSerieInput - ModuleTimeSerie - ERR23

The error message can occur because the time series file does not contain information for the simulation period. The time series data file must contain the entire period of the simulation.

ConstructGlobalOutput - WaterProperties - ERR02 - Keyword OUTPUT_TIME must be defined; at least one property has HDF format outputs

this may because you activated a water property HDF map output but did not activate the option Map output. Set "Map Output" to True, then a time step (increment) in seconds for the output is necessary.

SetSubModulesConstructor - ModuleInterfaceWaterAir - ERR10

This error can occur because you are running a 3D model (MOHID Water) and did not activate in the InterfaceWaterAir module options in rugosity. Here is a workaround for this issue:

1) Enable text file editor in FLOOD, instead of using property grids: How to enable text editor setup options in OpenFlows FLOOD
2) Copy this block to the InterfaceWaterAir input file:

<begin_rugosity>
INITIALIZATION_METHOD : CONSTANT
DEFAULTVALUE : 0.0025
REMAIN_CONSTANT : 0
OUTPUT_HDF : 1
TIME_SERIE : 0
<end_rugosity>

FATAL; INTERNAL; Read_Final_HDF5; ModuleHydrodynamic. ERR10

You have set the option CONTINUOUS to 1, which specifies that the simulation will run as a "hot start", i.e. use as initial conditions the final solution computed in a previous simulation. Because this is a root simulation the "previous" simulation is not found, thus the error. Please set the option to CONTINUOUS to 0 and the problem should be resolved.

Data file does not exist: ReadKeywords - MohidLand - ERR030

This can occur if there are unexpected characters in the file path. Simplifying the file path will likely resolve the issue.

ConstructGlobalVariables - HorizontalGrid - ERR10

This means the Grid Data Digital Terrain Model file was not found, most likely because the path contains special characters and that only ASCII letter should be used.

 ERROR 141: Outfall has more than 1 inlet link or an outlet link.

This error only will appear in the Stormwater.rpt file located in the res folder. This is a SWMM engine report file generated during the coupled 1D SWMM/2D simulation. This will occur if you have more than one conduit connected directly to an outfall, and can result in longer than expected model run times. The SWMM solver does not allow this configuration. To resolve this, add a manhole and connect the two conduits to this, then connect this new manhole to the outfall. You can size the extra conduit so that the headlosses will be minimal. It is also recommended to run the 1D model in SewerGEMS to assure that the model will compute.

PropertiesEvolution - ModuleLagrangianGlobal - ERR10

This has been known to occur when modeling larvae trajectory and growth. In such as case, you can set a proxy for larvae food by adding "fish food" as a water property in the WaterProperties file. An example of the settings are as follows: 

<beginproperty>
NAME                                 : fish food
UNITS                                 : mgC/m3
FILE_IN_TIME                    : NONE
REMAIN_CONSTANT         : 1
DEFAULTVALUE                 : 0.5
INITIALIZATION_METHOD : CONSTANT
ADVECTION_DIFFUSION  : 0
DISCHARGES                    : 0
SURFACE_FLUXES           : 0
MIN_VALUE                        : 0
OUTPUT_HDF                    : 0
TIME_SERIE                       : 0
<endproperty>

ReadHDF5Values2D - ModuleFillMatrix - ERR30

This error occurs if the user is reading data from an HDF5 that is not using the same grid as the model's computational grid. The data needs to be interpolated from the original grid to the actual model grid. See this link for details.

ConstructFile - ModuleField4D - ERR20

This error occurs if the input data is not in a file with an *.hdf5 or *.nc (netcdf) extension.

StartTimeSerieInput - ModuleTimeSerie - ERR15

The time units in the input time series file is not correct. Supported options are (case sensitive) SECONDS, MINUTES, HOURS, DAYS; MONTHS, YEARS.

ConstructTimeInterpolation; Hydrodynamic; ERR02

The time step of the child domain is not a multiple of the time step of the parent domain when using nested domains with the MOHID Water engine

StartTimeSerie - ModuleTimeSerie - ERR90

The error message occurs because the time series output configuration file (default name is TimeSeriesLocation.dat) does not have the correct format. Use the toolbox "Time Series -> Create Output Time Series in Grid Location" to create the file in the correct format. 

FATAL; INTERNAL; Verify_Numerical_Options - Hydrodynamic - ERR20

This error is caused by an inconsistent option setting where in the Hydrodynamic input options the you've set the Tide option to False and the Tide Warmup Period to be higher than zero. 

FATAL_, INTERNAL_, "UpdateImposedValues - ModuleMap - ERR08"

The most probable cause for this error is some kind of inconsistency with the bathymetry file and open boundary grid cells. Check for bathymetry values between -55 and -99 and either replace them with plausible bathymetry values or with -99 (set as land cell). 

ComputeLayers - Geometry - ERR20

With the MOHID Water engine, in the Geometry input options, when using CARTESIAN vertical coordinates, the sum of the layer thicknesses has to be higher than the maximum depth in the bathymetry file. 

ConstructHDFPredictDTMethod1 - ModuleFillMatrix - ERR30

When reading a solution from an HDF5 file (or a time series file), the simulation period must be contained within the period defined by the HDF5 file. This error occurs when the simulation initial date/time is lower than the initial date/time in the HDF5 file. Error message contains description: "Could not read solution from HDF5 file; First file instant greater than current time; Matrix name: ****". Change initial date/time for the simulation or use different HDF5 covering the period of the simulation.

ReadHDF5Values3D - ModuleFillMatrix - ERR140

When reading a solution from an HDF5 file, the grid dimensions are not the same as the one defined in the bathymetry file (computational grid size) or the it does not match the number of vertical layers defined in the Geometry input options. 

FATAL; KEYWORD; Inconsistency: mode baroclinic active in a 2D model - ERR01

When activating the Baroclinic option in the Hydrodynamic, the model needs to be 3D (i.e. more that one layer defined in the Geometry module)

ReadOptionsHDFinput - ModuleFillMatrix - ERR04b

Error in setting up wind velocity being read from an HDF5 file. Please follow these instructions to solve the problem.  

ConstructGlobalVariables - ModuleLagrangianGlobal - ERR05

The Lagrangian module option is not activated and the Lagrangian input file is not set to be read by the model. To solve this, in simulation properties, add the Lagrangian module to the list of modules if not yet done. Then, in the Model input data options, set the option "Enable Lagrangian Module" to "True" (if you're not using the user interface write LAGRANGIAN : 1)

Construct_Sub_Modules - ModuleHydrodynamic - ERR80 

The discharge is located outside the computational grid area. Please check the Discharge input options to fix the issue by making sure the discharge (inflow) point, line or polygon is inside the computational grid. 

ExtraPol2DNearestCell - ModuleFunctions - ERR10

Error message generated when running MOHID Water engine nested grids simulations. Check for potential consistency errors along the edge of a nested grid by visually compare it with the parent grid. Look for areas where the parent grid is land and the child grid has active grid cells. If the error occurs when using nested rotated grids, open your nested bathymetry file in the file editor and delete the text block  <CornersXY> <\CornersXY>. Then at the top of the file, add the following commands, save the file and re-run the simulation. 

CONSTANT_SPACING_X : 1
CONSTANT_SPACING_Y : 1
DX                                      : [insert the grid cell size of the child grid in the XX direction]
DY                                      : [insert the grid cell size of the child grid in the YY direction]

ConstructGlobalVariables - HorizontalGrid - ERR150

This error occurs when you has created a computational grid and selected UTM as the grid coordinate system, but it has set the wrong UTM zone. 

If the actual coordinates you are using is not UTM, then you should select "Grid Coordinates" when creating the new grid.