Mathieu Hellegouarch

Hi Matt,

The error you got was an engine error. All errors provided in the 'Simulation' window are thrown by the simulation engine.

And you're right, the shape of the branch is primarily used for calculating chainages, and usually only for that. But if you, for example, create a 2D map result file, the shape of the branch will also affect the 2D results, so it sometimes haev orther usages.

Best regards,
Mathieu

The problem could simply be that you haven't specified a structure ID.

When working with a dambreak structure, the ID is mandatory, and must be specified both in the *.nwk11 file, and in the boundary condition file. If you haven't specified one of them, or if they don't match, then you'll get this error.

The aim of this ID is to allow multiple dambreaks at the same location: therefore you're allowed to have multiple dambreaks on the same branch and chainage, and the ID is used to identify to which dambreak the boundary conditions apply to.

Best regards,
Mathieu

Hi,

In the hd11 file, in the additional outputs tab, you can tick the option "Lateral inflows" before running your simulation. You'll get a new item in the additional result file, called "Lateral Inflows Boundaries": this contains the discharge from all boundary conditions, which includes evaporation, at all calculation points. When this lateral inflow is negative, it means that the discharge is leaving the domain, and when positive it's added like a source.

Regarding the second question for discharge within the river branches: a negative discharge indeed means that water is flowing back, i.e. the sign describes the direction of the flow.

Best regards,
Mathieu

Hi,

Regarding error 385: you can easily check if the file is not found by clicking the "View" button for the time series, in the boundary conditions file. If the file is not found, you'll get an error, and you can simply re-select the file. If it's found, the problem may be due to the constraints, as indicated in the message. These constraints are shown in the window which shows up when you click on the '...' button to select the file: there is a 'Constraints' tab showing what may be wrong with that (typically that you're editing a boundary condition, but that the selected file doesn't contain any discharge item).

For the error 393: this usually indicates that the specified location of boundary condition (branch name + chainage) doesn't correspond to a boundary for this branch. You need to check that you correctly wrote the branch name in the bnd11 file, and then check in the nwk11 file what are the boundaries' chainages.

Best regards,
Mathieu

Hi,

You need to check the mentioned cross section: in the 'Processed data' view, it seems that you've computed the processed data on user-defined levels, but that these levels are not increasing (which they should do).

Best regards,
Mathieu

Hi,

This message probably indicates that the simulation was unstable. So you need to fix it as for any other instability: analyse the results to find what is going wrong, edit the model, or reduce the simulation time step, etc.

Best regards,
Mathieu

Hi Tim,

That's because the export tools always export only the raw data, which is an average value throughout each element, for a dfsu file.

The shaded contour is an option available in MIKE, which controls how these raw data are shown on the screen, but the shaded contour is not saved in the dfsu file and therefore cannot be exported. So you'll have to load the raw results in the other software you want to use (e.g. a GIS) and use the its own display options to get a similar display as the shaded contour in MIKE.

Best regards,
Mathieu

Hi Detolbar,

How big is your DEM size? The problem could be that you're trying to load a huge file.

If that's the problem, you should try to load a smaller file, either a DEM with a coarser resolution or a DEM with the original resolution but a smaller extent.

Best regards,
Mathieu

Hi,

this file could be in the Bin folder. But you should simply open MIKE Zero and go to File \ Options \ Edit Unit Base Groups. Then, using the 'Load unit file' button should directly open the appropriate location where the file is stored.

Mathieu

Hi,

Cross sections are linked to the branches using their 3 "identifiers": branch name, topo-ID, and chainage. So if the cross sections are not visible on the map (in the Network file), or if you get this error message when launching the simulation, one of these identifiers may be wrong.

For instance the branch name and/or Topo-ID specified in the cross section file may not strictly match those in the Network file. Or the chainage specified for the cross sections may not be in the range of chainages defining the branch in the Network file.

Best regards,
Mathieu