Rivers Errors
Error message:¶
ERROR : Error code received from MIKE 1D during simulation. MIKE 1D time step no.: 97 - please check the MIKE 1D log file Calling MIKE 1D with stop request after 97 time steps ... Ok
Description: This error notification at the end of an unsuccessful MIKE SHE simulation indicates that the MIKE1D engine in MIKE+ Rivers ran into an error.
Solution/workaround: Please navigate to the corresponding MIKE1D log file, which was created next to the MIKE+ River model file and is named exactly like the model, but with the file ending "MODELNAME.log". Here you can find more details about the problem in the MIKE 1D engine. For each problem you should find a more detailed solution further below on this page. Simply search again for the detailed error message.
Error message:¶
ERROR: Water level exceeded maximum on 1 grid point(s). Largest exceedance on reach 'Reach_1', chainage: 46100.00 ft. Water depth is 13.880 ft which is more than 1.0000 times the cross section height. Water level is 3.0001 ft. (HD_ERR_WLAboveMaxOnXS) Simulation time = 2017-09-10 11:55:56 (time step 2181538).
Description: This error is related to the default restriction that the simulated water depth shall not be higher than the cross section height.
Solution/workaround: This threshold is chosen very conservative, especially for flooding projects this threshold should be increased.
This can be done under the tab "MIKE 1D engine configuration", as shown in the screenshot below.
Error message:¶
ERROR: Digipoint direction is reversed, changing direction almost 180 degrees, at 'C-13_S5' chainage 4070.82.
Description: This is an error in MIKE Hydro River and should not happen anymore in MIKE+. Models being imported from 2017 to 2019 were showing this error sometime.
Solution/workaround: Export the river as polyline shapefile and re-import as river again.
Error message:¶
ERROR: Unexpected exception occurred. Please see log file for details. Exception message: Failed loading data from MIKE URBAN+ bridge (DHI.Mike1D.AmeliaBridge.AmeliaBridge): RiverModel.sqlite Exception: Failed loading data from MIKE URBAN+ bridge (DHI.Mike1D.AmeliaBridge.AmeliaBridge): RiverModel.sqlite Value cannot be null. (Parameter 'key')
Description: Whenever you read somethine like "MIKE URBAN+ bridge (DHI.Mike1D.AmeliaBridge.AmeliaBridge", the model runs into an unhandled exception, which is related to a bug..
Solution/workaround: Please write an email and send the model to mike@dhigroup.com. The source of the problem is normally within missing values or unphysical values in any field or cell of the database, e.g. within Structures or Control Rules/Actions. You can start to go through your model yourself and find & solve the issue. But the error message should be more clear, where the missing value is located.
Error message:¶
ERROR: Water level exceeded maximum on 1 grid point(s). Largest exceedance on reach 'River1', chainage: 43050.00 ft. Water depth is 1156.32 ft which is more than 11.000 times the cross section height. Water level is 1143.12 ft. (HD_ERR_WLAboveMaxOnXS)
Description: Since the extrapolation of the cross section height was already activated, your model is really running into a numerical instability. The combination of a too high fixed time steps together with some unconvenient geometry and flow condition triggers some oscillation and blow up in the model.
Solution/workaround: 1. The easiest solution is to reduce the numerical timestep to a value, that the model run succeeds. 2. But normally you would try to solve the issue to prevent an increase in total simulation time. 3. It is possible that the error would happen only in the very first timesteps, because the initial condition is too far away from an equilibrium state. Then it can beneficial to use in a copy of the model a very small timestep and produce a hotstart file or state file. Then you use this hotstart file with an equilibrium state as initial condition for the long run, which can use a much larger timestep.
Error message:¶
xx
Description: xx.
Solution/workaround: xx.
xx.
