Mathieu Hellegouarch

Hi, This is a defect in the version you are using, and a hotfix for this problem has just been released. You can download it from here: DHI (mikepoweredbydhi.com) [https://www.mikepoweredbydhi.com/download/hotfixes-2023-update-1/mike-plus-hotfix-13-10-2023?ref=%7b0699E7BA-BF7F-4E51-AE41-6E9F369ACC48%7d] Best regards, Mathieu Hellegouarch

Hi, From the 'Properties' window in the profile plot, you can use the 'Set as default' button so that your custom settings become the new default settings, for future plots created in the current model setup. In the same place, you can alternatively use the 'Save to file' and 'Load from file' buttons, to export the settings to a simple file which can be loaded in other model setups. Best regards, Mathieu Hellegouarch

Hi,
The 'Add delineate' tool will add only 1 catchment per click on the map. So if you want to create two catchements you indeed have to reproduce the step twice: once per catchment.

If your goal is to create one catchment on two different rivers, upstream their meeting point, then you should add one catchement on each river, just upstream the meeting point of the rivers.

Best regards,
Mathieu

Hi,

Generally speaking, you could re-use the same parameters in MIKE HYDRO as in MIKE 11.

In MIKE 11, you can run your simulations with 2 simulation engines: 'MIKE 11 Classic' and the new 'MIKE 1D' engine. MIKE HYDRO River uses only the MIKE 1D engine.
So, if you were using the MIKE 1D engine in MIKE 11, then it's strictly the same engine which is used to compute results in MIKE HYDRO, so it's expected that you'll get strictly the same results.
On the opposite, if you previously used the 'MIKE 11 Classic' engine in MIKE 11, there could be some details which are implemented in a slightly different manner in MIKE 1D, so in this case there could be some differences in the results, and a new calibration from MIKE HYDRO would be useful. But it's likely that in many cases the differences will be very small.

Mathieu

Hi,

Yes, it is the same NAM in MIKE 11, even though it is shown in a different graphical interface.

You can have a look at the MIKE HYDRO Basin manual here:
http://manuals.mikepoweredbydhi.help/2017/Water_Resources/MIKEHydro_Basin_UserGuide.pdf
It contains a simple tutorial, and also contains the detailed descriptions of the various NAM pages.

Mathieu

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