Mathieu Hellegouarch

Hi,

Yes, the direction is measured clockwise from true North.

For sources, the water is added as a water volume in the mesh element, for each time step (if the source has a negative discharge, then it's removed).

Regards,
Mathieu

Hi Felipe,

I think there could be different reasons to this problem.

First, do you display the scatter points on the map? If not, you should check that they're correctly located (there could be a problem in case you have specified a wrong coordinates system for the scatter points)

If that's not the problem, I would try to simplify the mesh generation, with:
- only a constant mesh resolution, with no buildings or islands excluded
- Use only 1 scatter data file.
Check if it works in this case. If it does, then you can introduce complexity step by step (add additional scatter data files, then add new polygons with local mesh resolution, etc.), and after each step make sure you can still perform the interpolation. That will help identifying which polygon used in the mesh generation, or which scatter data file, is causing the problem. Then it's easier to investigate further.

Best regards,
Mathieu

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