Annex 1: Mike11 Tutorial For The Mejerda Model Users: AN1.0 Introduction

The Study on Integrated Basin Management Mejerda Inundation Analysis Model
Focused on Flood Control in Mejerda River Explanation Note Annex1: MIKE11 Tutorial Mejerda
ANNEX 1 : MIKE11 TUTORIAL FOR THE MEJERDA MODEL

USERS
AN1.0 Introduction
This annex was prepared as an introduction of building the 1-D (MIKE11) Mejerda
Model for the users who are not familiar with the MIKE software. For the Mejerda
Model, one 1-D unsteady hydraulic analysis model was built using MIKE11. The
following figure schematically shows an example of a MIKE11 model and its required
inputs.
Ghardimaou
Ghardimaou
Inflow at
Cross Section (@ about 500m)
Runoff from Sub-
Jendouba
catchment (HY-U2p11)
Mellegue R.
Inflow
Mellegue Dam
Roughness Coefficient (Manning's n) Tessa R. Runoff from Sub-
Inflow catchment (HY-U2p12)
Tessa Dam Inflow

Mejerda R .
Bou Heurtma R.
Bou Heurtma
LEGEND Bou Salem
Dam
Inflow at upstream
boundary
Sidi Ismail
Sidi Salem Reservoir
Lateral Inflow Water Level
Result of Reservoir
Operation Analysis
(by MIKE BASIN)
Sidi Salem Dam
Source : Study Team

Figure AN1.1 : Example of MIKE11 Model (Mejerda, Upstream of Sidi Salem Dam)
The major inputs for the 1-D inundation analysis model are data regarding river channel
alignment (coordinates), cross sections, bed resistance, inflow hydrographs, downstream
water levels, simulation time steps and other hydraulic parameters. One MIKE11 model
applied to the Mejerda basin consists of the following input and simulation files, which
acquire these required data. (See Part II of the Explanation Note on Inundation Analysis
Model for the Mejerda River BPasin)
Nippon Koei Co.,Ltd. AN1-1 June 2008

Simulation Data Network Data

(**.sim11) (**.nwk11)
Cross Section Data

(**.xns11)
Boundary/ Inflow
Data
(**.bnd11)
Hydrographs, Water Levels

(Time seriese data)
(**.dfs0)
Hydraulic (HD)
Parameters
(**.hd11)
Note : (**.sim11) etc. : File extension name
Source : Study Team

Figure AN1.2: Overall Structure of MIKE11 Model for Mejerda Model
This annex describes basic methodologies of the following work items of MIKE11
modelling, referring to a simple sample model with nine cross sections. (Files for this
example were provided to the trainees during the training (in the folder Example
M11_Mejerda_byJICA Team).) These items are listed in order of the actual procedure
of modelling.
1. Preparing time series file (**.dfs0)
2. Preparing network file (**.nwk11)
3. Preparing cross section file (**.xns11)
4. Preparing HD (hydrodynamic) file (**.hd11)
5. Preparing boundary file (Empty file) (**.bnd11)
6. Preparing simulation file (**.sim11)
7. Inputting boundary data (**.bnd11)
8. Simulation (**.sim11)
9. Viewing result file (**.res11)
Upstream end
Source : MIKE11 Network window, Network File prepared by the Study Team
Figure AN1.3: Channel Alignment of a sample model used in this Annex (Network Editor)

Box AN1.1: NOTE for French Operating System (Windows) Users
If unknown strange errors are observed, changing the numbering system might improve the
situation.
A point [ . ], not a comma [ , ], is suggested to be used as a decimal point in the operating system.
(For instance, one thousand five hundred should be expressed like 1500.0 not like 1500,0 .)
How to change or confirm the numbering system:

[Control Panel] [Region and Language] Change setting only of the numbering system or Change
language selection to English (UK)
(English (UK) is more convenient than English (US), because it applies a 24 hour system for
showing hours, while English (US) employs a 12 hour system with a.m./p.m..)
Box AN1.2: Note Regarding Inputting Data of MIKE11
Users should keep the following issues in mind when modelling MIKE11.
Branch Name (River Name), Topo ID and Chainage in Cross Section (xns11) and Network
(nwk11) Files should be exactly the same.
AN1.1 Preparing Time Series File
(1) File extension : *.dfs0
(2) Example of time series data :

Hourly inflow discharge data at Ghardimaou and other gauging stations (hydrograph)
(3) Procedure :
Prepare an excel file Make a dfs0 file Copy data in excel file to dfs0 file
(i) Prepare an excel file
1st column : Time (hourly)

2nd column - : Hourly Data
(ii) Make a dfs0 file
[All Program] [MIKE BY DHI] [MIKE11] [MIKE11]

MIKE ZERO Time Series

(.dfs0)
2 3
5
Select [Blank Time Series]
on the next screen
Type necessary information
Select Equidistant Calendar Axis
Starting time of the excel data
The number of lines in the excel data
Automatically filled
Select Discharge

Repeat same procedures for

3 Jendouba and Bou Salem
2
A new line appears.
Repeat same procedures

and complete all items
1
2 Check: This column should

be instantaneous.

Save **.dfs0 file in an appropriate folder
(iii) Copy data in excel file to dfs0 file
Select a range of data cells

to be copied to dfs0 file
2 Execute Copy (ctrl + C) command on excel
Paste
The data are copied

on this table.
Graphs appear
automatically.
Source : Study Team
AN1.2 Preparing Network File

(1) File extension : *.nwk11
(2) Major information contained in a network file :

River name
Coordinates of cross section locations
Chainage (Distances of cross sections from the upstream end)
(3) Procedure :
Prepare an excel file and text file Make a nwk11 file Import text file data to nwk11
file and input other necessary data on nwk11 file
(i) Prepare an excel file and text file
Prepare an excel file based on topographic survey result like below.

These columns are used for network data, and

should be in this order
Check : 0 (zero) should

be at upstream end.
Select this range 2

Execute Copy (ctrl + C)
command on excel
Coordinate at the Cumulated distance

centre of cross from upstream end
section
1 Open a new notepad file

Execute Paste (ctrl + V) command
Dont worry even if data

dont line up a tandem.
Save **.txt file in an appropriate folder
(ii) Make a nwk11 file
MIKE 11 River Network

(.nwk11)
2 3

3
1
2 Select
UTM_Carthage
Coordinate for Mejerda upstream model

X Y
Lower left corner 446000 4025000
Upper right corner 520000 4060000
(iii) Import text file data to nwk11 file and input other necessary data on nwk11 file
[File] [Import] [Point and Branch Data from Point-Branch ASCII File...]
Select meter for unit
Select the **.txt file created in (i)

Save **.nwk11 file in an appropriate folder
[File] [Import] [Point and Branch Data from Point-Branch ASCII File...]
[View] [Tabular View...]

Information in this view are filled automatically based on the imported text
file, except for Topo ID
1 2 3 4
Network Confirm this is Confirm this is

Branches Positive Regular
Type
2007_1
AN1.3 Preparing Cross Section File
(1) File extension : *.xns11
(2) Major information contained in a cross section file :

River name
Cross section ID

Chainage (Distances of cross sections from the upstream end)

Cross section shapes (X, Y)
Roughness coefficient
(3) Procedure :
Prepare an excel file Make an xns11 file Input data on the xns11 file including
copying data in the excel file to the xns11 file
(i) Prepare an excel file
Prepare an excel file based on topographic survey result like below (one example).
These columns are used for inputting to
MIKE11 and should be in this order. A chart like this in the excel
file is useful for checking
data.
X and Y of cross
section
(ii) Make an xns11 file
1
Cross Section File
MIKE 11 (.xns11)
2 3
Save **.xns11 file in an appropriate folder
(iii) Input data on the xns11 file including copying data in the excel file to the xns11 file

River Name: MEJERDA-up

Topo ID: 2007_1
First chainage: 0 (Value of Chainage (distance from
the upstream end) for each cross section)
The above three items should be the exactly same to

the information in the network file.
Cross section ID: UP-349
1
Select this range
2
Execute Copy (ctrl + C) command on excel
1
Highlight these two columns
Execute Paste (ctrl + P) command

Cross section shape is

shown here.
X and Y data in excel

are copied on these
columns.
Mannings n:
Left high flow: 0.05
1 Right high flow: 0.05
Low flow: 0.04
Select position of Mark4

Press 4 on keyboard
(See (v) for brief
explanation of Marks)
3
Repeat for Mark 5
on right bank
Click Insert Cross Section and repeat the same procedures for all cross sections
[Cross-Sections] [Apply to all Sections...]

Check Recompute All 1
(iv) Practice : How to change inputted data in all cross sections at the same time
[Cross-Sections] [Apply to all Sections...]
Input
Left high flow: 0.055
Right high flow: 0.055
Low flow: 0.045
Check this one
2
(v) Memo : Function of Marks (See the software manuals for further details)

Mark 3
Mark 1 These parts of a cross

section are not used for
simulation.
Mark 4
Left high flow channel Right high flow channel
Mark 5
Low flow channel
Mark 2
(lowest)
AN1.4 Preparing HD (Hydrodynamic) File

(1) File extension : *.hd11
(2) Major information contained in a cross section file :

Initial conditions
Additional output files
(3) Procedure :
Make an hd11 file Input necessary information
(i) Make an hd11 file

MIKE 11
HD Parameters
2 (.hd11)
(ii) Input necessary information
[Initial] Check Water Depth Water depth : 1.5m

[Add. Output] Check Frude Number
AN1.5 Preparing Boundary File (Empty File)

(1) File extension : *.bnd11
(2) Procedure :
Make an empty bnd11 file (Further procedures should be conducted after preparing a
simulation file. See Section AN1.7)
(i) Make an empty bnd11 file
MIKE 11
2 Boundary Conditions
(.bnd11)

Save **.bnd11 file in an appropriate folder
AN1.6 Preparing Simulation File

(1) File extension : *.sim11
(2) Major information contained in a network file :

Directories and names of input files
Simulation time step and period
Directories and names of a result file
(3) Procedure :
Make a sim11 file Specify directories and names of input files Input simulation and
result information
(i) Make a sim11 file
1
Simulation File
(.sim11)
MIKE 11
2 3
Modules
1
Check Hydrodynamic
2
Select Unsteady
3

Save **.sim11 file in an appropriate folder
(ii) Specify directories and names of input files
1 Input
Specify file directories and names of the

prepared input files:
Network
Cross-sections
Boundary data
HD Parameters
(iii) Input simulation and result information
Fixed time step, 10 sec
Simulation Start: 11/01/2003 7:00:00

Simulation End: 21/01/2003 7:00:00
Select Steady state

Specify directory and name of result Storing Frequency

file to be stored. 360 Time step
File name: Res_MejUp_demo.res11
(iv) Input boundary data
See the next section
AN1.7 Inputting Boundary Data
(1) File extension : *.bnd11
(2) Data/information determined by the boundary file

Chainage (location) and time series of boundary inflow/ water level
Upstream boundary of the demo model: Hourly inflow discharge
Downstream boundary of the demo model: Hourly water level
(3) Procedure :
Open network editor through sim11 file Input boundary data
(ii) Open network editor through sim11 file
1 Input
Opened Network File
Zoom tool
Cross sections look like this (a square and a

line) , if there is no error in sim11, nwk11 and
xns11 files.
If cross sections on this view look just dots,
check these input and simulation files.

(ii) Input boundary data
Downstream end
Right click on upstream end

[Insert] [Boundary] [Hydro
Dynamic]
Upstream end
This line automatically is

added in bnd11 file Automatically filled
Select Open
(for up- or downstream end) Select Inflow
(for discharge)

Click targeted file:

TS_Q_MejUp_demo.dfs0
Select Ghardimaou
Repeat same procedure at two more

cross section locations
1
Information to be input:
Information to be input: Open
Point Source Inflow
2
Inflow TS_WL_MejUp_demo.dfs0
TS_Q_MejUp_demo2.dfs0 DownEnd
Middle
After inputting boundary data

successfully, a blue square appears on a
cross section.
Boundary editor dont ask you Save changes? before closing window!!
Click this icon and save changes before closing this window. Otherwise, changes
might be lost !!
Open: Up- or downstream end

Point Source: inflow at points other than up- or
downstream end

AN1.8 Simulation
Open Start page of the sim11 file.
If a yellow or red sign appears

here, model would have an error
/ errors.
Click this
to start
Error / warning
messages appear here
AN1.9 Viewing Result File
(1) File extension : *.res11

(2) Application used : MIKE VIEW
(3) Operations :
(i) Open a result file
[All Program] [MIKE BY DHI] [MIKE11] [MIKE VIEW]
Select
MIKE 11 DFS Files (*.res11)

Select and click the targeted

file
Res_MejUP_demo.res11
Click Open
Click [OK] on next screen
(ii) View profile
Double click on the river

channel
Click [OK] on next screen Select Water Level

For animation
(iii) View cross section
2
Click on the targeted position
(on a blue symbol).
For animation

(iii) Copy maximum water surface profile data to excel
Select Water Level
3
List
Select these columns
River name & Max. Max.

Chainange Water Level Time
2 Execute Copy (ctrl + C) command
3 Execute Paste (ctrl + V) command on excel
These data can be used for further analysis, including for making a water surface profile
in excel.

Republic of Tunisia
The Study
on
Integrated Basin Management
Training
Focused on Flood Control on
in Inundation Analysis Model (MIKE FLOOD)
Mejerda River for
the Mejerda River Basin
Training
on
Inundation Analysis Model (MIKE FLOOD) Presentation Material
for for
the Mejerda River Basin Day 1 (4 June, 2008)
June 2008
Nippon Koei Co., Ltd.
Hydrology/Hydraulics/Runoff and Sediment Analyses
TOTSUKA Natsuko
Purposes of Training Contents of Training

Lecture Type
Obtain basic information of the inundation 1-1: What is MIKE FLOOD
1-2: Overview of the Mejerda Model
analysis model for the Mejerda basin
2: MIKE11 Mejerda Model
prepared under the JICA Study
Acquire fundamental knowledge on how to
4: MIKE FLOOD Mejerda Model
operate the inundation analysis model
Software practices using simple sample
prepared under the JICA Study using MIKE
models (demo version)
FLOOD
Practices how to operate and update the
3 Mejerda inundation analysis model 4
Contents of Todays Presentation (1/2) Contents of Todays Presentation (2/2)

Topic 1: What is MIKE FLOOD Topic 2: Overview of the Mejerda Model
Outcomes of inundation analysis Overall Structure of the Mejerda Model
(What can be obtained form inundation Major inputs for the Mejerda Model
analysis?) Simulation Cases for the Mejerda Model
Functions of MIKE 11, MIKE 21 and General idea on how to modify / update
MIKE FLOOD, and their relations the Mejerda Model
Overall procedure of inundation
analysis with MIKE FLOOD
5 6
Lecture_Overall-1
What is MIKE FLOOD ?
Name of the software used for the
Topic 1: inundation analysis
under the JICA Study
What is MIKE FLOOD ? before explaining the software..
Please see what can be obtained from

the inundation analysis .....
Outcomes of inundation analysis Outcomes of inundation analysis

(What can be obtained form inundation analysis?) (What can be obtained form inundation analysis?)
Major outcomes of inundation analysis Example 1: Water Surface Profile
MIKE FLOOD
INPUT Simulation OUTPUT Time series data
Inflow Discharge Water level Design water level
Channel condition Inundation Area
... etc. ... etc.
Post-processing
Water surface profile (Design water level)
Inundation map
The inundation area (Numerical data) 9 10
Outcomes of inundation analysis BEFORE Project : 10-Year Flood

(What can be obtained form inundation analysis?)
Example 2 : Inundation Map
BEFORE Project : 5-Year Flood 11 12
Lecture_Overall-2
BEFORE Project : 20-Year Flood BEFORE Project : 50-Year Flood
13 14
Outcomes of inundation analysis Outcomes of inundation analysis

(What can be obtained form inundation analysis?) (What can be obtained form inundation analysis?)
Example 3 : Inundation Area (numerical data)
Unit : ha
Depth <0.5m 0.5-1m 1-2m 2-3m 3-4m
Delegation
BEJA SUD 26 14 53 26 18
BOU SALEM 28 639 20 22 15
DOUAR HICHER 259 40 0 0 0
EL BATTANE 425 377 541 253 32
..... ..... ..... ..... ..... .....

Example: 20-year Flood with
improved reservoir operation Note : Above table shows an example of data type only. The values in the table
do not based on actual computations.
15 16
MIKE 11, MIKE 21 and MIKE FLOOD MIKE 11, MIKE 21 and MIKE FLOOD
MIKE FLOOD : Software used for the MIKE 11
inundation analysis under the JICA Study
Unsteady & Two dimensional simulation
For one dimensional (1-D) hydraulic
Commercial software produced by DHI (Danish analysis
company) Simulation of hydraulic conditions (water
Combination of three applications : MIKE 11, level, discharge, etc.) in river channels
MIKE 21 and MIKE FLOOD Unsteady analysis function available
MIKE 11 : 1-D analysis application Independent
(Applied to the Mejerda Model)
MIKE 21 : 2-D analysis application
software
Similar software : HEC-RAS (by USACE)
MIKE FLOOD : Combine 1-D and 2-D Models17 18
Lecture_Overall-3
MIKE 11, MIKE 21 and MIKE FLOOD MIKE 11, MIKE 21 and MIKE FLOOD
MIKE 21 Functions and Relations
MIKE21 MIKE FLOOD MIKE11
2-D Analysis Combining 1-D and 2-D 1-D Analysis
For two dimensional (2-D) hydraulic Simulating hyraulic
Interrelating 1-D and 2-D
Simulating hyraulic
conditions conditions
models
analysis (water depth, velocity,
etc.)
Defining overflows along
interrelated reaches
(water depth, velocity,
etc.)
on flood plain in river channels
Simulation of hydraulic conditions (water

level, velocity, etc.) on flood plain, in a gulf,
or in estuary ... etc. (flow in grid data)
Flood plain defined
by MIKE21 Lateral Link defined
by MIKE FLOOD
River channel defined
by MIKE11
19 20
MIKE 11, MIKE 21 and MIKE FLOOD Overall Procedure of Inundation Analysis
Functions and Relations One Dimensional (1-D) Modelling Two Dimensional (2-D) Modelling
Overall River channels and Cross sections
1-D sim. Inflow hydrographs Flood plain (grid)
By MIKE 11 Procedure Hydraulic parameters

Structures etc.
etc.
(1/2) MIKE11 MIKE21
Judged by 1-D sim. Combine 1-D and 2-D Models
MIKE FLOOD By MIKE 11 Associate 1-D and 2-D Models

Define where and how overflowing from 1-D channel can
occur
MIKE FLOOD
Simulation (Start on MIKE FLOOD)
1-D Output 2-D Output
2-D sim. Time series of Time series of

Q, h, v, Fr etc. h, v, etc.
by MIKE 21 at each section of channel in each grid of flood plain
21 22
Overall Procedure of Inundation Analysis Overall Procedure of Inundation Analysis

Overall Procedure (2/2) Notes on the procedure:
MIKE11 and MIKE21 models have to be
Simulation (Start on MIKE FLOOD)
completed before making the MIKE FLOOD
1-D Output 2-D Output model.
Time series of Time series of
Q, h, v, Fr etc.
at each section of channel
h, v, etc.
in each grid of flood plain MIKE FLOOD controls the start of the
Post-Processing
simulation only. Results are actually
MIKE ZERO Result Viewer, MIKE
MIKE VIEW, Excel etc.
ZERO Tool Box, GIS, Excel etc. produced by MIKE 11 and MIKE 21.
Post-processing procedures are necessary to
e.g. Water Surface Profile e.g. Inundation Map
Water level
Inundated area
Max. inundation depth
develop required outcomes of the inundation
23 analysis. 24
Lecture_Overall-4
Overall Procedure Overall Procedure
MIKE 11 Result (1-
(1-D) MIKE 21 Result (2-
(2-D)
25 26
Contents of Todays Presentation (2/2)

Topic 2: Overview of the Mejerda Model
Topic 2: Overall Structure of the Mejerda Model
Major inputs for the Mejerda Model
Overview
of Simulation Cases of the Mejerda Model
the Mejerda Model General idea on how to modify / update
the Mejerda Model
28
Overall Structure of the Mejerda Model Overall Structure of the Mejerda Model
Upstream Model River channel model Ghardimaou
by MIKE11
Mejeda Model
Ghardimaou Flood plain (grid)
Inflow
model by MIKE21
Sidi Salem Dam Jendouba
Runoff from Sub-
catchment
Upstream Model Downstream Model Mellegue R.
Interrelating
(Upstream of Sidi Salem Dam) (Downstream of Sidi Salem Dam) Inflow channel and flood plain
Mellegue Dam
by MIKE FLOOD
MIKE 11 Model MIKE 11 Model Tessa R. Runoff from Sub-
catchment Bou Heurtma
Inflow Dam
MIKE 21 Model MIKE 21 Model Tessa Dam Inflow
Mejerda R
Bou Heurtma R.
Bou Salem
MIKE FLOOD Model MIKE FLOOD Model
(Definition file) (Definition file) Sidi Ismail
Water Level
29 30
Sidi Salem Dam
Lecture_Overall-5
Overall Structure of the Mejerda Model Purposes of Inundation Analysis
in the Mejerda JICA Study
Downstream Model Sidi Salem Dam
To clarify flood characteristics (flow direction,
Outflow from
Sidi Salem DamSiliana Dam Siliana R.
Sidi Salem Dam
inundated area and depth, etc.) Area, Location
Inflow
Estuary Slouguia To examine and compare inundation BEFORE
Bridge Mejez El Bab
Runoff from Sub-
and AFTER project. Effects & Impacts
River channel model
Improvement of reservoir operation
catchment
by MIKE11 El Herri
Improvement of river channel

Laroussia Dam (Weir)
El Battane Weir
conditions (Structural measures)
Interrelating Jedeida
channel and flood plain Runoff from Sub-

catchment To determine design water level for the master
by MIKE FLOOD Flood plain (grid)
Tobias Dam
(Weir)
model by MIKE21 plan level of design
Sea Water Level Sea
(Gulf of Tunis) 31 The simulation model should be built to fulfill these purposes. 32
Major Input for the Mejerda Model Major Input for the Mejerda Model
Upstream 1-
1-D Model Result of Downstream 1-
1-D Model Sidi Salem Dam
Runoff
Ghardimaou
Ghardimaou
Inflow at
Analysis
Siliana Dam Siliana R. Outflow from
Sidi Salem Dam
Runoff from Sub- Inflow
Jendouba
catchment (HY-U2p11)
Slouguia
Mellegue R.
Inflow Bridge Mejez El Bab

Runoff from Sub-
Roughness Coefficient (Manning's n) catchment
Mellegue Dam
El Herri
Roughness Coefficient (Manning's n) Tessa R. Runoff from Sub-
Inflow catchment (HY-U2p12) Laroussia Dam (Weir)
Tessa Dam Inflow

Result
LEGENDof El Battane Weir
Mejerda R
Bou Heurtma R.
Bou Heurtma Reservoir Operation
Inflow at upstream Jedeida
Result
LEGEND of Reservoir Bou Salem
Dam boundary
Inflow at upstream Analysis Runoff from Sub-
Operation
boundary Analysis Sidi Salem Reservoir
Lateral Inflow catchment
Sidi Ismail Tobias Dam
Lateral Inflow Water Level
Dam Outflow discharge (Weir)
Dam Outflow Discharge
(or water level) Sea Water Level Sea
Sidi Salem Dam 33 (Gulf of Tunis) 34
Major Input for the Mejerda Model Simulation Cases of the Mejerda Model
MIKE 11 Model Alternative cases analyzed under the Study
Reservoir
Inflow to River Channel Operation Analysis Combinations of .....
Outflow from dams Probability of inflow
Runoff from subcatchment Runoff Analysis 5-year, 10-year, 20-year, 50-year
Cross Section and Profile River channel shape
Cross section (X, Y)
Topographic Survey Present condition
Cross section distances
Design alternatives (Excavation, embankment)
Positions of cross sections (Coordinates)
Roughness coefficient Inflow by different reservoir operation
MIKE 21 Model Present standard operation
Grid Elevation on Flood Plain Improved dam operation
35 36
Lecture_Overall-6
Simulation Cases of the Mejerda Model Simulation Cases of the Mejerda Model
Selected Cases of the Mejerda Model
Reservoir Operation Analysis
Zone Probability Flood Control Option
U1 10-year fl. Present
(-Mel Conf.) Reservoir Operation
Flood Control Reservoir River Channel
Option Operation
Reservoir Operation + River Improvement
Present Present standard Present condition
U2 20-year fl. Present
operation
(Mel. Conf.) Reservoir Operation Reservoir Recommended Present condition
Reservoir Operation + River Improvement Operation improved operation
D1 & D2 10-year fl. Present Reservoir Recommended Planned (Master
Reservoir Operation
Operation + River improved operation plan design by the
Improvement JICA Study
Reservoir Operation + River Improvement
Note : The above tables lists the selected cases. Many other cases with different
probabilities, alternative design and other conditions were analyzed during the JICA Study. 37 38
General Idea on How to Modify / General Idea on How to Modify /

Update the Mejerda Model Update the Mejerda Model
I want to modify/update .... I want to modify/update ....
Cross Section and Profile MIKE 11 How and where overflow
MIKE FLOOD
Cross section shape (X, Y) (e.g. Model occurs
change design) Length of linked
Model
Positions of cross sections reaches, etc.
(Coordinates)
Reservoir operation go back to
Roughness coefficient
Outflow from dams, Reservoir Operation
Bridges, weirs, etc. Analysis
etc.
Flood Plain Grid Data (eg. grid size, MIKE 21
ground elevation. etc.) Model MIKE 11 Model 40
39
Lecture_Overall-7
Republic of Tunisia
The Study Training
on
Integrated Basin Management on
Focused on Flood Control Inundation Analysis Model (MIKE FLOOD)
in
Mejerda River for
Training
on Presentation Material
Inundation Analysis Model (MIKE FLOOD) for
for
the Mejerda River Basin Lecture 2
(MIKE 11 Mejerda Model)
June 2008
TOTSUKA Natsuko
Contents of Training Contents of Presentation (1/2)

Lecture Type MIKE 11 Mejerda Model
1-1: What is MIKE FLOOD MIKE11 Model Structure
1-2: Overview of the Mejerda Model MIKE11 Modelling Procedure

2: MIKE11 Mejerda Model Some Information of Input Files
3: MIKE21 Mejerda Model Time Series File (**.dfs0)
4: MIKE FLOOD Mejerda Model Network File (**.nwk11)
Software practices using simple sample Cross Section File (**.xns11)
models (demo version) Boundary File (**.bnd11)
Practices how to operate and update the Network File (**.nwk11) Structures
Simulation File (**.sim11)
Mejerda inundation analysis model 3 4
Contents of Presentation (2/2) MIKE11 Model Structure

Upstream Model
Bou Heurtma
Example of Errors Flood plain (grid)
model by MIKE21
Dam Sidi Salem
Bou Heurtma
Dam
MIKE11 Model as a Part of MIKE FLOOD Assumed max.limit
Assumed Max. limit
of
Bou Salem
potential flood plain
of potential area
flood Mejerda R.
Model plain Sidi Ismail
Tessa R.
River channel
model
Mejerda R.
Jendouba
Ghardimaou
.
R
e
gu
le
el
M
No inundation
(Land value in
Mellegue Dam MIKE21 bathymetry)
5 Tessa Dam 6
Lecture_M11-1
MIKE11 Model Structure MIKE11 Model Structure
Upstream Model Downstream Model
Assumed Max. limit of
Ghardimaou
Assumed max. limit of
(Gulf of Tunis)
Inflow at
Ghardimaou potential flood plain area
potential flood plain
Sea
(@ about 250m) Tobias Dam
Cross Section
Runoff from Sub- River channel model
Jendouba
catchment (HY-U2p11) by MIKE11
Mellegue R.
No inundation
(Land value in Jedeida
Mellegue Dam
Roughness Coefficient Runoff from Sub-catchment MIKE21 bathymetry) Mejerda R.
Tessa R.
(Manning's n) (HY-U2p12)
Larrousia Dam
Tessa Dam El Herri
Mejerda R
LEGEND
Bou Heurtma R. Bou Heurtma
Inflow at upstream Bou Salem Dam
Mejez El Bab Flood plain (grid)
boundary Sidi Salem model by MIKE21
Lateral Inflow Sidi Salem Reservoir Dam
Sidi Ismail
Result of Reservoir Water Level
Operation Analysis
Slouguia
(by MIKE BASIN)
Sidi Salem Dam Siliana R.
7 8
Siliana Dam
MIKE11 Model Structure MIKE11 Model Structure

Downstream Model Sidi Salem Dam As a part of MIKE FLOOD model, MIKE11
Cross Section Mejerda Model was designed so that....
(@ about 500m)
Siliana R.
Outflow from The model covers river reaches located on the potential
Sidi Salem
Siliana
Slouguia flood plain (corresponding to MIKE21 bathymetry).
Dam
Mejez El Bab
Runoff from Sub-
Upstream and downstream ends of river channels are
Roughness Coefficient
(Manning's n)
catchment
El Herri located outside of the potential flood plain.
Laroussia Dam
The river channel model contains the Mellegue, Bou
LEGEND El Battane
Inflow at upstream Jedeida Heurtma and Tessa rivers which are connected to
boundary Bridge Runoff from Sub-
Lateral Inflow catchment selected seven dams in order to evaluate effects of
Weir Tobias Dam
Result of Reservoir
Operation Analysis
reservoir operation improvement on inundation in
(by MIKE BASIN) Sea Water Level Sea
(Gulf of Tunis)
9 downstream areas. 10
MIKE11 Model Structure MIKE 11 Modelling Procedure

1. Preparing time series file (*.dfs0)
Simulation Data Network Data 2. Preparing network file (*.nwk11)
(**.sim11) (**.nwk11)
3. Preparing cross section file (*.xns11)
Cross Section Data
(**.xns11)
4. Preparing Hydrodynamic file (*.hd11)
Boundary/ Inflow
5. Preparing boundary file (Empty, *.bnd11)
Data
(**.bnd11)
6. Preparing simulation file (*.sim11)
Hydrographs, Water Levels 7. Inputting boundary data (*.bnd11)
(Time seriese data)
(**.dfs0) 8. Test simulation 1 (*.sim11)
Hydraulic (HD) 9. Inputting structure data (*.nwk11)
Parameters
(**.hd11) 10. Test simulation 2 (*.sim11)
Note : (**.sim11) etc. : File extension name
11 12
11. Viewing result file (*.res11, MIKE VIEW)
Lecture_M11-2
MIKE 11 Modelling Procedure Time Series File (**.dfs0)
Prepare River Channel Model Example of Time Series File (inflow, etc.)
To detect errors
Test Simulation 1 in a river channel
model
Input Structure data (weir, etc.)

To confirm MIKE11
model has no error
Test Simulation 2 prior to building
a MIKE FLOOD
model
MIKE FLOOD Modelling
13 Excel 14
Time Series File (**.dfs0) Network File (**.nwk11)

Time Series Data for Mejerda Model Upstream Model
Hourly data are used.
Time series data starts from 1st Jan, 1990 at 7:00
and covers simulation period (18 days). (The
year 1990 has no meaning, but just be same to Ghardimaou
all time series files.)

Reservoir operation and runoff analysis results
(input data for MIKE11) were organized in one
column in Excel so as to correspond to the MIKE
time series file format. 15 16
Network File (**.nwk11) Network File (**.nwk11)

Downstream Model Geographical Coordinate
Opening window of a new nwk11 file
or [Network] [Resize Area...] in an existing file
Extended to
the sea
[Brows...] [D_Carthage]
[ Carthage_UTM_Zone_32N]
(or select UTM_Carthage)

17 18
Lecture_M11-3
Network File (**.nwk11) Cross Section File (**.xns)
As a part of MIKE FLOOD Model Resistance Applied to the Mejerda Model
Coordinate system applied to MIKE 11 Network file
should be consistent with the one in MIKE 21 and
GIS etc.. (be careful with coordinates in
topographic survey results)
Carthage_UTM_Zone_32N
Transversal Mercator
Ellipsoid:Clarke_1880_IGN
Central meridian : 9 o
False easting : 500000
MIKE FLOOD Model = MIKE 11 + MIKE21

Inundation Map = MIKE21 Results + Topo Map 19 20
Cross Section File (**.xns) Cross Section File (**.xns11)

Resistance Applied to the Mejerda Model Mark 1 & 3: MIKE 11 as a part of MIKE FLOOD
Parameter Selection / Value Mark 3
Transversal High/Low flow zones Mark 1 These parts of a cross

distribution section are not used for
simulation.
Resistance Mannings n
Type Mark 4
Left high flow 0.055 Calibration

using H-Q data Mark 5
Right high flow 0.055 at Major

Low flow 0.045 Gauging stations
21 Mark 2 22
(lowest)
Cross Section File (**.xns11) Cross Section File (**.xns11)

Mark 1 & 3: MIKE 11 as a part of MIKE FLOOD Mark 3
Flood plain (grid) 1-D sim.
model by MIKE21 By MIKE 11
River channel model
by MIKE11
Judged by 1-D sim.

Interrelating Mark 1 MIKE FLOOD By MIKE 11
channel and flood plain
by MIKE FLOOD
Water doesn't overflow along Water in the channel
these reaces. overflows along these reaces
Overflow Overflow
Levees
on both banks
confine water.
(Levee : Left and right Flood plain (grid)
ends of cross section model by MIKE21 2-D sim.
marked 1 and 3 in
MIKE11 cross section River channel model by MIKE 21
editor) by MIKE11 23 24
Lecture_M11-4
Cross Section File (**.xns11) Cross Section File (**.xns11)
Mark 1 & 3: MIKE 11 as a part of MIKE FLOOD Mark 1 & 3: MIKE 11 as a part of MIKE FLOOD
In the Mejerda Model, chainages of overflowing Same cross section, but Different positions of
Marks 1 & 3
reaches changes according to the case (present, Overflow Overflow
alternatives of river improvement).
Hence, even at the same cross section, positions of Mark 3
marks 1 and 3 could differ according to the case. Mark 1
Before project : Overflow Mark 3

Mark 1
After project : No overflow (with levees)
Future (after Project) Present (before Project)

with levees no levee
25 26
Boundary File (**.bnd11) Boundary File (**.bnd11)

Upstream Model Downstream Model Outflow from
Inflow at Ghardimaou
Ghardimaou Inflow from Sidi Salem Dam

LEGEND
Inflow to Mellegue Siliana River
Boundary Condition Runoff from Sub-
("Open"in MIKE11) River Slouguia
(Outflow from
Jendouba catchment (HY-U2p11)
Lateral Inflow
Mellegue Dam) Andarrous Bridge Mejez El Bab
("Point Source"
in MIKE11) Mellegue R. Runoff from
Mejerda R
LEGEND Sub-catchment
Result of Reservoir
Boundary Condition Laroussia Dam
Operation Analysis Runoff from Sub-
(by MIKE BASIN) catchment (HY-U2p12) ("Open"in MIKE11)
Tessa R. El Battane Weir
Lateral Inflow
Inflow to Tessa River Jedeida
("Point Source"
(Outflow from in MIKE11) Runoff from
Tessa Dam) Bou Salem Inflow to
Sub-catchment
Bou Heurtma Result of Reservoir Tobias Mob. Dam
Sidi Ismail River Operation Analysis
Sidi Salem Reservoir (by MIKE BASIN)
Water Level 27
Sea Water Level Sea
28
(Gulf of Tunis)
Boundary File (**.bnd11) Boundary File (**.bnd11)

How to Input Boundaries in Network File (1/3) Network File opened through Simulation File
Open Network File (nwk11) through Simulation 3
4
file (sim11) [Insert]
Right click
on where boundary [Boundary]
**.sim11 file
wanted to be added [Hydro Dynamic]
1 Input
2
29 30
Lecture_M11-5
Boundary File (**.bnd11) Network File (**.nwk11) Structures
This page appears. (Bounary File) Structures (Bridges and Weirs)
All river crossing structures (bridge, weir) were
considered. (Cross sectional survey results)
Water surface profiles and flow capacities of all
Boundary Description: structure sites were checked by non-uniform
Open : Up- or donw- ends analysis (by HEC-RAS) before making MIKE11 model.
Point Source : Lateral inflow
Structures showing significant impacts on river flow
were identified and included in the MIKE11 model.
Select Time Series File Add Structure in MIKE 11 Model
Reflect on cross section shapes (e.g. Consider effective
31 32
area)
Network File (**.nwk11) Structures Network File (**.nwk11) Structures

Structures considered in MIKE 11 Model Structures input in MIKE 11 Model (1/2)
Upstream Bridge over Bou Heurtma River near Structure Name Structure Type in MIKE 11
the confluence with the Mejerda
Andalous Bridge Bridge
Downstream Andarrous Bridge at Mejez El Bab
Larrousia Dam
(at Mejez El Bab) (+ Weir and Culvert)
input in MIKE 11
Model as El Battane weir Bridge
Structure El Battan Weir
Tobias Mobile Dam (+ Weir and Culvert)
Considered in cross
Old Bridge at Jedeida
section shape. Can Larrousia Dam Weir
be input as Other weirs crossing riverbed, such
Structure at
detailed design
as a weir at the El Herri pumping
stage. station Tobias Mobile Dam Weir
33 34
Network File (**.nwk11) Structures Network File (**.nwk11) Structure

Structures inputted in MIKE 11 Model (2/2) How to input Structures in Network File (1/3)
Outflow from Open Network File (nwk11) through Simulation
Inflow from Sidi Salem Dam
Siliana River file (sim11)
Slouguia
**.sim11 file
Andarrous Bridge Mejez El Bab
Runoff from Sub-
catchment 1 Input
Laroussia Dam
2
El Battane Weir LEGEND
Inflow at upstream
Jedeida
Bridge boundary
Runoff from Sub- Lateral Inflow
catchment Weir Result of Reservoir
Tobias Mob. Dam Operation Analysis
(by MIKE BASIN)
Sea Water Level Sea 35 36

(Gulf of Tunis)
Lecture_M11-6
Network File (**.nwk11) Structure Network File (**.nwk11) Structures
How to input Structures in Network File (2/3) How to input Structures in Network File (3/3)
4 5
3 This page appears. (Tabular View of Network File)
Right click [Insert]
on a cross section of [Network]
the structure site [Bridges] (or [Weirs])
6 A new structure (e.g.

7
bridge) is added Input required
parameters on this
page
37 38

Structures on Network View Weir
Weir in MIKE11 Mejerda Model (1/2)
Larrousia Dam
Tobias Mobile Dam
Broad Crested Weir

Opening geometry Topographic Survey
Pont Andalous Results (Cross Section)
(Mejez El Bab) Cross section or HxB
Crest elevation
Existing Drawings
El Battane
Simulation Condition : All gates are fully opened

during the major flood.
39 40

Weir
Weir in MIKE11 Mejerda Model (2/2) Bridge
Bridge in MIKE11 Mejerda Model (1/4)
(1/4)
Parameter inputting page (Weir)
Andalous Bridge (Mejez El Bab)
(Tabular View of Network File)
El Battan Weir
Weirs
Arch Bridge with
multiple openings
Input required parameters
on this page
Weir type
Opening geometry (H-Q)
Overflow Weir
etc.........
41
Submergence Culverts 42
Lecture_M11-7
Network File (**.nwk11) Structure Network File (**.nwk11) Structures
Bridge
Bridge in MIKE11 Mejerda Model (2/4) Bridge
Bridge in MIKE11 Mejerda Model (3/4)
Window of Network File Parameter inputting page (Bridge) Pont Andalous
Bridge should be inserted (Tabular View of Network File) Br-MejezPA
Weir at the same position
Culvert (Chainage)
Arch Bridge
Submergence
Submergence Culvert No.1
Overflow Overflow
Weir No.3
43 44
Network File (**.nwk11) Structures Simulation File (**.sim11)

Bridge
Bridge in MIKE11 Mejerda Model (4/4) Simulation Period (1/3)
Parameter inputting page (Weir) (Tabular View)
Input required
Upstream Model : 18 days
parameters for Weir
Simulation Start: 01/01/1990 7:00:00
Weir No.3 Simulation End: 18/01/1990 7:00:00
for Donwstream Model : 18 days
Pont Andalous Simulation Start: 02/01/1990 7:00:00
Simulation End: 19/01/1990 7:00:00
45 46
Simulation File (**.sim11) Simulation File (**.sim11)

Simulation Period (2/3) Simulation Period (3/3)
According to the duration of inflow hydrographs... 1000
Mejerda 10 year 2030 - improved operation
Ghardimaou
Simulation period should cover the duration of a 1day Sidi Salem out CAL
flood peak + D 800 Slouguia CAL
Mejerda basin : One peak of flood could last more

600
than ten days due to natural runoff and an effect of

(m3/s)
dam operation, especially in downstream areas. 400
200
Require simulation period was determined to be long
enough. 0
3/1 4/1 5/1 6/1 7/1 8/1 9/1 10/1 11/1 12/1 13/1 14/1 15/1
47 48
Date
Lecture_M11-8
Initial Condition (
(Steady State
State or Hot Start
Start) (1/4) Initial Condition (
(Steady State
State or Hot Start
Start) (2/4)
Steady State
Starting simulation from the steady condition (Water
depth or discharge specified in HD file)
Hot Start
Starting simulation from the last step of the previous
simulation.
01/Jan. 7:00 09/Jan. 7:00 18/Jan. 7:00
Steady State Simulation 1 Simulation 2
or
Hot Start
Steady State Hot Start
49 50

Initial Condition (
(Steady State
State or Hot Start
Start) (3/4) Initial Condition (
(Steady State
State or Hot Start
Start) (4/4)
01/Jan. 7:00 09/Jan. 7:00 Hot Start is useful As a part of MIKE FLOOD Model
Simulation 1
One simulation of a MIKE FLOOD model often
requires significantly long time (a half day or
Result File 1
09/Jan. 7:00 18/Jan. 7:00 more), because of the MIKE21 simulation.
simulation
Simulation 2 Dividing a simulation into two could give a chance
to check results at the middle of simulation.
Hot Start File Result File
= for entire Hot Start file could save a half of results, even if
Result File 1 simulation period
unexpected termination of the simulation occurs at
Initial Condition = Results after 09/Jan 7:00 are
result at 09/Jan 7:00 added to the result file nearly end of the required simulation period.
51 52
Example of Errors [meter]

Example of Errors
10-1-2003 07:00:00
Simulation Time Step is too Large (1 min.)

205.0
Test simulation 1 : To detect errors in a river 200.0
195.0
channel model before adding structures (e.g. bridge) 190.0
185.0
Inappropriate time step (usually too large) = divergence 180.0

Max. Water Level: Appropriate
175.0 Divergence of time step :
of computation (c.f. Time step for Mejerda Model: 10s) 170.0
computation
10 sec
165.0
Wrong marking (Marks 1, 2, 3, 4 and 5) 160.0
155.0
Wrong Mannings number, etc. 150.0
145.0
Test simulation 2 : To confirm that the MIKE 11 140.0
135.0
model (with structure) has no error prior to building 130.0
125.0
120.0
a MIKE FLOOD model 115.0
110.0
Inappropriate time step : Presence of structures often 105.0 MEJERDA-UP 0 - 89084 MEJERDA-UP MEJERDA-UP 110162 - 152973
0.0 20000.0 40000.0 60000.0 80000.0 100000.0 120000.0 140000.0
necessitates smaller simulation time step, etc. 53 54

[m]
Lecture_M11-9
Example of Errors Example of Errors
[meter] 10-1-2003 07:00:00
Wrong Position of Mark 3 (1/2, Wrong input) Wrong Position of Mark 3 (2/2, Result)
205.0
200.0
195.0
Mark 1
190.0
Effective flow
185.0 area is too small.
180.0
175.0
170.0 Effective flow

Mark 3
(correct)
165.0
160.0
area is too small.
Mark 3
155.0
150.0
Effective flow
(wrong) 145.0 area is too small.
140.0
135.0
130.0
125.0
120.0
115.0
110.0
105.0 MEJERDA-UP 0 - 89084 MEJERDA-UP MEJERDA-UP 110162 - 152973
0.0 20000.0 40000.0 60000.0 80000.0 100000.0 120000.0 140000.0

[m]
55 56
Example of Errors Example of Errors

Wrong Manning
Mannings n (1/2, Wrong input) Wrong Manning
Mannings n (2/2, Result)
[meter] Maximum
205.0
200.0
195.0
190.0
185.0
180.0
175.0
Resistance is too big.
170.0
165.0
160.0
155.0
150.0
145.0
Accidentally, copied CS 140.0
135.0
data in Excel on a 130.0
wrong column 125.0
120.0
115.0
110.0
105.0 MEJERDA-UP 0 - 89084 MEJERDA-UP MEJERDA-UP 110162 - 152973
0.0 20000.0 40000.0 60000.0 80000.0 100000.0 120000.0 140000.0

57 58 [m]
Example of Errors MIKE 11 Model as a part of MIKE

FLOOD Model
Positions of Marks 1 and 3 on a cross section
should carefully be selected.
Evaluation of simulation results are Geographical coordinate system in MIKE 11 model
important!! should be consistent with the ones in MIKE 21 (and
GIS data) files.
Simulation time step and period should be
consistent with the one in MIKE21.
Steady State or Hot Start of simulation should
be selected according to the time required for the
59 simulation of MIKE FLOOD (MIKE 21) Model. 60
Lecture_M11-10
Personal Comments
MIKE FLOOD is applied to the inundation analysis
for the Mejerda River basin, because 2-D analysis
wanted to be employed, especially for Bou Salem
and downstream areas.
However, in many cases, (if inundation areas have
the limited extent) 1-D analysis is already a useful
method to discuss flood conditions.
For 1-D analysis, other software, such as HEC-RAS
(FREE software), could also be a strong tool
instead of MIKE11.
61
Lecture_M11-11
Republic of Tunisia
The Study Training
on
in
Mejerda River for
Training
for
(MIKE 21 Mejerda Model)
June 2008
TOTSUKA Natsuko
Contents of Training Contents of Presentation

Lecture Type
MIKE 21 Mejerda Model
1-1: What is MIKE FLOOD
Overall Structure of the Mejerda Model
2: MIKE11 Mejerda Model Structure of MIKE 21 Mejerda Model
3: MIKE21 Mejerda Model Bathymetry File
4: MIKE FLOOD Mejerda Model Simulation Cold Start or Hot Start
Software practices using simple sample MIKE 21 Model as a part of MIKE FLOOD
models (demo version) Model
Practices how to operate and update the Post Processing MIKE21 Results
Overall Structure of the Mejerda Model Overall Structure of the Mejerda Model
Upstream Model River channel model Ghardimaou
Downstream Model Sidi Salem Dam
by MIKE11
Outflow from
Ghardimaou Flood plain (grid) Sidi Salem DamSiliana Dam Siliana R.
Sidi Salem Dam
Inflow
model by MIKE21 Inflow

Runoff from Sub-
Sidi Salem Dam Jendouba
catchment
Estuary Slouguia
Mellegue R.
Interrelating
Inflow Bridge Mejez El Bab
River channel model
Mellegue Dam
by MIKE FLOOD catchment
by MIKE11 El Herri
Tessa R. Runoff from Sub-
catchment Bou Heurtma Laroussia Dam (Weir)
Inflow Dam
Tessa Dam El Battane Weir
Inflow
Mejerda R
Bou Heurtma R. Interrelating Jedeida

Bou Salem
catchment
by MIKE FLOOD Flood plain (grid)
Sidi Ismail Tobias Dam
Water Level (Weir)
model by MIKE21
Sea Water Level Sea
5 (Gulf of Tunis) 6
Sidi Salem Dam
Lecture_M21-1
Structure of MIKE 21 Mejerda Model Structure of MIKE 21 Mejerda Model
Simulation File [Basic Parameters] [Bathymetry]
Flow Model File Bathymetry File

(Simulation file) (Topography 2-D grid data)
(**.m21) (**.dfs2)
Structure of MIKE 21 Model as a part of Mejerda MIKE FLOOD MODEL

Specify Bathymetry File
7 8
Bathymetry File (Upstream Model) Bathymetry File

Location sample model (mfbig.couple file)
Bou Heurtma
Flood plain (grid)
Dam Sidi Salem
model by MIKE21 Bou Heurtma
Dam

Bou Salem
potential flood plain area Mejerda R.
Sidi Ismail
Tessa R.
River channel
model
Mejerda R.
Ghardimaou
Jendouba MIKE11
e
R
. river channel
gu
M
e lle model
No inundation
MIKE21
(Land value in
MIKE21 bathymetry) flood plain model
Mellegue Dam
Tessa Dam 9 10
Bathymetry File Bathymetry File

Bathymetry for the Mejerda Model was
prepared to cover the maximum limit of
potential inundation area.
Bathymetry (except land value) was
designed to be within the extent of MIKE11
Model
MIKE11 model : One grid = Square
MIKE21 model :
Enclosed (Land value cells). Inflow discharge is supplied from Bathymetry should be a square shape.
NO boundary. MIKE11 Model to the flood plain
11 (including land value) 12
Lecture_M21-2
Bathymetry File Bathymetry File (Upstream Model)
Location
Boundary conditions (inflow discharges and Flood plain (grid) Bou Heurtma
Dam Sidi Salem
model by MIKE21 Bou Heurtma
Dam
downstream water level) of a MIKE FLOOD Assumed Max. limit of
Bou Salem
potential flood plain area
Model area controlled by MIKE11. Mejerda R.
Sidi Ismail
Bathymetry boundaries were designed to be
Tessa R.
River channel
model
closed, in principle. (except downstream end Ghardimaou
Mejerda R.
Jendouba
.
of the downstream model) el
le
gu
e
R
No inundation
(Land value in
Mellegue Dam MIKE21 bathymetry)
13 Tessa Dam 14
Bathymetry File (Upstream Model) Bathymetry File (Upstream Model)

dfs2 File (grid_Jnd-
(grid_Jnd-BS-
BS-LL02rev.dfs2) No Boundary Closed
Closed
No inundation is expected.
Grid Size : 228.13 m x 228.13 m Land value = 500 (NGTm)
15 16
Bathymetry File (Upstream Model) Bathymetry File (Upstream Model)

Closed Boundary MIKE21 Simulation File (**.m21)
(by land value
value 500) [Basic Parameters] [Boundary]
Program detected
Nothing
17 18
Lecture_M21-3
Bathymetry File (Upstream Model) Bathymetry File (Downstream Model)
Setting Land Value Location Assumed Max. limit of
(Gulf of Tunis)
potential flood plain area
Window of dfs2 file [Edit] [Items...]
Sea
Tobias Dam
River channel model

by MIKE11
No inundation
(Land value in Jedeida
MIKE21 bathymetry) Mejerda R.
Larrousia Dam
El Herri
Mejez El Bab Flood plain (grid)

Sidi Salem model by MIKE21
Dam
Slouguia
Siliana R.
19 20
Siliana Dam
Bathymetry File (Downstream Model) Bathymetry File (Downstream Model)

dfs2 File (grid_DeltaEx03.dfs2)
Closed Boundary
(by land value
value
500)
Mean High Sea

Water Level
No inundation is expected. 0.5 mNGT (const.)
Land value = 500 (NGTm)
21 22
Bathymetry File (Downstream Model) Bathymetry File (Downstream Model)

MIKE21 Simulation File (**.m21) MIKE21 Simulation File (**.m21)
[Basic Parameters] [Boundary] [Hydrodynamic Parameters] [Boundary]
Program detected
Constant 0.50
Automatically
filled
23 24
Lecture_M21-4
Bathymetry File (Coordinate System) Bathymetry (Coordinate System)
Coordinate system applied to MIKE 21 should Inundation Depth (Grid data):
Imported MIKE21 Results
be consistent with the one applied in MIKE
11 (and topographic survey) and GIS.
Base Map, Reservoir, River

channel alignment :
GIS data
MIKE FLOOD Model = MIKE 11 + MIKE21
MIKE 21 Bathymetry File = Prepared in GIS
Inundation Map = MIKE21 Results + Topo Map
25 26
Bathymetry File (Coordinate System) Bathymetry File (Grid Size)

Coordinate System Applied to the Mejerda Model Grid Size Applied to the Mejerda Model
Carthage_UTM_Zone_32N (or UTM Carthage)
Upstream Model 228.13 m x 228.13 m
(76.04 m x 76.04 m)
Transversal Mercator
Downstream Model 228.13 m x 228.13 m
Ellipsoid: Clarke_1880_IGN
Central meridian : 9 degree Notes on grid size selection
Elevation in a grid cell represents average elevation.
False easting : 500000 Modify one by one,
Sporadic depressions cannot be expressed. if necessary
Small cell size result in.... (but, often not available....)
This system was applied, because it matches with... Long simulation time, but unnecessarily high resolution.....
the one used in GIS data prepared by MARH, and
Inflow
Size by different
selection reservoir
according to operation
the required accuracy
the one used for the topographic survey
27 (the stage of study) is required. 28
Bathymetry File (Grid Size) Bathymetry File (Grid Size)

Bou Salem: before Project, 10-
10-year flood Bou Salem: before Project, 10-
10-year flood
Grid Size : 228.13 m x 228.13 m Grid Size : 228.13 m x 228.13 m

29 + 76.04 m x 76.04 m 30
Lecture_M21-5
Simulation Cold Start or Hot Start Simulation Cold Start or Hot Start
Initial Condition Cold Start
Start or Hot Start
Start (1/2) Initial Condition Cold Start
Start or Hot Start
Start (2/2)
01/Jan. 7:00 09/Jan. 7:00
Simulation 1 Bathymetry information
01/Jan. 7:00 09/Jan. 7:00 18/Jan. 7:00 + Result at 09/Jan. 7:00
Simulation 1 Simulation 2
Hot Start File
Two result files are
Cold Start Hot Start Result File 1 created.
09/Jan. 7:00 18/Jan. 7:00

Simulation 2
Hot Start File Result File 2

use as
31 Bathymetry File 32
How to Input (1/3) How to Input (2/3)
[Basic Parameters] [Bathymetry]
In MIKE 21, settings require in the windows
Cold Start
of..... or
[Basic Parameters] [Bathymetry] Hot Start
[Hydraulic Parameters] [Result]
Cold Start: Specify bathymetry file

Hot Start : Specify hot start file
33 34
How to Input (2/3) Advantages of Hot Start in MIKE21
[Hydraulic Parameters] [Result] Save a half of results, even if unexpected
termination of the simulation occurs at the
nearly end of the required simulation period
Tick Generate hot start Dividing a simulation could give a chance to
check results at the middle of simulation.
The size of one result file can be limited.
Specify directory and name e.g. Downstream model: Present condition 50-y
of Hot Start file
1 file = could be about 1 GB.
35 36
Lecture_M21-6
Disadvantages of Hot Start in MIKE21 In consideration of post-processing of MIKE21
Results are divided and stored in separate files. result files, one result file for the entire
Additional post-processing procedures (e.g.
simulation period (without Hot Start) is more
combining two files) might be involved.
convenient........
For Mejerda Model, Hot Start was applied only
Note:
for cases with extensive inundation areas
Larger MIKE21 result file size is brought by
More cells with inundation (=significantly long simulation time) ....
Longer simulation period (and smaller time step) Present condition: Upstream. and Downstream,
Larger MIKE21 result file = Longer simulation time
20, 50-year, etc.
37 38
MIKE 21 Model as a part of MIKE MIKE 21 Model as a part of MIKE

FLOOD Model FLOOD Model
Geographical coordinate system in MIKE 21
Bathymetry (except land value) should be
model should be consistent with the ones in
within the extent of MIKE11 Model
MIKE 11 and GIS data files.
Boundaries are suggested to be closed in
Simulation time step and period should be
principle.
consistent with the one in MIKE11.
Boundary conditions (inflow discharges and Cold Start or Hot Start of simulation should
downstream water level) of MIKE FLOOD be selected according to the time required for
Model are basically controlled by 1-D model the simulation.
(MIKE11). (MIKE21=Hot Start MIKE11=Hot Start)
39 40
Post Processing MIKE21 Results Post Processing MIKE21 Results

Concept of dfs2 File Topography grid data Overall Procedure
Bathymetry MIKE21 Result file (**.dfs2)
(Time series grid data)
Grid data
Max. water depth
dfs2 file Grid data Extract max water depth at in each cell
Water depth at Time step n
Time step = n each grid
...
t+1
t
...
MIKE Applications
Simulation result MIKE21 Result file (**.dfs2)
...
2
...
Time step = 1
dfs2 file (Time series grid data)
Grid data Overlay with background images Overlay with other images
Water depth at Time step n (shape file, jpg images, etc.) (e.g. Maps
Time step = n Create video File Arrange presentation
...
t+1 MIKE Applications ArcGIS (with Spatial Analysit)

t
...
...
2
...
Time step = 1
Video Inundation Map
41 42
Lecture_M21-7
Post Processing MIKE21 Results
Inundation Depth (Grid data):
Imported MIKE21 Results
(Extracted max. depth)
Base Map, Reservoir, River

channel alignment :
GIS data
43
Lecture_M21-8
Republic of Tunisia
The Study Training
on
in
Mejerda River for
Training
for
(MIKE FLOOD Mejerda Model)
June 2008
TOTSUKA Natsuko
Contents of Training Contents of Presentation

Lecture Type MIKE FLOOD Mejerda Model
1-1: What is MIKE FLOOD
MIKE FLOOD Model Structure
Overflowing River Reaches
3: MIKE21 Mejerda Model Linking River Reaches to MIKE21
4: MIKE FLOOD Mejerda Model
Software practices using simple sample
models (demo version)
MIKE FLOOD Model Structure MIKE FLOOD Model Structure

Upstream Model Downstream Model
(Gulf of Tunis)
Bou Heurtma
Flood plain (grid) potential flood plain area
Dam Sidi Salem
model by MIKE21
Sea
Bou Heurtma
Dam Tobias Dam
Assumed Max. limit of River channel model

Bou Salem
potential flood plain area Mejerda R. by MIKE11
No inundation
Sidi Ismail
(Land value in MIKE21
Tessa R.
River channel Jedeida
model bathymetry) Mejerda R.

Mejerda R.
Jendouba
Ghardimaou Larrousia Dam
. El Herri
R
e
gu
le
el Mejez El Bab Flood plain (grid)
M
Sidi Salem model by MIKE21
No inundation Dam
(Land value in MIKE21

bathymetry) Slouguia
Mellegue Dam
Siliana R.
Tessa Dam 5 6
Siliana Dam
Lecture_MF-1
MIKE FLOOD Model Structure Overflowing River Reaches
Flood plain (grid)
Input files
model by MIKE21
MIKE11 (e.g. *.nwk11)
Simulation File River channel model
(**.sim11) by MIKE11
......
MIKE FLOOD
Definition File Completed MIKE 11 Model Interrelating
(**.couple) channel and flood plain
by MIKE FLOOD
Input files
MIKE21 (e.g. *.dsf2)
Definition File Overflowing might
This is the only file need for (**.m21) occur here.
......
modelling of the MIKE We expect NO overflowing might
FLOOD part of a inundation
analysis model.
occur here.
River sections are large enough.
Completed MIKE 11 Model
Levees will be installed. etc....
7 8
Overflowing River Reaches Overflowing River Reaches

Flood plain (grid)
model by MIKE21
MIKE FLOOD **.couple File, [Definition] page
River channel model Chainage of Linked river reaches
by MIKE11
(Chainage : in MIKE11)
Interrelating
by MIKE FLOOD
Green : Linked river reaches
Water doesn't overflow Water in the channel overflows
along these reaces. along these reaces (Linked river reaches = Overflow
(1-D simulation only) (1-D & 2-D simulation) might occur)
Overflow Overflow
Virtual levees
on both banks
confine water.
ends of cross section model by MIKE21
marked 1 and 3 in
River channel model
MIKE11 cross section
editor) by MIKE11 MIKE21 model : MIKE11 model :
Example : Example : Grid topography data Inflow discharge is supplied from
River reaches River reaches
with embankment without embankment 9
of flood plain MIKE11 Model to the flood plain10

Upstream Model: Present Condition Upstream Model: After Project (River Improvement)
(example of one of alternatives)
(Linked river reaches = Green : Linked river reaches
Overflow might occur, (Linked river reaches =
or might not occur) Overflow might occur,
or might not occur)
Levees are planned:
No overflowing
11 12
Lecture_MF-2
Downstream Model: Present Condition Downstream Model: After Project (River Improvement)
(example of one of alternatives)
(Linked river reaches = Green : Linked river reaches
Overflow might occur, (Linked river reaches =
or might not occur) Overflow might occur,
or might not occur)
Levees are planned:

No overflowing
13 14
Linking River Reaches to MIKE21 Linking River Reaches to MIKE21

How to Input / Change Linked Chainages (1/2) How to Input / Change Linked Chainages (2/2)
1
2
Check Lateral link
River name: Select [Left] (or [Right])
Type river name to be linked to
2-D model
1
Right click on this
3
window Chainage upstream:
Chainage downstream:
2 Link river branch to
MIKE21.... Upstream and downstream ends of
overflowing reaches. (Chainages are
15 defined in MIKE 11) 16

Link and Land Value How to Determine Chainage
Chainage to be linked (1/3)
Chainage : from MIKE11
Up- and down- ends of linking

chainage should be within the
bathymetry + should not be on
land value cells.
MIKE21 grid cells linked to MIKE11 cross
sections
Chainages should be
determined carefully.
Error: Cells with the land value are linked
17 But, how..... 18
Lecture_MF-3
How to Determine Chainage
Chainage to be linked (2/3) How to Determine Chainage
Chainage to be linked (3/3)
MIKE11 Network view
Chainages need to be
found manually...
Click
comparing...... Chainage
MIKE FLOOD window

MIKE11 network view
19 20
Closing
Building model involves engineering judgement and
a lot of data processing routine work. (Modelling
cannot be all automatic!!)
Evaluating simulation results is important.
Finding mistakes
Evaluating calibration results (parameter values)
Judging settings in the model. (based on results)
Modelling always involves assumptions and
simplification.
There might be limitation of software functions
Required accuracy according to the purpose. 21
Lecture_MF-4
Republic of Tunisia
Todays Training Item
The Study Lecture Type
on
Focused on Flood Control 1-1: What is MIKE FLOOD
in
Mejerda River 1-2: Overview of Mejerda Model
Training
on 3: MIKE21 Mejerda Model
Inundation Analysis Model
for 4: MIKE FLOOD Part of Mejerda Model
Software practices using a simple sample
June 2008 model MIKE11 : Software for 1-D
Nippon Koei Co., Ltd. Hydraulic Analysis (like HEC-RAS)
Practices how to use and update Mejerda
TOTSUKA Natsuko inundation analysis model 2
Overall view of MIKE11 Model Outcome of MIKE 11 Simulation

Model Example OUTPUT
Sidi Salem Dam
Water level
Outflow from
Discharge
Siliana Dam Siliana R.
Sidi Salem Dam
Inflow
... etc.
Slouguia
Bridge Mejez El Bab

Runoff from Sub-
Roughness Coefficient (Manning's n) catchment
El Herri
Laroussia Dam (Weir)
INPUT LEGEND El Battane Weir
Inflow
boundary Discharge
Inflow at upstream Jedeida
Runoff from Sub-
Cross section
Lateral Inflow catchment
Tobias Dam
(Weir)
... etc.
Sea Water Level Sea
(Gulf of Tunis) 3 4
Structure of MIKE 11 Model Structure of MIKE 11 Model

Simulation (**.sim11) File
(**.sim11) (**.nwk11)
Cross Section Data

sim11 file
(**.xns11)
interrelates other
input files. Boundary/ Inflow
Data
(**.bnd11)
Hydrographs, Water Levels Input files can be opened

(Time seriese data) from **.sim11 file
(**.dfs0)
Hydraulic (HD)
Lets try opening....
Parameters
(**.hd11) Example M11_Mejerda_byJICATeam
Note : (**.sim11) etc. : File extension name 5 Sim_MejUp_demo.sim11 6
Tutorial_M11-1
Major Input Data to MIKE 11 Major Input Data to MIKE 11
Cross Section File (*.xns11)
Simulation File (*.sim11)
Cross section ID No.
Model definition (Hydrodynamic, unsteady)
Location (chainage) of cross sections
Names and directories of input files (Network, Cross
Cross section shape (X, Y)
section, Boundary, etc.) and a result file
Bed resistance (resistance type, roughness coefficient)
Simulation time step and period
Boundary file (*.bnd11)
Network File (*.nwk11)
(Location of boundary conditions) (This can be input on
Coordinates of cross section positions (Easting, Northing)
the Network editor.)
Chainage (distance for the upstream end) of cross
Names (and directories) of inflow/water level time
sections
series data files (**.dfs0)
Structures (e.g. bridge) (Type, location, dimension)
Location of boundary conditions (inflow, etc.) Hydraulic parameter file (*.hd11)
7 Initial condition (water level or discharge) 8
MIKE 11 Modelling Procedure

Procedure of Modelling
1. Preparing time series file (*.dfs0)
2. Preparing network file (*.nwk11)
3. Preparing cross section file (*.xns11)
4. Preparing Hydrodynamic file (*.hd11)
5. Preparing boundary file (Empty, *.bnd11)
6. Preparing simulation file (*.sim11)
7. Inputting boundary data (*.bnd11)
8. Simulation (*.sim11)
9. Viewing result file (*.res11) 9
Tutorial_M11-2
Republic of Tunisia
on
in
Training
Nippon Koei Co., Ltd. Hydraulic Analysis
Outcome of MIKE 21 Simulation Topography data for 2-D Analysis

For MIKE21, 2-D (grid) topography data should
be prepared.
(Elevation in m) GIS Software
5 5 4 6 6 7 7 5 or
6 4 5 5 4 4 4 3 MIKE application
6 4 5 5 4 4 4 3 Digitized
6 4 6 6 5 4 5 4 contour lines
6 5 7 6 4 5 5 4
or
6 7 6 6 4 4 4 7
5 7 5 5 5 6 9 16 or
5 7 5 5 5 6 9 22 Existing grid data
2-D (grid) topography data

(called Bathymetry in MIKE21)
Point Elevation Data
3 For MIKE 21 : One Grid = Perfect square 44
Concept of 2-D Analysis Result Outcome of MIKE 21 Simulation

Example of Result
Results are Simulation by MIKE 21
and
also grid data.
Post-processing by
1.2 1.2 2.2 0.2 0.2 0 0 1.2
MIKE Software, GIS etc.
0.2 2.2 1.2 1.2 2.2 2.2 2.2 3.2
0.2 2.2 1.2 1.2 2.2 2.2 2.2 3.2
0.2 2.2 0.2 0.2 1.2 2.2 1.2 2.2
0.2 1.2 0 0.2 2.2 1.2 1.2 2.2
0.2 0 0.2 0.2 2.2 2.2 2.2 0
1.2 0 1.2 1.2 1.2 0.2 0 0
1.2 0 1.2 1.2 1.2 0.2 0 0
Max. Water Depth (m)

(Inundation Depth)
5 6
Tutorial_M21a-1
Some Notes Structure of MIKE 21 Model
MIKE 21 (2-D analysis) is often used for Flow Model File

Bathymetry File
(Topography 2-D grid data)
(Simulation file)
simulation of coastal areas (current in a bay, (**.m21)
(**.dfs2)
Boundary Data File (e.g. Water Level)

etc.) (Time series data)
(**.dfs0, **.dfs1)
MIKE 21 (2-D analysis) can be also applied to
Typical Structure of MIKE 21 Model
the simulation of inundation on a flood plain.
This is not always necessary. (The Mejerda Model
does not require this.)
For example...
If a boundary water level is constant, the boundary condition
can be defined in the Simulation file (*.m21) without time
7 series files. 8
Major Input Data to MIKE 21 Structure of MIKE 21 Model

Sample 1: Lake (provided by DHI)
Bathymetry file (*.dfs2)
lake.m21 ---- Flow model file (simulation file)
Grid data (Topography of flood plain, sea bottom, etc.)
bathy.dfs2 ---- Bathymetry file (2-D grid data)
Flow model file (Simulation file) (*.m21)
Name of bathymetry file Sample 2: Sound (provided by DHI)
Simulation time step, simulation period Sound_HD.m21 (in HD folder) ---- Flow model file
Resistance (Manning number, etc.) (simulation file)
Boundary condition (constant values or time series file) Bathy900.dfs2 (in Data folder) ---- Bathymetry file
Result file name
(2-D grid data)
Other parameters (wind, etc.)
wln.dfs1 (in Data folder) ---- Boundary time series
Boundary time series file (if necessary)
wls.dfs1 (in Data folder) ---- Boundary time series
9 10
Sample 1: Lake Sample 1: Lake

Continued...
Let
Lets see the model structure !
[Hydraulic Parameters] [Initial surface elevation]
Open lake.m21 (double click)
[Hydraulic Parameters] [Boundary]
[Basic Parameters] [Bathymetry] [View]
In Lake, [constant] is selected.
bathy.dfs2 file opens
[Hydraulic Parameters] [Resistance]
This is a simple example of bathymetry (grid) data.
In Lake, [constant] is selected.
Close bathy.dfs2
[Hydraulic Parameters] [Results]
[Basic Parameters] [Simulation Period]
Click a small squire on right of Time.
A time step is normally small. (20 second for Lake)
Click Ctrl + D on Data File
[Basic Parameters] [Boundary]
[Program detected] is normally recommended.
Continue Continue
11 12
Tutorial_M21a-2
Sample 1: Lake Concept of dfs2 files
Continued...
Bathymetry Topography grid data
[Run] [Start Simulation.....] [OK]
dfs2 file
Open lakeres.dfs2 file created (Result file)

Click Timestep forward and Timestep back icons
(symbol look like clocks) on Tool bar dfs2 file (Time series grid data)
Slide a bar at the bottom of the table view Grid data
Mesh on the grid moves simultaneously Water depth at Time step n
Time step = n
Select one of cells in the table view, and input 5
...

t+1
t
Close lakeres.dfs2 (Dont save your changes)
...

...
2
...
Time step = 1
13 14
MIKE 21 Modelling Procedure Sample 2: Sound

5 1. Develop Bathymetry File (grid data) (*.dfs2) This example is simulation of coastal area.
1 2. Make Flow Model File (simulation file) Water level time series
recording point Water level time
(*.m21) series profiles at
are known.
2 3. Input parameters
2-D Simulation
3 4. Simulation Obtain
4 5. Viewing results water level time

series
Order of modelling Modelling Area Flow direction
Order of at other points

todays practice 15 16
Source : Adapted from DHI manual, M21 step-by step
Sample 2: Sound Bathymetry File Sample 2: Make Flow Model File (*.m21)
and Input Parameters
Start MIKE21 [MIKE 21] [Flow Model (.m21)]
Save *.m21 file
Go to page 23 of DHI Manual

(MIKE 21 step-
step-by-
by-step)
17 18
Tutorial_M21a-3
Sample 2: Viewing Results Sample 2: Develop Bathymetry File
Directly open *.dfs2 file Start MIKE21 [MIKE ZERO] [Bathymetries]
Prot Composer
Start MIKE 21 New icon [MIKE ZERO] [Prot
Composer] UTM-33
[Plot] [Insert New Plot Object] [Grid Plot] select E: 290000
the result dfs2 file at Master File N: 6120000
Result Viewer W: 120000
Start MIKE 21 New icon [MIKE ZERO] [Result H: 120000
Viewer]
[Projects] [Add Files to Project] at File Type select
MIKE21 Result File Click ... , select result dfs2 file
19 [OK] Save **.batsf File 20
Tutorial: Develop Bathymetry File Tutorial: Develop Bathymetry File

[Work Area] [Background Management] [Import] [Import] - Select soundbathywater.xyz
[Files of Type : MIKE21 XYZ Files (*.xyz)] [Convert from : LONG/LAT] [Open]
Select soundbathyland.xyz [OK]
Fig 2.7 in DHI Manual (MIKE21 Step-by-step)
This is an ASCII (text) file of

digitized shore line.
21 22
Tutorial: Develop Bathymetry File

Procedure of Modelling
[Work Area] [Bathymetry Management] [New]

[Convert from : LONG/LAT] [Open]
[OK]
Fig 2.7 in DHI Manual (MIKE21 Step-by-step)
Go to page 6 of DHI Manual

(MIKE 21 step-
step-by-
by-step)
23
Tutorial_M21a-4
Republic of Tunisia
on
in
Training
Nippon Koei Co., Ltd. Hydraulic Analysis
Sample 1: Lake
Sample 1: Lake
Continue
3 4
Automatically
5 6
Tutorial_M21b-1
Time Step
(sec)
Automatically
7 8
Constant
9 10
11 12
Tutorial_M21b-2
Automatically
13 14
Sample 1: Lake
15
Tutorial_M21b-3
Republic of Tunisia
on
in
Training
June 2008 model MIKE FLOOD : Software for
Nippon Koei Co., Ltd. combining 1-D and 2-D Models
MIKE 11, MIKE 21 and MIKE FLOOD Structure of MIKE FLOOD Model
Functions and Relations Completed Input files
MIKE 11 Model MIKE11 (e.g. *.nwk11)
MIKE21 MIKE FLOOD MIKE11
Simulation File
2-D Analysis Combining 1-D and 2-D 1-D Analysis
(**.sim11)
......
Simulating hyraulic Simulating hyraulic
Interrelating 1-D and 2-D
conditions conditions
models
(water depth, velocity,
Defining overflows along
(water depth, velocity, MIKE FLOOD
etc.) etc.)
on flood plain
interrelated reaches
in river channels Definition File
(**.couple)
Input files
MIKE21 (e.g. *.dsf2)
Definition File
This is the only file need for
(**.m21)
......
modelling of the MIKE
Flood plain defined FLOOD part of a inundation
by MIKE21 Lateral Link defined analysis model.
by MIKE FLOOD
River channel defined
by MIKE11 Completed MIKE 21 Model
3 4
Structure of MIKE FLOOD Model Structure of MIKE FLOOD Model

Note : Sample model
Sample programme used in this session
MIKE 11 (1-D) and MIKE 21 (2-D) models
mfbig.couple in FloodplainDemonstration
have to be completed before building a MIKE
provided by DHI
FLOOD Model.
Test run / MIKE 11 and MIKE 21 models
MIKE 11 model files are in river folder
independently
MIKE 21 model files are in floodplain
Confirm MIKE 11 and MIKE 21 models have no
error. folder
5 6
Tutorial_MF-1
Structure of MIKE FLOOD Model Major Input Data to MIKE FLOOD
Let
Lets see the sample model (mfbig.couple file)
Name of MIKE 11 simulation file (*.sim11)
MIKE11 (**.sim11) and Name of MIKE 21 simulation file (*.m21)
MIKE21 (**.m21) files can be Chainage of river reaches overflow occurs
opened from hear.
Definition of overflowing
MIKE11
river channel model
MIKE21
flood plain model
7 8
Meanings of Overflowing Meanings of Overflowing

Flood plain (grid)
model by MIKE21
Chainage of Linked river reaches River channel model
(Chainage : in MIKE11) by MIKE11
Interrelating
Green : Linked river reaches channel and flood plain
(Linked river reaches = Overflow by MIKE FLOOD
might occur)
Overflowing might
We expect NO overflowing might occur here.
occur here.
River sections are large enough.
Levees will be installed. etc....
9 10
Meanings of Overflowing MIKE 21 Model in MIKE FLOOD Model

Flood plain (grid)
model by MIKE21
sample model (mfbig.couple file)
River channel model
by MIKE11
Interrelating
by MIKE FLOOD
Water doesn't overflow Water in the channel overflows
along these reaces. along these reaces
(1-D simulation only) (1-D & 2-D simulation) MIKE11
Overflow Overflow
Virtual levees river channel model
on both banks
confine water.
ends of cross section model by MIKE21
marked 1 and 3 in
River channel model
MIKE11 cross section
by MIKE11
MIKE21
editor)
Example : Example : flood plain model
River reaches River reaches
with embankment without embankment 11 12
Tutorial_MF-2
MIKE 21 Model in MIKE FLOOD Model Procedure of MIKE FLOOD Modelling
1 Create a new **.couple" file
Combine MIKE11 (1-D) and MIKE21 (2-D) Models

Specify prepared
2 MIKE11 simulation file (**.sim11) and
MIKE21 definition file (**.m21)
Define overflowing reaches (where 1-D and

3
2-D models are interrelated.)
MIKE21 model : MIKE11 model : 4 Final check of MIKE11 and MIKE21 Models
Enclosed (Land value cells). Inflow discharge is supplied from
NO boundary. MIKE11 Model to the flood plain 5 Simulation
13 14
Major Items of Final Check Practice on Sample Model

MIKE 11 and MIKE 21
Make a mf-
mf-practice.couple
practice.couple file
[Program]
Simulation time step and simulation period -[MIKE BY DHI]
should be consistent in the two models. -[MIKE FLOOD]
-[MIKE FLOOD]
Directory and name of result file is defined
correctly.
MIKE 21
Ranges of time and grid for storing result Save as ....
mf-practice.couple
should cover required time and area.
15
in your practice folder 16
Practice on Sample Model Practice on Sample Model

1 3
2
Select MIKE11 and MIKE21

simulation files in your practice
folder 1
Right click on this
window of grid and
river reaches

MIKE21....
17 18
Tutorial_MF-3
Practice on Sample Model Practice on Sample Model
Definition
Definition page
1
2
Check Lateral link Right
River name: trib
Select [Left] (or [Right]) Left 3000.000
3000.000
2-D model (With typing first one Right
or two letters, the selection tab Left
of river names appears.)
3
Lateral Link Options
Options page
Chainage upstream: 1350
Chainage downstream: 1885 trib
DEM_1m
1350
1885
Upstream and downstream ends of

defined in MIKE 11) 19 Save (Close Open ) Simulation (Key) 20
Lateral Link and MIKE11 Markers Lateral Link and MIKE11 Markers
MIKE 11 : Mark 3 Right in
Mark 3
Cross section editor MIKE
Left in
These parts of a cross
Mark 1 These parts of a cross FLOOD
MIKE
Mark 1
simulation.
simulation.
lateral link
FLOOD
lateral link
Mark 4
Mark 4
Mark 5 Mark 5
Mark 2 21 Mark 2 22
(lowest) (lowest)
Lateral Link and MIKE11 Markers Lateral Link and MIKE11 Markers
Functions and Relations Mark 3
1-D sim.
By MIKE 11
Judged by 1-D sim.

Mark 1 MIKE FLOOD By MIKE 11
Left and right of river channel =

2-D sim.
Come from Marks 1 and 3 in MIKE 11 by MIKE 21
23 24
Tutorial_MF-4
Republic of Tunisia
Contents of Training
The Study
on
Lecture Type
in
Mejerda River 1-2: Overview of the Mejerda Model
Training
Inundation Analysis Model (MIKE FLOOD) 4: MIKE FLOOD Mejerda Model
for
the Mejerda River Basin Software practices using simple sample
June 2008 models (demo version) MIKE11
TOTSUKA Natsuko Mejerda inundation analysis model 2
Practice Items : MIKE 11 Mejerda Model MIKE 11 Mejerda Model : Practice D1

Down stream Model D1. Add Tobias Weir and Andalous Bridge
D1 : Add Tobias Weir and Andalous Bridge (Downstream Model)
Upstream Model Simulation Data Network Data
(**.sim11) (**.nwk11)
U1 : Input boundary condition
Cross Section Data

U2 : Input Marks 4 and 5 (**.xns11)
U3 : Change Mannings n (all Cross sections) Boundary/ Inflow

Data
U4 : Make a new model for different inflow (**.bnd11)

U5 : Change cross section shape (Time seriese data)
(**.dfs0)
U6 : Add Bou Heurtma River (Cross section file) Hydraulic (HD)

Parameters
U7 : Add Bou Heurtma River (Network file) (**.hd11)
3 Note : (**.sim11) etc. : File extension name 4
MIKE 11 Mejerda Model : Practice D1 MIKE 11 Mejerda Model : Practice D1

D1. Add Tobias Weir and Andalous Bridge D1. Add Tobias Weir and Andalous Bridge
(Downstream Model) (Downstream Model)
prac_Dn_OptOpe2030_D2t_010LL.sim11 Right click on a cross section of
the structure site
Network File (**.nwk11) [Insert] [Network] [Brides]
(or [Weirs] [Culverts])
z Open network file through simulation file
MejDn_st-exs_woPAandTobi.nwk11
z Add Tobias Weir (Weir)
Chainage : 137753.2
z Add Andalous Bridge (Bridge, Weir, Culvert)
Chainage : 41044.52
5 6
Practice_M11-1
(Downstream Model) Tobias Weir (Downstream Model) Pont Andalous
WR-Tobias Br-MejezPA
Arch Bridge
Structures - Submergence Culvert No. & Weir

Overflow No. in Culvert & Weir
Weirs
pages
Structures -
7
Bridges 8

(Downstream Model) Pont Andalous (Downstream Model) Pont Andalous
[Geometry and Loss factors]-[Edit] Br-MejezPA Br-MejezPA
Parameters Values
Opening width, b 9
Number of arches 5
Level for bottom of arch curvature 48.5 Structures -

Weirs
Level for top of each curvature 53 Culvert No. for Br-
MehezPA : To be input
Radius of arch curvature, r 4.5
9
on Bridge page 10
MIKE 11 Mejerda Model : Practice D1 MIKE 11 Mejerda Model : Practice U1

D1. Add Tobias Weir and Andalous Bridge U1. Input boundary condition (Upstream Model)
(Downstream Model) Pont Andalous
Br-MejezPA
(**.sim11) (**.nwk11)
Cross Section Data

(**.xns11)
Boundary/ Inflow
Data
Structures - (**.bnd11)
Culverts Hydrographs, Water Levels

(Time seriese data)
(**.dfs0)
Weir No. for Br- Hydraulic (HD)
MehezPA : To be input Parameters
(**.hd11)
on Bridge page 11 Note : (**.sim11) etc. : File extension name 12
Practice_M11-2
MIKE 11 Mejerda Model : Practice U1 MIKE 11 Mejerda Model : Practice U1
U1. Input boundary condition (Upstream Model) U1. Input boundary condition (Upstream Model)
Prac_Up_StOpeU2_010.sim11 Prac_Up_StOpeU2_010.sim11
Network File (*.nwk11) and Boundary file (*.bnd11) z Input upstream boundaries (Open) : inflow
Inflow discharge : Standard operation, 10-year Mejerda (Ghardimaou), Mellegue, Bou Heurtma, Tessa
z Make empty boundary file z Input downstream boundary (Open) : water level
Prac_Up_StOpeU2_010.bnd11 Sidi Salem Water Level
z Specify boundary file in simulation file z Input lateral inflow (Point Source) : inflow
z Open Network file through the simulation file Conf. with Mellegue (U2p11), Conf. with BH (U2p12)
13 14
MIKEBoundary
11 MejerdaFile
Model : Practice U1
(**.bnd11) MIKE 11 Mejerda Model : Practice U1
U1. Input boundary condition (Upstream Model) 1. Input boundary condition (Upstream Model)
Inflow at Ghardimaou
LEGEND Ghardimaou
Boundary Condition Inflow to Mellegue
River Runoff from Sub-
("Open"in MIKE11)
Lateral Inflow
(Outflow from
Jendouba catchment (HY-U2p11) Network Editor
("Point Source" Mellegue Dam)
in MIKE11) Mellegue R. Right click on targeted
Mejerda R
Result of Reservoir positions

Operation Analysis Runoff from Sub- [Insert] [Boundary]
(by MIKE BASIN) catchment (HY-U2p12)
Tessa R. [Hydro Dynamic]
Inflow to Tessa River 1
(Outflow from
Tessa Dam) Bou Salem Inflow to
Bou Heurtma
Sidi Ismail River
15 16
Water Level

1. Input boundary condition (Upstream Model) 1. Input boundary condition (Upstream Model)
This line automatically is Boundary Editor
added in bnd11 file
4
Open targeted folder
5
Open : for up- or 2 Automatically
Click targeted time series
downstream end) Select Inflow filled
file
Point Source : for (for discharge)
lateral inflow
3 Select Item
6
7
17 Repeat (1)-
(1)-(7) for all boundaries 18
Practice_M11-3
1. Input boundary condition (Upstream Model) 1. Input boundary condition (Upstream Model)
Up-
Up- & Down-
Down- ends : Open
Open Up-
Up- & Down-
Down- ends : Point Source
Source
Location Chainage Folder File Name+ Item
Name Location Chainage Folder File Name Item
Upstream end 0 TS- Qin-BPAU1 10-y
Name
(Ghardimaou) QDesign _Ghardi.dfs0 Mejerda & Mellegue 88834.33 TS-QDesign Qd- 10-y
Downstream end 152972.97 TS- SSWLd-D2t- 10-y Confluence, U2tp11.dfs0
(Upstream end of Sidi DamWL 4damStOpe- Mejerda & B.Heurtma 110641.48 TS-QDesign Qd- 10-y
Salem Reservoir) Design MIKEBasin.dfs0 Confluence U2tp12.dfs0
Upstream end of 0 TS-QDesign Qd-D2t-4damStOpe MelDam
Mellegue River _10y.dfs0 _out
Upstream end of Bou 0 TS-QDesign Qdb-D2t-4damStOpe 10-y
Heurtma River _BouHeurtma.dfs0
Upstream end of 0 TS-QDesign Qdb-D2t-4damStOpe 10-y

Tessa River _Tessa.dfs0
19 20

1. Input boundary condition (Upstream Model) U2. Input Marks 4 and 5 (Upstream Model)

Network Editor (after (**.sim11) (**.nwk11)
inserting all boundaries) Cross Section Data

(**.xns11)
Boundary/ Inflow
Data
(**.bnd11)

(Time seriese data)
(**.dfs0)
Hydraulic (HD)
Parameters
(**.hd11)

U2. Input Marks 4 and 5 (Upstream Model) U3. Change Manning
Mannings n (all Cross sections)
(Upstream Model)
Prac_Up_StOpeU2_010.sim11
(**.sim11) (**.nwk11)
Cross section File (**.xns11)
MEJERDA-up : UP-200 ~ UP-213 Cross Section Data
(**.xns11)

z After inputting, compute section parameters, Boundary/ Inflow

Data
[Cross Sections ] [Apply to all Sections] (**.bnd11)

Re-compute All (Time seriese data)
(**.dfs0)
Hydraulic (HD)
Parameters
(**.hd11)
Practice_M11-4
U3. Change Manning
Mannings n (all Cross sections) U3. Change Manning
Mannings n (all Cross sections)
(Upstream Model) (Upstream Model) [Cross Sections ]
Prac_Up_StOpeU2_010.sim11 [Apply to all Sections]
Cross section File (**.xns11)
z 0.05, 0.04 0.055, 0.045
[Cross Sections ] [Apply to all Sections]
[Raw data-Resistance]
High/Low flow zones
Mannings n
0.055, 0.055, 0.045 25 26

U4. Make a new model for different inflow U4. Make a new model for different inflow
(Upstream Model) (Upstream Model)
Boundary : Cross sec.:
(**.sim11) (**.nwk11) Change No Change
Flood Control Reservoir River Channel
Cross Section Data
Option
(**.xns11) Operation
Boundary/ Inflow Present Present Present
Data
(**.bnd11) (Standard Operation)
Hydrographs, Water Levels Reservoir Improved Present
(Time seriese data)
(**.dfs0)
Operation (Optimized, 2030)
Hydraulic (HD) Reservoir Improved After Project
Parameters
(**.hd11) Operation + River (Optimized, 2030)
Note : (**.sim11) etc. : File extension name 27 Improvement 28

(Upstream Model) Inflow at Ghardimaou (Upstream Model)
Ghardimaou
Inflow to Mellegue
River Runoff from Sub-
(Outflow from
Jendouba catchment (HY-U2p11)
Mellegue Dam)
Mellegue R.
LEGEND
Mejerda R
Boundary Condition
("Open"in MIKE11)
Runoff from Sub- Runoff from Remaining
Tessa R. catchment (HY-U2p12) Subcatchments
Lateral Inflow
Runoff from Dam Natural Runoff
("Point Source" Inflow to Tessa River
in MIKE11) Catchments No change after
(Outflow from
Inflow to Regulated by dams
Result of Reservoir Tessa Dam) Bou Salem
improving dam
Bou Heurtma (Reservoir Operation
Operation Analysis
Sidi Ismail River operation
(by MIKE BASIN) Analysis by MIKE BASIN)
Water Level 29 30
Practice_M11-5
Original : Prac_Up_StOpeU2_010.sim11 New : Prac_Up_OptOpeU2_010.sim11
New : Prac_Up_OptOpeU2_010.sim11 z Open new Simulation file
z Specify new boundary file in Simulation. file
Network File (**.nwk11) and Boundary file (**.bnd11)
Prac_Up_OptOpeU2_010.bnd11
Change inflow, No change in cross section
z Open new boundary file through Simulation File (**.bnd11)
Inflow : Standard dam operation 10-year
z Change time series data (upstream inflow and water level)
Optimized dam operation (2030) 10-year
Standard dam operation 10-year
z Copy and Change file names StOpe (copy a folder)
Optimized dam operation (2030) 10-year
simulation file (Prac_Up_OptOpeU2_010.sim11)
z Save Boundary File
boundary file (Prac_Up_OptOpeU2_010.bnd11) 31 32

U5. Change cross section shape U5. Change cross section shape
Simulation Data Network Data Copy from CS2007_MejUp.xns11
(**.sim11) (**.nwk11)
Cross section file (**.xns11)

Cross Section Data

(**.xns11) z Copy and Change file names
Boundary/ Inflow
Data
Original : CS2007_MejUp.xns11
(**.bnd11)
Copied : CS2007_MejUp-practice.xns11
(Time seriese data)
(**.dfs0)
z Change cross section shapes
Hydraulic (HD)
Parameters
(**.hd11)
Note : (**.sim11) etc. : File extension name 33 34

U6. Add Bou Heurtma River (Cross section file) U6. Add Bou Heurtma River (Cross section file)
Simulation Data
(**.sim11)
Network Data
(**.nwk11)
CS2007_MejUp-
CS2007_MejUp-woBH.xns11
Cross Section Data

CS2007_Bouheurtma.xns11

(**.xns11)
Boundary/ Inflow
Cross section file (**.xns11)
Data
(**.bnd11) z Export Bou Heurtma cross section data to text file
(Time seriese data)
CS2007_Bouheurtma.xns11
(**.dfs0)
[File] [Export All Sections] [Export raw data]
Hydraulic (HD)
Parameters
(**.hd11) Save text file (folder 00Excel_txt File BouH.txt)
Practice_M11-6
U6. Add Bou Heurtma River (Cross section file) U7. Add Bou Heurtma River (Network file)
CS2007_MejUp-
CS2007_MejUp-woBH.xns11 Mejerda_up_woBH.nwk11
CS2007_Bouheurtma.xns11 BHeurtma.nwk11
z Import Bou Heurtma cross section data in to Network file (**.nwk11)

CS2007_MejUp-woBH.xns11 z Copy Bou Heurtma cross section data in excel file
[File] [Import raw data] BHeurtma.nwk11
Select text file of Bou Heurtma cross sections [View] [Tabular View]
(folder 00Excel_txt File BouH.txt) [Network] [Points]
37 Select X-coord. to Chainage, then Copy 38

U7. Add Bou Heurtma River (Network file) U7. Add Bou Heurtma River (Network file)
Simulation Data Network Data Mejerda_up_woBH.nwk11
(**.sim11) (**.nwk11)
BHeurtma.nwk11
Cross Section Data

(**.xns11)
z Paste data on excel file
Boundary/ Inflow
Data
z Delete the column of Chainage type
(**.bnd11)

z Select columns in Excel
(Time seriese data)
(**.dfs0) z Past on a new Note Pad file
Hydraulic (HD)
Parameters
z Save Note Pad file prac_bh.txt
(**.hd11)
MIKE 11 Mejerda Model : Practice U7

U7. Add Bou Heurtma River (Network file)
(Upstream Model)
Mejerda_up_woBH.nwk11
BHeurtma.nwk11
z Import text file
Mejerda_up_woBH.nwk11
[File] [Import] [Point and Branch Data from
Point-Branch ASCII File...]
[View] [Tabular View...] [Topo ID] 2007_2
41
Practice_M11-7
Republic of Tunisia
The Study
on
Lecture Type
in
Training
for
June 2008 models (demo version) MIKE21
Practice Items : MIKE 21 Mejerda Model Practice Items : MIKE 21 Mejerda Model
U1 : Open and close boundaries (Change D1 : Make a MIKE 21 Model (Cold Start)
elevation data in some cells) D2 : Post Processing : Overlay result dfs2 file
U2 : Make a MIKE 21 Model (Cold Start) and GIS shp file
U3 : Make a MIKE 21 Model (Hot Start) D3 : Post Processing : Make video file
D4 : Post Processing : Extract maximum
inundation depth in cells
3 4

U1. Open and close boundaries (Change U1. Open and close boundaries (Change
elevation data in some cells) (Upstream Model) elevation data in some cells) (Upstream Model)
grid-
grid-Up-
Up-practice.dfs2 grid-
grid-Up-
Up-practice.dfs2
z Open boundary
500 200 (mNGT)
z Close boundary
200 500
z Check land value
[Edit] [Items...]
5 6
Practice_M21-1
U1. Open and close boundaries (Change U2. Make a MIKE 21 Model (Upstream Model)
elevation data in some cells) (Upstream Model)
Window of dfs2 file [Edit] [Items...]
Flow Model File Bathymetry File

(Simulation file) (Topography 2-D grid data)
(**.m21) (**.dfs2)
Structure of MIKE 21 Model as a part of Mejerda MIKE FLOOD MODEL
7 8

U2. Make a MIKE 21 Model (Cold Start)
(Upstream Model) 01/Jan. 7:00 09/Jan. 7:00
Simulation 1 Bathymetry information
prac_Up_OptOpe_10y.m21 + Result at 09/Jan. 7:00
Flow Model File (**.m21) Hot Start File
z Make a new Flow Model File (**.m21) Result File 1 created.
prac_Up_OptOpe_10y.m21
09/Jan. 7:00 18/Jan. 7:00
z Select bathymetry file
Simulation 2
grid-Up.dfs2
z Input parameters (Cold Start) Hot Start File Result File 2
use as
Simulation period : 3 days (from 11/Jan/90 12:00)
9 Bathymetry File 10

U2. Make a MIKE 21 Model (Cold Start) U2. Make a MIKE 21 Model (Cold Start)
[Basic Parameters] [Bathymetry] [Basic Parameters] [Results]
Cold Start
Tick Generate hot start
Specify bathymetry file

Specify directory and name of
Hot Start file to be created
11 12
Practice_M21-2
U2. Make a MIKE 21 Model (Cold Start) U3. Make a MIKE 21 Model (Hot Start)
[Basic Parameters] [Results] prac_Up_OptOpe_10y-
prac_Up_OptOpe_10y-hot.m21
Flow Model File (**.m21)
z Copy a cold start Flow Model File (**.m21)
25920 25920
Original: prac_Up_OptOpe_10y.m21
360 Copy: prac_Up_OptOpe_10y-hot.m21
(This means 1hr.
10sec x 360)
z Select hot start file as a bathymetry file
Max. of Range
HotS_Up_StOpe_010.dfs2
z Input parameters (Hot Start)
13
Simulation period : 3 day 14

U3. Make a MIKE 21 Model (Hot Start)
01/Jan. 7:00 09/Jan. 7:00 (Upstream Model)
Simulation 1 Bathymetry information [Basic Parameters] [Bathymetry]
+ Result at 09/Jan. 7:00
Hot Start
Hot Start File
Result File 1 created.
09/Jan. 7:00 18/Jan. 7:00

Specify Hot start file created by the
Simulation 2
previous simulation
(HotS_Up_StOpe_010.dfs2)
Hot Start File Result File 2
use as
Bathymetry File 15 16
MIKE 21 Mejerda Model : Practice U3 MIKE 21 Mejerda Model : Practice D1

U3. Make a MIKE 21 Model (Hot Start) D1. Make a MIKE 21 Model (Cold Start)
(Upstream Model) (Downstream Model)
[Basic Parameters] [Results] prac_Dn_OptOpe_10y.m21
Flow Model File (**.m21)
z Make a new Flow Model File (**.m21)
prac_Dn_OptOpe_10y.m21
360
(This means 1hr. z Select bathymetry file
Max. of Range 10sec x 360) grid-dn.dfs2
z Input parameters (Cold Start)
17
Simulation period : 3 days (12/Jan/90 7:00-) 18
Practice_M21-3
grid-
grid-dn.dfs2 prac_Dn_OptOpe_10y.m21
[Basic Parameters] [Boundary]
Closed Boundary
(by land value
value Program detected
500)
Automatically
filled
Mean High Sea
Water Level
0.5 mNGT (const.)
19 20

prac_Dn_OptOpe_10y.m21 D2. Post Processing : Overlay result dfs2 file
[Hydrodynamic Parameters] [Boundary] and GIS shp file (Downstream Model)
Dn_OptOpe2030_D2t_020yLL_3-
Dn_OptOpe2030_D2t_020yLL_3-18.dfs2
MIKE21 Result File (**.m21)
z Make a new Result View file (**.rev) (MIKE ZERO)
Constant 0.50
prac_rev.rev
z Select MIKE21 result file
[Projects] [Add Files to Project] Press new
file icon [MIKE21 Result File] Select
21
Dn_OptOpe2030_D2t_020yLL_3-18.dfs2 22

D2. Post Processing : Overlay result dfs2 file D2. Post Processing : Overlay result dfs2 file
and GIS shp file (Downstream Model) and GIS shp file (Downstream Model)
for
z Select MIKE21 result file Inundation :
animation
Data from
[Projects] [Work Area] browse dfs2 file
D_Carthage Carthage_UTM_Zone_32N (or
UTM_Carthage)
[Projects] [Add Files to Project] Press new
River channel
icon [Shape file] Select GIS shape file of the alignment:
Data from shp file
Mejerda River Topo2007_mejerda-down.shp 23 24
Practice_M21-4
D3. Post Processing : Make video file D4. Post Processing : Extract maximum
(Downstream Model) inundation depth in cells (Downstream Model)
[Projects] [Video] [Record...]
vide file name prac-Video MIKE 21 Result File (**.dfs2)
[OK] MIKE ZERO Toolbox
Select video file type (e.g.
Microsoft Video 1)
z Procedures
[OK] (recording starts) See separate papers
(Message : A video file ...... has
been created.)
[OK]
25 26
MIKE 21 Mejerda Model : Practice D4

D4. Post Processing : Extract maximum
inundation depth in cells (Downstream Model)
dfs2 file (Time series grid data)
Grid data
Water depth at Time step n
Time step = n
...
dfs2 file for t+1

t
...
...
max. depth 2
...
Time step = 1
27
Practice_M21-5
Republic of Tunisia
The Study
on
Lecture Type
in
Training
for
June 2008 models (demo version) MIKE FLOOD
Practice Items : MIKE Fl. Mejerda Model : Practice U1

MIKE FLOOD Mejerda Model
U1. Make a MIKE FLOOD Model (Improved
U1 : Make a MIKE FLOOD Model (Improved dam operation) (Upstream Model)
dam operation) prac_up_OptOpe.couple
U2 : Make a MIKE FLOOD Model (River MIKE FLOOD definition file (**.couple)
Improvement) (Modify linking chainages, Improved Dam Operation + Present Channel
z Make a new *.couple file
including modifying positions of Mark 1 & 3
prac_up_OptOpe.couple
of cross section)
z Specify MIKE11 (**.sim11) and MIKE21 (**.m21)
files
MIKE11: prac_Up_OptOpeU2_10y-mf.sim11
3
MIKE21: prac_Up_OptOpe_10y-mf.m21 4
MIKE Fl. Mejerda Model : Practice U1 MIKE Fl. Mejerda Model : Practice U1
U1. Make a MIKE FLOOD Model (Improved U1. Make a MIKE FLOOD Model (Improved
dam operation) (Upstream Model) dam operation) (Upstream Model)
Select
MIKE11 file : prac_Up_OptOpeU2_10y.sim11
MIKE21 file : prac_Up_OptOpe_10y.m21 1
Right click on this
window

MIKE21....
5 6
Practice_MF-1
2
1 Check Lateral link
River name: Select [Left] (or [Right]) River Name Chainage Chainage
Upstream Downstream
2-D model
MEJERDA-up 7119.190 145950.120
3 Mellegue 16725.350 45043.660
Chainage upstream: BouHeurtma 6400.700 17334.270
Chainage downstream:
Tessa 2772.070 20209.790
Upstream and downstream ends of
defined in MIKE 11) 7 8
prac_up_OptOpe.couple
z Specify simulation period (MIKE11 and MIKE21)

2 / Jan., 1990 12:00 ~ 3 days
9 10
U2. Make a MIKE FLOOD Model (River U2. Make a MIKE FLOOD Model (River
Improvement) (Upstream Model) Improvement) (Upstream Model)
prac_up_afterPro.couple prac_up_afterPro.couple
z Copy *.couple file
MIKE FLOOD definition file (**.couple)
Original : prac_up_OptOpe.couple
Improved Dam Operation + Present Channel & Copy : prac_up_afterPro.couple
Levee (Cross Section UP-124 to UP-90 z MIKE 11 and MIKE21
Modify linking chainages MIKE 11 :
modify positions of Mark 1 & 3 of cross section Folder Name : Sim_Bound_OptOpe_U2_010-afterPro
File Name: Prac_Up_OptOpeU2_010-afterPro.sim11
11
MIKE 21 : Prac_Up_OptOpe_10y-afterPro.m21 12
Practice_MF-2
U2. Make a MIKE FLOOD Model (River U2. Make a MIKE FLOOD Model (River
Improvement) (Upstream Model) Improvement) (Upstream Model)
prac_up_afterPro.couple prac_up_afterPro.couple
z Open MIKE11 sim file z Result file name
z Change cross section file MIKE 11 : Prac_Up_OptOpeU2_010-afterPro.res11
before: CS2007_MejUp.xns11 MIKE 21 : Res_OptOpe_10y-afterPro.dfs2
after : CS2007_MejUp-afterPro.xns11 z Open MIKE11 Cross section file
z Change chainage on MIKE FLOOD: Mejerda-Up z Change positions of Mark 1 and 3
Levee : Cross Section UP-124 to UP-90 Cross Section : UP-124 to UP-90
New Link : 7119.19 105187.7
117460.26 145950.12 13 14
Practice_MF-3

Annex 1: Mike11 Tutorial For The Mejerda Model Users: AN1.0 Introduction

Transféré par

Informations du document

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Annex 1: Mike11 Tutorial For The Mejerda Model Users: AN1.0 Introduction

Transféré par

Droits d'auteur :

Formats disponibles

The Study on Integrated Basin Management Mejerda Inundation Analysis Model

ANNEX 1 : MIKE11 TUTORIAL FOR THE MEJERDA MODEL

Tessa Dam Inflow

Source : Study Team

Nippon Koei Co.,Ltd. AN1-1 June 2008

Simulation Data Network Data

Cross Section Data

Hydrographs, Water Levels

Source : Study Team

Nippon Koei Co.,Ltd. AN1-2 June 2008

Box AN1.1: NOTE for French Operating System (Windows) Users

How to change or confirm the numbering system:

Box AN1.2: Note Regarding Inputting Data of MIKE11

AN1.1 Preparing Time Series File

(1) File extension : *.dfs0

(2) Example of time series data :

1st column : Time (hourly)

(ii) Make a dfs0 file

[All Program] [MIKE BY DHI] [MIKE11] [MIKE11]

Nippon Koei Co.,Ltd. AN1-3 June 2008

MIKE ZERO Time Series

Type necessary information

Select Equidistant Calendar Axis

Starting time of the excel data

The number of lines in the excel data

Nippon Koei Co.,Ltd. AN1-4 June 2008

Repeat same procedures for

Repeat same procedures

2 Check: This column should

Nippon Koei Co.,Ltd. AN1-5 June 2008

Save **.dfs0 file in an appropriate folder

(iii) Copy data in excel file to dfs0 file

Select a range of data cells

2 Execute Copy (ctrl + C) command on excel

The data are copied

Source : Study Team

AN1.2 Preparing Network File

(2) Major information contained in a network file :

(i) Prepare an excel file and text file

Prepare an excel file based on topographic survey result like below.

Nippon Koei Co.,Ltd. AN1-6 June 2008

These columns are used for network data, and

Check : 0 (zero) should

Select this range 2

Coordinate at the Cumulated distance

1 Open a new notepad file

Dont worry even if data

Save **.txt file in an appropriate folder

(ii) Make a nwk11 file

[All Program] [MIKE BY DHI] [MIKE11] [MIKE11]

MIKE 11 River Network

Nippon Koei Co.,Ltd. AN1-7 June 2008

Coordinate for Mejerda upstream model

Select meter for unit

Select the **.txt file created in (i)

[View] [Tabular View...]

Network Confirm this is Confirm this is

AN1.3 Preparing Cross Section File

(1) File extension : *.xns11

(2) Major information contained in a cross section file :

Nippon Koei Co.,Ltd. AN1-8 June 2008

Chainage (Distances of cross sections from the upstream end)

(i) Prepare an excel file