Mathieu Hellegouarch

Hi Christian,

Yes, the *.exe file will work with version 2017 only. If you e.g. want to use it with version 2016, you will simply need to install MIKE SDK 2016, open the source code and update the references to MIKE SDK libraries in 2016 version, and re-create the executable.

Cheers,
Mathieu

Yes, some errors would instead appear right away when starting the simulation. This is why I think it may be related to the calculated water level.

If you're using the rectangular grid version of MIKE 21 (not the flexible mesh one), if your boundary cells are initially dry, then the error will be detected only when water will reach the boundary during the simulation. The error could be that, when this occurs, only some of the boundary cells become wet, which is not allowed. To avoid this, you may apply a constant bathymetry along the boundary, and also change the initial condition so that the cells along the boundary are all initially wet.

Best regards,
Mathieu

Hi all,

A tool called "Velocity at Maximum Flow Tool" is available for download on this page:
https://www.mikepoweredbydhi.com/download/mike-by-dhi-tools

It does exactly what Christian suggested, to save the U- and V-velocity components corresponding to the maximum current speed (or the maximum water depth).

Note that the tool is provided with its source code, so you can easily modify the code in case you want to get the directions for the minimum values instead of maximum ones.

Best regards,
Mathieu

Hi,

In short, you have two main options to describe a reservoir:
- the simple one, where the reservoir's storage capacity is described with a Level-Area or Level-Volume relationship. You can enter this type of relationship e.g. when you use the "side structure + reservoir" type. We may need to get survey data in the reservoir to assess this kind of relationship.
- the more detailed one, where the reservoir is described with a river branch and with cross sections along the branch. This is the same as the description you use for any other part of a river, except that here the cross sections have to describe the geometry of the reservoir. With this solution, the dynamics of the flow along the reservoir (i.e. between cross sections) can be modelled.

Hope this helps.

Best regards,
Mathieu

Hi Panda,

You can see in the MIKE Zero manual, that the list of options from the MZLaunch utility can be called using this command line:
C:\"Program Files (x86)"\DHI\2017\bin\x64\MZLaunch.exe -h
So if you run this from a command prompt, you then get the MPI option which is:
-mpi X, where X is the number of subdomains to use.

So the final command line may look like this:
Start /wait C:\"Program Files (x86)"\DHI\2017\bin\x64\Mzlaunch.exe case_1_opening.m21fm -mpi 4 -x
if you want to use 4 subdomains with version 2017.

Best regards,
Mathieu

Hi mahsa,

It is no problem for MIKE 11 to have negative values in the boundary conditions! So it is technically possible to keep the current values you have.

What you need to check, is that all your elevation data have the same altimetric reference. That is, cross sections' elevations, structures' elevations and boundary conditions must be expressed with the same reference level.

Best regards,
Mathieu

Hi Vitor Pessoa,

You are most likely working with the version 2014 of the software, which was the very first version of MIKE HYDRO River, and which was not able to edit boundaries from the map. You can check the installed version from the menu Help \ About MIKE Zero...

If you instead use the 2016 or the 2017 version, then you can see the "Boundaries" ribbon as soon as you create a new MIKE HYDRO file.

Best regards,
Mathieu

Hi,

Ref. error 340: it is correct that each structure in MIKE 11 must have one cross section located upstream, and another one downstream. If you have added such cross sections but you still get this error, it means that MIKE 11 is not able to "see" them, and I think that the most obvious reasons may be:
1. that you mispelled the branch name of the cross sections (i.e. that cross sections are defined on a branch with a slightly different name than the branch on which the structure is defined)
2. that you mispelled the Topo ID of the cross section: just like for the branch name, the Topo ID of the cross sections must be identical to the Topo ID of the branch on which you have defined the structure.

Ref. error 86: in this structure, you have a table with Q/h relationships, and something's apparently wrong in that table. Values must be increasing downwards. Sometimes this simply highlights that you didn't compute at all the Q/h relations (i.e. the table is still empty): in this case, simply recompute the relations. If you manually edited the table, you should either recompute again the relations using the dedicated button, or correct manually the problem.

Please let everyone know if this was usefull, or if you found other information useful for others :)

Best regards,
Mathieu

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