Mathieu Hellegouarch

Hi Jeremie,

I didn't find any clue to explain the problem in your log files.

This isn't a common problem, which probably requires to check the input data. I think you should attach all the setup files, or send them to your local MIKE by DHI support center.

Best regards,
Mathieu

Hi Serafima,

Your guess is correct that it is not possible to directly merge different *.mdf files. However when you've built several polygons, it's quite easy to export them to text files using the menu Data \ Export boundary. You can then import them in another *.mdf file through Data \ Import boundary.
So I suppose this solution may help you.

Regarding your other issue: that looks like a memory issue ! So it can be due either to a big setup, or a low RAM on your computer. If you can't use a computer with bigger RAM, you can try to reduce the number of 'Undo/redo levels' in the Edit \ Options menu. This controls the number of versions of the mesh which are temporary saved in the memory while you edit the mesh, to allow you cancelling the last changes. If you set it to the minimum, you won't be able to undo the last changes, but it will release part of the memory.

Best regards,
Mathieu

Hi,

There doesn't seem to be anything wrong with your settings. However, since you have set the parameter 'No. of culverts' to 6, it means that you have actually inserted 6 culverts at each location (all with the same geometry of 3x3m). So you need to make sure that this is correct, since it's not what you described initially.

It is however not possible to say whether the obbserved effect is correct or not without knowing the hydrodynamic conditions. If you doubt that this is realistic, I'd suggest that you try for example to refine the mesh in the channels where you have set the culverts: having only two mesh elements across these channels is maybe not detailed enough to accurately describe the flow through these channels.

Best regards,
Mathieu

Hi Matt,

Digipoints are the intermediate points, that you may also call vertices, which define the shape of the branch.

When you edit a branch on the map, all these digipoints appear, and you can move them graphically. So I suppose that the solution to your problem is to move a digipoint close the mentioned chainage, and you'll probably see that you had 2 of them superimposed, which may be troublesome.

If you have two points at the same location, you can simply delete one of them.

Best regards,
Mathieu

Hi Mar,
you can select the cross-sections by double clicking them one by one, but you can't e.g. use the Shift key to select a number of sections in one go.

If the cross-sections you want to select are all on a specific branch, you can also right-click on the branch name, and select at the same time all the cross-sections from this branch.

Best regards,
Mathieu

Hi,

a common mistake is that you may have converted the XYZ to another coordinate system. The results will be that points won't be displayed at the expected location. So you should try to import again the XYZ file, and while browsing and selecting the XYZ, pay attention to the corrdinate system specified at the bottom of the browsing window (in the field 'Convert from'), and make sure that the specified system is the actual coordinate system in which the XYZ data are provided.

You can also check that your XYZ file has an appropriate format, by comparing with available example data, for example those installed in :
C:\Program Files (x86)\DHI\2014\MIKE Zero\Examples\MIKE_ZERO\BatEdit

Hope this may help.

Best regards,
Mathieu

Hi,

This is probably because you haven't loaded any shape file.

You first need to load your shape file from the menu Layers \ Add/Remove. This has to be done prior to the conversion.

Best regards,
Mathieu

Hi Sarah,
Have you tried changing the item type to either 'Wind speed' or 'Wind velocity'? When selecting the input file, you can check the possible item types in the tab 'Constraints info'.

Note that you can also check out the example installed in the folder C:\Program Files (x86)\DHI\2014\MIKE Zero\Examples\MIKE_21\SW\NorthSea

Best regards,
Mathieu

Hi,
The descriptions you get using a link channel and a (weir) side structure are both approximations of the real world. They both provide the same, i.e. they represent the transversal spilling over the banks using a weir equation. With both options, you can define a storage area in the floodplain, downstream the weir. A difference is that the link channel can be connected downstream to another branch (for example another branch describing the floodplain), but the side structure cannot.

If you have to model a long bank, you may need to use multiple weirs (side structures or link channels) to describe the overspilling, instead of a single one. Using muliple weirs will be more accurate, because each weir will compute the spilling using a local water level in the river bed. On the opposite, if you use a single weir, the spilling will be computed using only 1 water level value, whereas in the real world the water level is usually not constant along the bank.

Best regards,
Mathieu

Hi Mar,

it's correct that the US level describes the bank's elevation, whereas the DS level describes the floodplain topography.
The cross-section geometry represents a longitudinal profile of the bank, which will be used as a weir between the main stream and the floodplain.

Best regards,
Mathieu