When running an OpenFlows FLOOD simulation, if the model setup and configuration is inconsistent, the numerical engine will output for the majority of cases an error message.
Typically, the error message is shown during the initialization phase of the simulation, a few seconds after the user launches the simulation. A dialog stating the simulation has finished will appear:
Note that, this message appears always when the model simulation is finalized either successfully or unsuccessfully.
Select Yes to view the simulation log file and scroll to the end. In case the simulation ran successfully, a clear message will appear at the end of the file.
If the simulation was unsuccessfully, an error message will appear at the of the file. The error message may contain a information about the error and how to solve it. It maybe more or less detailed as shown below:
Nevertheless, the error message will always contain an error code as shown in the figure below:
The error code will contain 3 parts, the subroutine/method that generated the error, the correspondent module and a number (e.g. ERR50).
The aim of this article is to list the most common error codes that don't show a accompanying message that helps to solve the error.
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