Douglas Graham

Sorry, I replied to your first query and can now see that you have already found the Toolbox.
You don't say what the format for your DEM is.
What program are you using now to create/edit your DEM?
Regards,
Douglas

It depends on the format of your DEM.
If it is an ASCII Grid file in ArcGIS, then you can use the MZero Toolbox "Grd2MIKE".
This is found by clicking on File/New/File... and then selecting the MIKEZero/MIKE Zero Toolbox (.mzt) icon.
Regards,
Douglas

At the end of the _WM_Print.log file is a summary of the simulation effort for each of the MSHE processes.
The best way to speed up the simulation is to find which process is taking the most time and work on it first.

In the screen shot that you included, all of your timesteps are 24 hours.
This is much too long for any of the very dynamic processes, such as OL, UZ and the river.
So, I suspect that the simulation is simply not converging.
If you really don't need short time steps, then I suggest that you use the 2LayerUZ and routing branches in the rivers.
If you are not worried about the OL dynamics, you can also use a low ManningsM (very rough) to slow the OL velocities.

Probably the most important thing is to start out with short simulations and a coarse grid. When you have a stable simulation, you can start slowly lengthening the simulation period and then refine the grid.
Regards,
Douglas

Hi, this error is saying that your UZ column is too short. MIKE SHE will generally not run if the water table is below the bottom of the UZ column. You need to make the depth of your UZ column deeper than the depth of the water table, or the thickness of the top SZ layer - which ever is shallower.

Regards,
Douglas

Hi Hannu,
for many years we included a very simple editor for creating and modifying polygons.
We stopped supporting this tool several years ago.
Most people who use shape files have a preferred GIS platform, such as ArcGIS (expensive) or QGIS (free).
I hope this helps.
Douglas

Hi,
I don't really have a good answer for you.
The drip method is probably your best bet. But it isn't ideal.
The amount of drip that infiltrates to the GW will be net of Actual ET (ie rate of drip - AET).
Remember that the drip is added to ponded depth, and your ET will also be taken first from ponding before root zone ET.
So, you will lose some or at lot of your drip to ET.

I had a similar problem a few years ago, and there we created an array of pumping wells to add the water directly to the shallow groundwater.
This way we could control precisely how much water was added to the water table.

Regards, Douglas

Hi Is this solved now?
I looks your internet connection has dropped, and then the software has lost the connection to the internet license.
douglas

Hi Waseem,
I don't think this is an error with your topography.

MIKE SHE cannot interpolate Integer Grid Codes, such as Vegetation and Soils codes. 
All of these must be integer multiples of the Model Domain. That is, each grid cell must have 4 or 9 or 16, etc vegetation types.
This restriction can also can trouble when the origns for the grid files are not aligned.

The easiest way to resolve this is to use the "Create" buttons on the individual dialogs after you have set up your grid. This will ensure that all your grid files are the same as your domain.
Otherwise, you can also edit the geographic properties of the grid files in the Grid Editor.

Regards,
Douglas

Hi Ajai,
what version of the software are you using?
The log message is saying that the convoluted boundary polygon is creating some boundary cells that are surrounded by internal cells. This can happen when the boundary shape file has tight loops.
I think this was updated in the latest Service Pack for Release 2017.
If you are not using this, then you may have to edit your polygon to remove small tight loops.
Douglas

Hi Ajai,
The way it works, is that you
1. create a dfs2 map of grid codes with each code representing an area around each rainfall station.
2. From this map, the GUI will create one data tree item for each grid code.
3. Then, for each grid code item in the data tree, you assign a dfs0 time series.

So, you don't need to convert your dfs0 to a dfs2.
Hope this helps,
Douglas