Professional Documents
Culture Documents
MIKE SHE
Basic Exercises
1
INTRODUCTION ............................................................................................................. 3
1.1
1.2
1.3
5.7
5.8
6
Notes:
The step-by-step exercises in this book are designed to illustrate the basic
functionality available in the user interface and the basic steps required for
integrated groundwater-surface water modeling.
Although the MIKE SHE model used in these exercises is based on a real case
study, it has been significantly simplified to make it run quickly. Thus, the
parameter values may not be representative of real world values. Further, the
simplifications employed are not intended to illustrate best practices in integrated
modeling.
The exercises in Section 1 will run in MIKE SHE's demo mode. Although the rest
of the exercises will not run in the demo mode, the exercises can be easily
modified so that they will run in the demo mode by reducing the number of nodes
or the simulation length. The necessary changes are noted in the exercises.
1 Introduction
In the hydrological cycle, water evaporates from the oceans, lakes and rivers, from the
soil and is transpired by plants. This water vapour is transported in the atmosphere and
falls back to the earth as rain and snow. It infiltrates to the groundwater and discharges
to streams and rivers as base flow. It also runs off directly to streams and rivers that
flow back to the ocean. The hydrologic cycle is a closed loop and our interventions do
not remove water; rather they affect the movement and transfer of water within the
hydrologic cycle.
MIKE SHE is an advanced, flexible framework for hydrologic modelling. It includes a
full suite of pre- and post-processing tools, plus a flexible mix of advanced and simple
solution techniques for each of the hydrologic processes. MIKE SHE covers the major
processes in the hydrologic cycle and includes process models for evapotranspiration,
overland flow, unsaturated flow, groundwater flow, and channel flow and their
interactions. Each of these processes can be represented at different levels of spatial
distribution and complexity, according to the goals of the modelling study, the
availability of field data and the modellers choices. The MIKE SHE user interface
allows the user to intuitively build the model description based on the user's conceptual
model of the watershed. The model data is specified in a variety of formats
independent of the model domain and grid, including native GIS formats. At run time,
the spatial data is mapped onto the numerical grid, which makes it easy to change the
spatial discretisation.
1.1
MIKE SHE uses MIKE 11 to simulate channel flow. MIKE 11 includes comprehensive
facilities for modelling complex channel networks, lakes and reservoirs, and river
structures, such as gates, sluices, and weirs. In many highly managed river systems,
accurate representation of the river structures and their operation rules is essential. In
a similar manner, MIKE SHE is also linked to the MOUSE sewer model, which can be
used to simulate the interaction between urban storm water and sanitary sewer networks and groundwater. MIKE SHE is applicable at spatial scales ranging from a single
soil profile, for evaluating crop water requirements, to large regions including several
2
river catchments, such as the 80,000 km Senegal Basin. MIKE SHE has proven
valuable in hundreds of research and consultancy projects covering a wide range of
climatological and hydrological regimes.
The need for fully integrated surface and groundwater models, like MIKE SHE, has
been highlighted by several recent independent studies that can be downloaded from
the MIKE SHE web site. These studies compare and contrast available integrated
groundwater/surface water codes. They also show that few codes exist that have been
designed and developed to fully integrate surface water and groundwater. Further, few
of these have been applied outside of the academic community.
1.2
MIKE SHE has been used in a broad range of applications. It is being used
operationally in many countries around the world by organizations ranging from
universities and research centres to consulting engineers companies. MIKE SHE has
been used for the analysis, planning and management of a wide range of water
resources and environmental and ecological problems related to surface water and
groundwater, such as:
1.3
Develop a GUI that promotes a logical and intuitive workflow, which is why it
includes
o
o
o
o
o
Strengthen the calibration and result analysis processes, which is why it includes
o
o
o
o
Flexible data format (gridded data, .shp files, etc.) that is easy to
update for new data formats
Flexible time series module for manipulating time-varying data
Flexible engine structure that can be easily updated with new
numerical engines
The result is a GUI that is flexible enough for the most complex applications
imaginable, yet remains easy-to-use for simple applications.
In addition to the MIKE ZERO Project Explorer, the MIKE SHE document consists of 4
parts:
Along the bottom - the Validation area and Mouse-over data area
Tool bar - contains icon short cuts for many MIKE SHE operations that can be
acccessed via the Menus. Also, it changes depending on the tools that are currently in
use.
Data tree - displays the data items required to run the model as it is currently defined.
If you add or subtract hydrologic processes or change numeric engines, the make up of
the data tree will change.
Dialog Area - is different for each item in the data tree.
Validation area - displays information on missing data or invalid data items. Any items
displayed here are hot linked to the dialog in which the error has occurred.
Mouse-over area - displays dynamic coordinate and value information related to the
mouse position in the map area of any of the spatial dialogs.
2.1
The MIKE SHE is part of the MIKE Zero suite of modelling tools, which is a global user interface for managing and manipulating data files and
projects for many of the DHI Software products. Thus, when you launch MIKE SHE or one of the other MIKE Zero products you are really
launching MIKE Zero. MIKE Zero then provides the framework from which you can run MIKE SHE or any other product in the MIKE Zero family.
2.2
MIKE Zero is more than a set of modelling tools. MIKE Zero is a project management interface, with a full range of tools for helping you with your
modelling project.
A MIKE Zero project includes all of the modelling files; that is all of
model input files, and model output files. It can also include any raw
data files, reports, spreadsheets, plots, etc. In any project, it is a
challenge to maintain an overview of all of these files, not to mention
keeping regular backups and archives of all of these files. The
number of model artefacts can become overwhelming, as you
progress through the calibration and validation phases and then on
to the scenario analysis and report writing phases.
The core of each project is a .mzp file, which contains all of the
references to all of the files. The Location listed is where the
projectname.mzp file is located.
The MIKE Zero Start Page includes two parts:
The Project Overview table lists the projects that you have recently
accessed, along with their creation and last modified dates.
The Project Explorer is a view into the directory with all the files
that are associated with the project.
The MIKE Zero project structure is designed to help you keep control
of your project.
, in the
click OK.
The default MIKE SHE Setup dialog will now appear and the new
.she file will be added to the project under the Model directory.
The .SHE file contains all the user-specified information required to
run MIKE SHE. However, the file does not contain the actual time
series and grid data. MIKE SHE only stores the path names to the
other data files for time-series data and grid data. This greatly
improves the flexibility of the user interface for keeping your model
up-to-date with new data and for running calibration and prediction
scenarios
Alternatively, you can select any of the listed file types on the right
hand side, or even navigate to one of the other items on the left
hand side. For example, you may need to create a water balance
(.wbl) file during calibration, or a new dfs0 time series file, which you
will find under the MIKE Zero list.
Type in a file name (e.g. SZ1 this file will be used in the next
exercise)
Click OK
10
11
Use GIS point data and xyz point data to interpolated gridded surfaces in MIKE SHE
Add graphical overlays (bitmaps and shape files) to your model display
Understand the properties and attributes that are attached to a Geological Model
Understand the properties and attributes that are attached to Computational Layers
Run the simulation engine and view results using the Result Viewer
3.1
The models used in the following exercises are based on the Karup River watershed in western Denmark. The data files are installed in the MIKE
SHE Examples directory.
Note: If you have just finished the Getting Started exercise and you have the SZ1. she file still open, skip to Step 2.
12
Select the
If you have opened this project before, the project will be displayed
in the list box. In this case, open by clicking on the project name.
3.2
The first thing to do in most projects is to define the maps and overlays that you are going to use in your project.
MIKE SHE allows you to add graphical overlays using bitmaps, ArcView .shp files, etc. These overlays will appear on all maps shown in the
graphical view in the user interface.
13
The Display item is located at the top of the data tree to make it easy
to add and edit your background maps. In the Display item, you can
add any number of images to your model setup, in a variety of
formats. The images are carried over to the various editors, so you
can keep a consistent display between the set up editor and, for
example, the Grid Editor and the Results Viewer.
The option ' Default map display based on the Model Domain'
means that the map view will be defined by the size of the model
domain that you select in the next section of this exercise.
However, in some cases you may want the displayed map area
should be much larger than the model domain, in which case you
can define the map extents in this dialog.
You can also import the extents from a shape or dfs2 file.
14
Notice that a plus sign (+) appears beside the Foreground item in
the data tree. This indicates that sub-items have been added in the
data tree.
The Background and Foreground options refer to the way the
overlays are displayed relative to the input data specified in the other
dialogs.
Also, if you have multiple overlays, the order that they are listed
defines the order in which they are displayed. Thus, you don't
usually want a bitmap at the top of the list, since it would hide all of
the lower overlays.
3.2.3 Define the file and geo-reference the bitmap
Now click on the plus sign beside the Foreground item in the data
tree to expand the data tree. Then click on the sub-item to display
the sub-dialog.
In the subdialog,
Set the Display style as Blend Colors, which will blend the map
colors with any other displayed colors. This will prevent the
15
MIKE SHE includes several simulation modules. The navigation tree in the user interface depends on your choice of simulation modules.
16
17
18
3.4
The model domain and the surface topography are required for all MIKE SHE components.
The model domain defines the horizontal extent of the model area, as well as the horizontal discretization used in the model for overland flow,
unsaturated flow and saturated groundwater flow
3.4.1 Define the model domain
In the Model Domain and Grid Dialog
19
20
This will open the .shp editor utility, where you can add, move and
delete nodes on a shp polygon.
icon
icon
The polygon editor also allows you to create new polygon files. If you
had clicked on the
icon.
21
22
23
Choose line-color
Now in all of your map dialogs, such as the Model Domain and Grid
dialog. The model domain should now appear as a polyline on top of
the map.
3.5
If the map is covered by black dots, click off the Show shape
raw data checkbox. This will turn off the shape file data points.
24
For an integrated hydrological model, you normally define the distribution of precipitation and reference evapotranspiration in both time and space.
However, in this exercise, you are building only a groundwater model and thus the precipitation is actually groundwater recharge.
25
Click on the
Scroll through the list and pick the file Precipitation.dfs0 that
has the green check mark beside it
Click OK
This file browser lists of all of the files in your project that are the
correct file type. The green check beside the file name indicates that
the file contents match the data requirements for example, the
correct time period and units type. If you are in doubt, you can click
on the
In this case, you are using spatially uniform recharge data. The
precipitation file contains data from several rain gauges. The
particular rain gauge to use is selected under the Item in the browse
dialog. In this case, you are using only the data from Precipitation
station 1.
Precipitation is specified the same way data is collected from rain
gauges. It can be input as mean-step accumulated values (e.g.
average rainfall per day in units of mm/day) or, as step accumulated
values (e.g. measured rainfall in a tipping bucket rain gauge in units
of mm since the last measurement).
26
Specify Value = 0.2, which indicates that only 20% of the rainfall
reaches the groundwater table.
Before defining your computational layers you must input a geological model, which is defined as part of the saturated zone.
A geological model may be defined as a combination of layers and lenses. Once the geological model is defined you may choose computational
layers that are either identical to the geological layers or you may choose different computational layers. If the computational layers differ from the
geological layers MIKE SHE s pre-processor will transfer the hydraulic properties of the geological model to the computational mesh.
27
Make sure that the Include pumping wells is not selected, which
says that there are no groundwater pumping wells in the model.
The geology data can be assigned using both Geological layers and
Geological Units. If you chose the geological layers approach then
the hydraulic properties are assigned as spatially distributed within
the layer. If you use gridded data or point data, the hydraulic
properties are smoothly interpolated to the model grid.
If you chose the geological units approach, then you must specify a
distribution of geological units for each geological layer, for example,
by a polygon file. In this case, all of the model cells in each polygon
are assigned a value for each of the hydraulic properties. The
geologic units method is often specified when you use the
AUTOCAL program for parameter estimation and automatic
calibration. In this case, the parameters for each polygon can be
estimated automatically and the model sensitivity for each parameter
calculated.
28
, deleted by
29
Each of the Geological layers includes one item in the data tree for
each of the properties. Additional layers will add additional sets of
items to the data tree.
30
31
The Values relative to ground tells MIKE SHE that you have drains
located 0.5 meter below ground surface in the entire model domain.
If the groundwater table is higher than the drainage level drain flow
will be produced and removed from the model.
32
33
The computational layers are defined independently of the geological layers. While the Geological Layers have geological attributes, the
Computational Layers include computational attributes such as initial conditions and boundary conditions. The properties of the geological layers are
mapped and interpolated to the computational layers during the model preprocessing.
Although, MIKE SHE allows you to define Computational Layers independent of your Geological Layers, in this exercise computational and
geological layers will be identical.
3.8.1 Define Computational Layers
In the Computational Layers dialog:
.\Model Inputs\Maps\init-head-500.dfs2
You are using an initial head from a previous model run, which gives
you a good starting point. In a real model, you might initially start
from a value such as 3m below the topography. However, such a
value will require a run in time, as the model may take several
months to equilibrate.
An alternative is to run the model as a steady-state simulation and
then use the steady-state solution as an initial condition. However,
the steady state solution still might not be a reasonable starting point
depending on how steady the groundwater table is.
34
Look at some of the editing options and close the grid editor
without saving.
Demo Note: in Demo mode, you will not be able to save any
changes to the dfs2 file
MIKE SHE includes sophisticated tools for managing gridded data
as well as time series data. The grid editor can also manage a
combination of both time series and gridded data - that is a time
series of grids. This is very useful for time varying distributed
parameters, such as precipitation that is interpolated from rain gage
data, or distributed recharge calculated by third party programs such
as DaisyGIS.
The grid editor is a split window that can be dragged rightwards to
make the map larger. The table of values on the right side reflects
highlighted grid shown on the lefthand map.
Ranges of values can be searched for, selected and changed using
the select and unselect tools,
Tools/Set Value dialog
, plus the
Important Note
The grid editor is a generic grid tool for all DHI Software, and was
originally developed for the Marine programs MIKE 21 and MIKE 3.
However, this often leads to confusion in the node and layer
numbering because MIKE 21 and MIKE 3 use a different numbering
system.
Node numbering: In the Grid Editor (and in MIKE 21 and MIKE 3)
the nodes are numbered starting in the lower left from (0,0), whereas
in MIKE SHE the nodes are numbered starting in the lower left from
(1,1).
Layer numbering: In the Grid Editor (and in MIKE 21 and MIKE 3)
35
dfs0 files for time series data (e.g. rainfall data at a rain gauge),
dfs1 data, which is not used in MIKE SHE, but used for time
series of lines (e.g. the shape of a coast line)
This now gives you a no-flow boundary condition along the entire
outside of the model. If the entire outer boundary is a no flow
boundary, then this step is actually unnecessary because by default
the outer boundary is no flow.
This is realistic in terms of a watershed boundary, but is not really
very realistic in this case, because you are not going to specify a
river boundary now. In this model, you are basically specifying the
river outflow via drainage, in the sense that wherever the water table
approaches the ground surface, water will be removed from the
36
37
model.
The outside of the model can be divided into boundary sections, by
clicking on the Add Item icon again.
Then click on the Add Point icon,
, and click on the map to
define the location of the boundary point. The boundaries are
specified clockwise around the model starting at the first point in the
table.
The outer boundary conditions are defined independent of the model
grid. Thus, if you change your model grid the boundaries will be
interpolated automatically to the new grid based on the nearest
boundary cells to the point locations. If you change the shape or
extent of the grid, you should check that your boundaries have not
moved unexpectedly.
Internal boundary conditions Internal boundaries are used to
specify such things as lakes and reservoirs that are not included in
MIKE 11. In this case you could specify a constant head or a general
head boundary for the lake.
Internal boundaries are distinguished from outer boundaries
because on the outside of the model, you can specify flux and
gradient boundaries.
3.9
Your have now specified all the input required for the model, including
Up to this point, all of the input data has been specified independent of the numeric model. You have specified only the characteristics of the numeric
model that will be run. Before actually running the model you must run the pre-processor. The pre-processor extracts all of the spatial data that you
Click on the
The preprocessor will start the MIKE Zero Launch utility, which is
allows you to set the process priority for the simulation.
Click OK
If you are starting a very long simulation, then you can also set up
MIKE Zero to alert you when the simulation is finished.
38
Then, click on the items in the data tree and explore the results.
The pre-processor creates a .fif file that contains the cell values etc.
that will be used in the simulation. The processed data has been
interpolated to the computational mesh, exactly as the simulation
engine will read it. However, the .fif file is a binary format optimized
for use by the numerical engine.
The fif-file embeds all geometric data. Temporal data (time-series
data) are not contained in the fif-file, but are read directly from the
source data files during the simulation.
To view the pre-processed data, an parallel set of dfs2 and dfs3 files
are also created so that the standard MIKE Zero tools can be used
to view the data.
It is the dfs data that is shown in the data tree and listed in the file
name text box. Clicking on the View button opens the Grid Editor
with the current pre-processed data file loaded with all the current
overlays.
If you want to edit values in the Grid Editor and use the edited values
in your simulation, then you need to save the file to a new name
after making the changes. Then specify the modified dfs file in the
Setup data tree.
Spend some time moving around in the Processed Data and make
sure you understand the input data and the relation between Setup
Data and Processed Data.
3.10 Step 10 Redefine the horizontal grid resolution
A very powerful feature of MIKE SHE is that you can change the horizontal grid without redefining your model parameters. Thus, you can perform
39
40
sensitivity analysis of your model grid and grid resolution in way that is impossible with other modeling user interfaces.
Demo Note: the demo version is restricted to a maximum of 70x70 cells, so you will not be able to pre-process or run the model with the refined grid.
3.10.1 Change Horizontal Grid Resolution.
In the Model Domain and Grid dialog
NX = 130
NY = 140
Click on the
Verify in the pre-processor tab that all of the input data has
been converted to a 500m grid
NX = 100
NY = 100
When combining dfs2 files and unstructured data files the dfs2 files
put some constraints on the geometry of the computational mesh
you can create.
If the grids are coincident and
the data is real data (e.g. topography) the finer grid will be
interpolated to the coarser grid using the bilinear interpolation to
the center node.
41
the data is real data, then the grids will be interpolated in the
same way as distributed XYZ and .shp data.
NX = 65
NY = 70
The Water balance items are used during the post-processing of the
results to calculate water exchanges between the various
components
The Hot start data is used for starting transient simulations from the
end of a previous simulation. This allows you to modify things such
as land use over time, or to do scenario analysis from the same
starting scenario.
Gridded output is stored as dfs2 (2D grid time-series files) or dfs3
(3D grid time-series files). If output data is stored too frequently, you
may get very large and unwieldy result files. Thus, before running
the simulation you should consider how often you need to save the
data.
42
X-coordinate
Y-coordinate
Obs 5
24103
8419
Obs 35
13800
17607
Obs 37
17508
20887
Obs 65
8866
25549
43
If you did not enable storing of water balance data, then you
should enable storing of
precipitation rate,
depth to phreatic surface,
head-elevation in saturated zone,
groundwater flow in the X-direction, and
groundwater flow in the Y-direction.
44
45
46
The Detailed Time Series Output dialog lists the Detailed Time
Series results you have chosen to store during the MIKE SHE
simulation.
If you have specified more than 5 items for detailed time series
output, then you will only see a page of links on the main Detailed
timeseries page. The links will direct you to separate .html files with
5 graphs in each.
47
48
Check on the Add XY flow vectors for the head elevation in the
saturated zone plot
The Results Viewer dialog lists the results you have chosen to store
in the MIKE SHE results files.
The XY flow vectors check box adds velocity flow vectors calculated
for each cell.
The Layer no for groundwater items is used to select the numerical
layer number in groundwater models with multiple numerical layers.
Note that the velocity vectors will not appear in the initial time step, but
rather appear first in the second time step.
49
, to add a lens.
50
All the lenses will be assigned the same hydraulic properties. If you
want to assign different hydraulic properties to different lenses, then
you need to add additional lenses (see the step above)
Lenses can also be assigned using polygon shp files.
51
52
53
54
The Results Viewer dialog lists the results you have chose to store in
the MIKE SHE results file. In this exercise, you chose to store the
precipitation (groundwater recharge), depth to phreatic surface,
groundwater head, and the groundwater flow in the x-, y- and zdirections.
55
56
Click in the area of interest to select the points along the profile
line. Double click on the last point of the profile to terminate the
profile line. The profile line is indicated with a thick green line.
57
58
) will
Then,
59
Press the
button on the Results Viewer tool bar to
generate an animation of simulated heads.
Press the
The animation now displays the head distribution at every other time
step, (every 2 days).
60
Press the
Press the
button on the Results Viewer tool bar to
generate an animation of simulated heads for the selected
portion of the simulated area.
The animation file can be played in Windows Media Player and most
other media programs.
61
4.1
As described in Chapter 2, create a MIKE SHE (.she) document file, and save the document, specifying a name such as UZ1.SHE
4.2
MIKE SHE includes several simulation modules. The navigation tree in the user interface depends on your choice of simulation modules.
62
Check Evapotranspiration On
63
Demo Note: The demo mode only allows 800 time steps. If you are
running this exercise in demo mode, you should only run the
simulation for two months.
Specification of the simulation period at this early stage in the model
development is not a requirement. However, it is convenient
because the time-varying input data you specify later is validated
against the simulation period. Thus, when you specify a rainfall timeseries file, the user interface checks to make sure that the timeseries covers the Simulation Period.
4.3
64
NX, NY = 3
Rotation = 0
X0, Y0 = 0
The above steps will create a 3x3 grid file for the unsaturated zone
model. This is the minimum size grid, as it contains only one
calculation point.
The model grid file contains two integer values (1 for the calculation
point and 2 for the boundary points), plus Null values outside the
model area.
65
4.4
For an integrated hydrological model you normally define the distribution of precipitation and reference evapotranspiration in both time and space,
along with the distribution of vegetation in you catchment.
4.4.1 Define Precipitation
In the Precipitation Rate data item
66
Typically, for a 2-D model with a network of gird cells a land use map
would be specified.
Note that there were three Data Type options available:
67
4.5
In this step, you will specify geometry of the soil profile and hydraulic properties for the layers.
4.5.1 Building your Unsaturated Zone Model
In the Unsaturated Flow data item.
68
69
.\Model Inputs\Karup.uzs
Note: Before you click OK, you need to select the Soil type the
file selection dialog. Leave it as Fine Sand.
This dialog is divided into two parts:
The upper part is used to define the soil profile. That is the vertical
distribution of soils that are observed in the field.
The lower part is used to define the numerical grid spacing for
solving the unsaturated zone flow equations.
The Soil type combo box includes a complete list of all of the soil
types that are available the database. You must choose the soil type
here because the soil type is not editable in the main dialog. It has
been done in this way, to avoid slow response times in the Soil
definition dialog when very large databases are being referenced.
70
No of cells = 3
No of cells = 6
No of cells = 44
The numerical grid is usually very fine at the top, where rapid
changes in saturated can occur in response to precipitation.
Typically, the grid becomes increasingly coarse with depth, while
following the soil horizon boundaries.
The combination of negative sign (-8m) and the checkbox for Values
relative to ground means that the groundwater table is 8m below the
ground surface.
The Saturated Zone Component is not included in this model, so no
dialogs for this component are available. However, the Unsaturated
Zone Component requires the groundwater table as the lower
boundary condition, which is the reason that you must specify the
groundwater table here. If the saturated component was included,
the location of the groundwater table would be calculated by MIKE
71
72
SHE.
Step 6 Pre-process the data
4.6
Your have now specified all the input required for the model, including
Up to this point, all of the input data has been specified independent of the numeric model. You have specified only the characteristics of the numeric
model that will be run. Before actually running the model you must run the pre-processor. The pre-processor extracts all of the spatial data that you
have included and applies it to the numerical model that you have defined in the Model Domain and Grid and the Computational Layers. The preprocessor writes all input data to a binary Flow-Input-File (fif file) which is then read by the simulation engine when running the simulation.
4.6.1 Run the Preprocessor
Click on the
The preprocessor will start the MIKE Zero Launch utility, which is
allows you to set the process priority for the simulation.
Click OK
If you are starting a very long simulation, then you can also set up
MIKE Zero to alert you when the simulation is finished.
73
4.7
After running the pre-processor, you can run the actual simulation.
Before running the model, you need to go back to the Setup menu to make a few changes to the simulation specifications, including simulation
period, time-steps and storing of results.
74
75
Set the Storing interval for grid series output (Prec, ET, UZ) to 2
hours.
76
Click on the Add Item icon to add a new line to the table
Then select a Data type for detailed time series output, such as
average water content in the root zone
Now click on the center of the grid to set the coordinates of the
point where you want to obtain a detailed time series output.
77
4.8
Upon successful execution of the model, youre now ready to view the results.
The Results Viewer allows you to view and animate results from all DHI dfs file types. This first exercise will guide you through only the most basic
functionality of the Result Viewer, but you are welcome to explore the rich functionality of this tool.
4.8.1 Locate the Results
After successfully running the model,
The Results Viewer dialog lists the results you have chosen to store
in the MIKE SHE results files.
78
The Result Viewer opens and displays the results for the first timestep in the top layer of the model. The layer number can be easily
changed by right clicking on the grid and selecting properties.
When you click on the movie icon, the Results Viewer loops through
the time series of water content for the displayed cells. It ends with a
message about an .avi file being saved for the movie.
When the movie has stopped (or you have stopped it), click on
the UZ-plot viewer toolbar
button
79
Make sure that the REV:1 view is active and then click on the
Projects menu, and Add Files to Project.
Then click on the Browse button to add the following time series
files
.\Results\UZ1\UZ1_ET_AllCells.dfs2
.\Results\UZ1\UZ1_ET_UzCells.dfs2
Note: the file names will depend on the specified name of
the simulation file.
These files will not be part of your project yet. So, they will not
appear in the list of available files.
Click on the External File button and browse to find the files
The first file above contains the input precipitation rate and the
second file contains the calculated actual ET.
80
This will bring up the Items dialog, where you can select what
items to plot. The top soil cell, and the precipitation, and ET are
clicked on by default
Finally, click on OK
This will display a time series graph with three lines one for each of
the selected items.
The actual evapotranspiration and the precipitation are shown for the
grid cell as they are not dependent on the depth. The water content,
on the other hand, is depth dependent and only displayed for the
selected layers.
These default graph axes are also somewhat poor in this case, since
the precipitation ranges from 0 to 12 mm, yet the water content
ranges only between 0.2 and 0.05.
81
Change the Placement for the water content to the Right Axis
This moves the scale for the water content to the right hand Y-axis
and changes the scale so that you can better see the relationship
between water content, ET and precipitation.
You are welcome to explore these tabs, and try out a few of the
other features. For example, you could try to change the colours of
the graphs, etc.
82
4.9
83
84
5.1
Understand the concepts and associated files for building a MIKE 11 hydraulic model
Understand the properties and attributes that are attached to a simulation file
Understand the properties and attributes that are attached to the following files: cross-section, network, boundary and hydrodynamic files.
Step 1 Create a new MIKE 11 setup
As described in Section 2, create a MIKE 11 (.sim11) document file, and save the document, specifying a name such as River.sim11
The sim11 document contains all user-input required to run MIKE 11. The sim11 document links
the different MIKE 11 components together as it contains the references to the other MIKE 11
modules including
River Network (.nwk11) for specifying the river geometry and connections
Boundary Conditions (.bnd11) for specifying the upstream and downstream boundary
conditions
85
The Models dialog enables you to specify the MIKE 11 models to be used in the hydraulic
model.
The selected options define a hydrodynamic model based on hydrodynamic flow conditions.
86
Under Simulation Period, specify the Start date and End date for the simulation
Start Date: 1. Jan. 1980
End date: 27. Jan. 1980
Under Initial Conditions, specify the hydrodynamic (HD) initial condition.
Select the Parameter File option.
You dont need to specify the Simulation period now. However, it is convenient because the
time varying input data you specify later on will be validated against this simulation period.
Hence, when you specify a discharge time-series file, the user interface requires that the
time-series cover the Simulation Period.
When selecting the parameter file option the initial conditions are read from the HD
parameter file.
87
Specify a result filename of your choice with the suffix .res11. For example,
.\Model\Results\River1\River1.res11
Specify the storing frequency as 1, meaning that the results are stored at every
simulation time step.
The MIKE 11 result files always end with the suffix .res11.
If you dont use the browse button to specify a results path, then the results will be
automatically placed in the current directory.
88
5.2
The map projection for all MIKE SHE files must be NON-UTM.
5.2.3 Save the file
Before you go on, save your network document. For example,
.\Model Inputs\MIKE 11\River1.nwk11
Note: when you save the file in this way, the file is automatically added to your current
project.
89
.\Model Inputs\GIS-Data\Karup0.bmp
Note: The top bar menu depending on the document that is active.
For example if the steps above are only possible if the .nwk11
document is the active document. If you make the .sim11 dialog
active the top menu bar will change.
If a previously geo-referenced image file is loaded. The georeference information is stored in a file with the same name as the
image file but with the suffix .bmpw.
90
In the top button bar, click on the Add New Points tool button,
Using your mouse, start at the river mouth (upper left) and follow the river, clicking the
left mouse button to define river points along on the main branch of the Karup River.
When finished with the main branch, repeat this for the two tributaries, with the first point
of the tributary next to the Karup River.
The points are only used to geo-position the branches and are not used in the calculation
scheme. Thus, the number of points entered does not effect the simulation time. Nor does it
matter what order the points have been input.
Note: If the point locations are not visible or disappear, you can change any of the display
settings for the various components by opening the Display Settings dialog under Settings ->
Network, in the top menu bar.
This image is a map of the Karup River basin, including two main tributaries. The river
source is in the lower right and exits the map area near the upper left corner.
91
In the top button bar, click on the Define Branch' tool button,
Position your mouse at the upstream end (source) of the river (lower right) and hold
down the left mouse button
With the mouse button held down, follow the river points that you previously added until
you reach the downstream end (river mouth) (upper left) and then let go of the mouse
button. This should connect all of your points along the main branch together with a
black line.
When finished with the main branch, repeat this for the two tributaries, starting at the
upstream end of the tributary and ending at the last point before joining the main
branch.
Note: when you define the branch tributaries, you will not be able to connect them to the
main branch. You will do this in a subsequent step.
If you make a mistake while defining the branches, you can delete the branch by clicking on
the Delete Branch tool button,
, and then clicking on the branch that you want to delete.
Remember, though, to click on the Define Branch tool button again.
Note: If the branches are not visible or disappear, you can change any of the display
settings for the various components by opening the Display Settings dialog under Settings ->
Network, in the top menu bar
5.2.8 Network - Define the Branch properties
To open the branch properties dialog
Right click on the branch and choose Edit from the pop up menu
Click on OK
92
Downstream end = outflow
93
This will open the Network Tabular View at the branch properties dialog.
The Network Tabular View can also be opened by using the Ctrl-t keyboard shortcut.
In the Network Tabular View, for each Branch
Change the Topo ID to model cross (The spelling here is important, see Note below)
Note: the current branch in the Tabular View is highlighted on the map
Downstream end = outflow
Note: The Topo ID is referenced to the Cross-section database. That is, if the Topo ID does
not match the Topo ID in the Cross-section database, then the referencing will fail.
Karup
River
Haderup
River
Hauge
Creek
94
Right click on the upstream or downstream river node and select Point Properties from
the pop-up menu
Then change the Chainage value to the following values, where 0 is the chainage at the
uppermost upstream point:
52000
14200
12100
0
The internal notation of MIKE 11 is such that the flow direction is positive with increasing
chainage. This requires that the starting point of the river branch (Chainage = 0) is at the
upstream end of the branch. And the end point of the branch is at the mouth of the river
(maximum chainage value).
However, in many river surveys the downstream end of the river network (ie. the mouth of
the river) is the starting point. In this case, the Flow Direction in the Tabular View must be set
to Negative.
Then select the downstream end of the connecting branch, hold the mouse button while
dragging the pointer towards the connecting point at the main branch. MIKE 11 displays
a line indicating that the branches are connected.
When you use the browse button, only the valid file types that are part of your current project
will be displayed. If you want to use a file that is not yet part of your project, then you can
click on the [External File] button to access a regular Windows explorer dialog. Then you
will be asked if you want to add the file to your project. If you answer Yes, then a short cut to
the file will be added to your project.
5.2.12 Review questions for Step 2
Try to answer the following questions before proceeding with the exercise:
What is the suffix of the network file? What is the main purpose with the network file?
95
5.3
96
Note:
97
Open the network document (.nwk11) by selecting it from the drop-down menu under
Window in the top menu bar.
Check to make sure that the Branch ID and TOPO ID in the network and the crosssection document are consistent (spelled the same).
Check to make sure that the cross-sections are turned on under Settings -> Network,
where you can change any of the display settings for the various components.
5.4
Which two IDs connects the network and the cross-section data?How are the cross-section data geo-referenced on the network?
What is the purpose of chainage values and how are they defined?
What is the purpose of marker values and how are they used?
98
Open the Network editor, by clicking on the Network Editor dialog, or by selecting your
network document from the Window pull down menu in the top menu bar.
Right click on the node at the downstream end (mouth) of the Karup River
99
Repeat this for the upstream end of the Karup River and each of the tributaries
When the boundary conditions are added to the MIKE 11 network and there is a boundary
condition file defined in the simulation file (.sim11 file), then the boundary locations are
automatically added in the Boundary editor.
5.4.4 Boundary - Assign the boundary data to each Boundary Item
Open the Boundary Editor by selecting the boundary (.bnd11) document from the
Window pull down menu in the top menu bar.
Change each of the four boundary item as follows:
For the upstream boundaries (Chainage = 0), the boundary type should be Inflow
For the downstream boundary at the mouth of the Karup River, the boundary type
should be Water Level.
In the file browser, the valid item types in the dfs0 file will be available in the Item
column. In this file, there is only one valid item for each boundary type.
The upstream boundaries are Inflow, but there is no inflow at the source of the river. If you
were simulating only part of a river network, then you would use the measured inflow rate.
At the mouth of the river, you have defined a Water level boundary. You must define at least
one water level boundary, or else the system is indeterminate there might be several valid
water levels if all the boundaries are flow boundaries.
The time series data must be in the MIKE ZERO time series format (*.dfs0 files). You can
use the time series editor to view the dfs0 file by clicking on the [Edit] button. This file is
rather boring, though, because for this exercise, you have defined a constant downstream
water level.
100
5.5
Which types of boundary conditions are normally applied for a hydrodynamic model?
101
Acceleration term
Gravity term
This allows larger time steps and is especially applicable for:
Fast transients
Tidal flows
Steep channels
102
Note: In MIKE 11, you need to make sure your changes are registered before you save.
MIKE 11 was the first MIKE Zero product and not all of the dialog controls register your
changes when you make them. The changes are first registered when you leave the
control. Thus, when you change the default value to 1.0, the change will be lost if you leave
the dialog even if you click Save unless you click in a different control (e.g. click in the
Discharge text box). A quick way to check if your changes have been registered is to always
check that the dialog title bar contains the words Modified . However, this
only reflects the previous change and your last change will still not be registered unless you
have clicked outside of the control in which you made the last change.
5.6
the Add. Output tab lists the additional results that can be saved,
the Time Series Output tab allows you to automatically generate dfs0 time series results files
the Groundwater Leakage tab allows you to simulate baseflow loses from the stream based on a unit gradient, and
103
Your simulation should run, but you will get a number of warning messages.
Warning 65: there is a difference in the bed level
This warning is telling you that, at the point were they join, the bed level in the main branch is
different that the bed level in the tributary. This is normal, but you should look carefully at
such warnings to make sure you dont have a data error.
Warning 47: ... the water level has fallen below the bottom of the slot ___ times.
This warning is simply telling you that your solution is not numerically stable. This is also
normal for this case, because you dont really have any water in the river because it is not
connected to MIKE SHE or a rainfall runoff model. The slot that is referred to is a numerical
trick to keep the river from completely drying out.
Tips: If you encounter problems getting a MIKE 11 simulation to run, the following are some
tips that might make a difference:
Smaller time steps increase the stability of the simulation. However, this will increase
the length of time that the simulation takes to run.
If the time steps are increasing very slowly, you can start subsequent simulations from a
results file using the Hot Start option for the initial conditions.
How are you able to see if all the input data has been entered and is valid prior to starting the simulation?
104
How would you know if the time step affecting the numerical stability of the model?
Step 7 View the results
5.7
105
Select OK
Now, click on a point in the river network where you wish to see the results (Note, the
cursor will change when you hover over a valid calculation point),
Alternatively, you can click on the List button in the Data Type Selection dialog, which will
give you a list of available calculation points.
The time series plot with the selected data is then shown.
Right mouse click -> Add TS to add additional time series to the plot.
Right mouse click -> External TS to add external dfs0 files to the plot.
106
107
Shown on the profile plot are the Bed level, the Bank level, and the
Maximum and minimum water level or discharge (depending on the
chosen data type).
Standard animation tool buttons are available for Play
Pause
, Stop
, and
5.8
The results to this point are rather boring because there is not really any water being added to the river. Normally, the hydraulic model is coupled to
an inflow boundary or a rainfall runoff model. If the MIKE 11 model is coupled to MIKE SHE, the MIKE SHE is essentially a distributed rainfall-runoff
model.
In this step, you will create a simple rainfall-runoff catchment based on the Karup catchment.
Demo note: The following step cannot be done in Demo mode.
108
In the Catchments tab, add a catchment by clicking on the [Insert catchment] button
2
2
In this step, you are creating a catchment. The catchment has an area (440 km ), but not a
3
location. When it rains, 10mm of rain in one day will generate 4.4 million m of potential
runoff. The NAM model apportions this potential runoff into the various components of the
hydrologic cycle and calculates an actual runoff including the timing the runoff hydrograph.
The NAM model does this by means of various of the factors and time constants that you
must specify. In this exercise, you will leave all of these factors at their default values, but in
a real case, you would calibrate all of these factors against the measured stream flow
hydrographs.
The problem is that many of these factors are not physically based. They represent some
physical process, but are lumped together for the entire catchment. Hence, rainfall runoff
109
or
This will add a new time series item at the end of the list. In the new
time series item, change
110
You have now filled item 10 with the amount of rainfall in each 24 hour time step that was
measured at Station 9.
In a real model, you would do the above calculation for each rainfall station and distribute the
rainfall across the catchment based on Theissen polygons.
For this exercise, you will limit ourselves to assigning the rainfall from one station to the
entire catchment.
In the Project Explorer double click on the PotentialEvap.dfs0 file located in the Time
111
Use the Browse button to locate the two files that you modified above.
112
Add three items, by selecting the line in the table and clicking
the Insert key on your keyboard
Hauge Creek 68 km
113
What is the difference between a step-accumulated and mean step-accumulated time series?
114
6 Integrated Exercise
Overall Objective
Extend the SZ1 model to make it into a fully integrated groundwater-surface water model
Important learning objectives
Understand how the River Module interacts with the Saturated Zone Module
Understand how detailed time-series outputs can be extracted and combined with field data for calibration purposes.
As described in Section 2, open the MIKE SHE (.she) document file that you created in Exercise SZ1, and use the Save As command to save the
document to a different name, such as Integ1.SHE.
115
Demo Note: If you are using the demo version of MIKE SHE do not
extend the simulation period.
116
6.2
You will now add a river to the groundwater model that you created in the SZ1 exercise. In this exercise, you will use an existing MIKE 11 river
setup that is slightly more detailed than the one you created in the River1 exercise.
6.2.1 Select simulation modules
In the Simulation Specification dialog
Your model now has a Rivers and Lakes branch in the Data Tree.
Press the
117
118
If you did not do the River exercise, then you should carefully work through this step. If you did the River exercise, then can skip this step or simply
note the differences between this setup and one you created.
6.3.1 Explore the MIKE 11 simulation document
The sim11 file contains a complete river model setup. You are not
going to build a river model as part of this exercise.
The Simulation editor includes five tabs.
The Models tab allows you to select the model components.
The Input tab allows you define the links to the model input files. A
typical MIKE 11 model for MIKE SHE requires the following
documents:
river network (nwk11),
cross-sections (xns11),
boundary conditions (bnd11), and
hydraulic parameters (HD11).
The Simulation tab allows you to set the time step and simulation
length. However, the simulation length is overridden by MIKE SHE.
The Results tab allows you to set the output file name and storing
frequency for the output. In dynamic simulations the time step for
MIKE 11 can be quite small, so it is often necessary to reduce the
storing frequency.
The Start tab allows you to see if there are any data input errors in
your setup and start the simulation when you are ready.
119
Press the
Selecting View from the top menu and then Tabular View or
In the Branches Dialogue, note that the Branch Type for all
branches are set to Kinematic Routing
A regular branch will calculate the water level based on the SaintVenant equation (Kinematic, Diffusion or Dynamic Wave
formulations). For detailed simulations, you would generally use
regular branches.
However, often it is convenient to use simpler routing formulations,
where the water in the river is moved down the river without
120
121
122
click OK.
The marker values in the table define the extent of the crosssection to be used in the simulation.
123
Chose Edit in the pop-up menu, and select the Boundary item
This will open the boundary editor with the current boundary point
highlighted.
Now take a quick look at the boundary specifications in MIKE 11.
All the upstream ends are defined as Inflow boundaries with zero
inflow. The downstream mouth of the river is defined as a water level
boundary.
124
6.4
Your model now has an Overland Flow branch in the data tree.
125
The Karup catchment is quite sandy, and in this simulation there are
no serious storm events. Thus, in reality, overland flow is
insignificant for this simulation.
However, the overland flow module is required whenever the
channel flow component is included. You can run overland flow
without the channel flow component but not the opposite. If you do
not want to include overland flow you can essentially disable
overland flow by specifying a Mannings M = 0.
If you left in the overland flow component, the overland flow
simulation would require that the model run with small time-steps (560 minutes) which would slow down the computation significantly.
6.5
126
127
Click on the
icon to start the pre-processor, which will start
the MIKE Zero Launch utility.
Click OK
128
Go to the River Links Item in the data tree to view the pre-processed
river links:
129
6.6
You will now view some of the outputs of this exercise using the Result Viewer. It is always a good idea to run and evaluate your model as you are
setting it up. Otherwise, there is a danger that you when you are finished setting up a big model, you will have a lot errors that are difficult to track
down.
6.6.1 View Groundwater Level Results
In the Result Viewer dialog:
6.7
Look at whatever outputs you may find interesting, such as the SZ Exchange with river and the SZ drainage flow from point?
Is the model predicting any significant drain flow? Why or why not? What is happening to the drain water in this exercise?
You will now make the simulation a bit more realistic by adding distributed rainfall data.
130
Press
.\Model Inputs\Maps\Precipitation.dfs2
You are now using a dfs2-grid code file to distribute rainfall timeseries data. Each code (area) now needs to be associated with a
rainfall time-series. The grid file contains 9 different codes (1-9). The
value of the code is not important and may be anything. Each area
(defined by a code) just needs to be associated with a rainfall timeseries.
Station areas may also be assigned using .shp file polygons.
131
At the bottom of the file selection dialog, under Items, select the
appropriate precipitation station from the combo box list.
Press Ok.
6.8
In the SZ1 exercise, subsurface drains were included 0.5 meter below ground surface throughout the model domain. Thus, whenever the water
table goes above the drainage level, water will drain from the saturated zone. In the SZ1 exercise, this drainage was exported from the model
domain. You will now change the drainage setup so that drainage water is routed to the river instead.
132
Leave the Level and Time Constant the same as in the SZ1
exercise.
133
134
The map now displays your vegetation distribution. The map (dfs2
file) contains 4 different integer codes that define 4 different areas.
You now need to define the vegetation types and growth function is
are associated with the 4 different areas.
135
Repeat the above steps for each line in the Crop Development
table, with a start date of 1970, 1971, etc.
136
137
138
The soil map contains three different code values, which now need
to be associated with three soil profiles.
Repeat the above for the other two soil types using
139
For Grid Code = 3 use Coarse Sand in the for the upper 2
meters and use Fine Sand in the remaining 35 meters
140
141