Description
The user can collectively check the consistency of the model using a semi-automated validation functionality for an active simulation by clicking on the 'Validate' button that is located in the 'General' tab of the 'Simulation setup' under 'Simulation specifications' (see Fig. 1).
Fig. 1 - Simulation set-up ID
This validation is carried out by the engines in such a way that the user can get the errors and warnings before actually running the simulation. Therefore the 'Validate' button makes a very comprehensive check, exactly as it does when the user starts the simulation. This also means that whenever the engines get improved e.g., to report more succinct error messages, the messages displayed with the ‘Validate’ function also get improved.
That being said, MIKE+ also runs an automatic "on the fly" validation check in the background looking for simple data errors (showing red exclamation marks) when the user is in the process of setting up the model in the user interface's editors. This type of user interface validation can only check the values the way they are stored in the database e.g. verify that a fraction is indeed in the range [0-100]. However this validation check cannot always check that the value is consistent with other data defined elsewhere in the model setup, because it can be difficult for the user interface to compare with other sources of data. This is why there may be errors identified by the engine (and the 'Validate' button), and not identified by the editors (see Fig. 2).
Fig. 2 - On the Fly Validation
Note: Any error message from the 1D engine comes with a corresponding error ID at the end, e.g. "ST_ERR_NoXSFound" shown in the log file. The user has the possibility to convert such an error to a warning during runtime, thus allowing the simulation to keep running.
Note that depending on the error, converting it to a warning could cause invalid or incorrect results.
To convert an error in MIKE+ navigate to the 'Simulation' tab in the upper bar and click 'MIKE 1D engine configuration' and then 'Custom options'. The 'Option name' is 'MessageIdToWarning', 'Value type' is 'Text' and the 'Value' is the desired error ID to convert like the example ID mentioned above (see Fig. 3).
Fig. 3 - Converting a simulation error to a warning is feasible by activating the relevant 'Custom option' in 'MIKE 1D engine configuration' dialog
Conclusion
The process of validation is aided by both the visual data checks on the graphical user interface but also the 'Validate' button, which is employing the 1D and 2D engines to check for potential errors and warnings.
Conversion of a simulation error to a warning is possible but care should be taken so that the results are still valid.
FURTHER INFORMATION & USEFUL LINKS
Manuals and User Guides
MIKE+ Documentation Index
Training options
Portfolio: MIKE+ self-paced courses