MIKE+ | What are the differences between MIKE 11, MIKE HYDRO River and MIKE+? How do I check that MIKE+ is set up appropriately after importing an old model?

'Models' tab (.sim11) > 'Models'

Choose desired models to simulate.

'Simulation specifications' > 'Modules'

Choose from list of 'River modules' to include in GUI ('Data') and/or simulate ('Sim.').

'General settings' > 'Model type' &
'Simulation specifications' > 'Simulation setup' editor > 'General' tab 

Features and Modules need to be activated in the 'Model type' under 'General settings' but also in the 'General' tab of the 'Simulation setup' under 'Simulation specifications'. These options make it more  flexible for the user especially when simulating the Rivers module as part of a coupled model.

'Simulation' tab (.sim11) > 'Simulation period'

Set up value for 'Time step type' ('Fixed time step' or Tabulated / Adaptive) and 'Time step'.

'Simulation specifications' > 'Time step  control'

Set up value for 'Fixed time step' type/length (or values for Tabulated/Adaptive time step type).

'Simulation specifications' > 'Simulation setup' editor > 'HD' tab 

Set up value(s) for 'Fixed' or 'Adaptive' Time step.

'Input' tab (.sim11) > Edit 'HD Parameters' > 'Initial' tab

Set up 'Global Values' and 'Local Values' in 'Initial conditions'.

'Initial conditions' > 'HD initial conditions' / 'State file'

Set up 'HD initial conditions' as:

• 'Global values' and
• 'Local branch values' or using
• 'Hotstart files'

Or load a pre-prepared 'State file'.

Notes:
• Possible to specify multiple hotstart files
• Possible to run a simulation using a hotstart file, which does not include all calculation points in the model
• Possible to define initial conditions from a state file, which contains more information than a hotstart file.

'Simulation specifications' > 'Simulation setup' > 'HD' tab &
'Initial conditions' > 'Initial conditions' editor
 

Choose from multiple 'User-specified' 'Network initial conditions' (each has a unique 'Initial conditions ID' defined in 'Initial conditions' editor). Alternatively the user may choose to run the simulation on an 'Empty network', from a 'State file' or as 'Steady state'.

'Input' tab (.sim11) > Edit 'Boundary data'

Select appropriate 'Boundary Description' (Open/Point Source/Distributed Source/Global/Structures/Closed) and Boundary Type for upstream ('Inflow' Boundary Type), downstream (normally 'Water Level' or 'Q-h') ends (excluding rivers connections), as well as any lateral inflows/outflows (Point/Distributed Source).

Note: Insert new boundaries at the table by clicking on the 'tab' keyboard button or Auto-create boundary conditions in network view ('Input' tab (.sim11) > Edit 'Network' > 'Network' menu > Auto Boundary Free Branch Ends)

'Boundary conditions' > 'Standard boundaries'

Select appropriate boundary 'Type' (Water level/Discharge/Q/h relation/Free outflow/Closed/Rainfall/Evaporation) and 'Location type' (Open/Point source/Distributed source/Storage) for upstream ('Discharge' Type), downstream (normally 'Water level' or 'Q/h relation') ends (excluding rivers connections), as well as any lateral inflows/outflows (Point/Distributed source).

Note: Insert new boundaries at the table by clicking on the '+' button (top left at the table) or auto-create boundary conditions by clicking on the 'Create open end boundaries' (top right of the dialog).

'Boundary conditions' > 'Boundary conditions' editor > 'Spatial extent' tab / 'Temporal variation' tab

Select appropriate boundary 'Type' (Inflow from result file/Open inflow to river/Source inflow to river/River water level/River Q/h relation/Free river outflow/Closed river boundary/Inflow to storage/Network rainfall/Network evaporation/Wind friciton/Groundwater leakage) for upstream ('Open inflow to river' Type), downstream (normally 'River water level' or 'River Q/h relation' or 'Free river outflow') ends (excluding rivers connections), as well as any lateral inflows/outflows (Source inflow to river).

Notes:

• Insert new boundaries at the table by clicking on the 'Insert' button or auto-create boundary conditions by clicking on the 'Insert all rivers' (top left at the editor).
• The simulation start and stop time ('Simulation specifications' > 'Simulation setup' > 'General' tab) should be within the time span of the boundary conditions, else errors shall be displayed in the validation dialog. The user can always check the simulation time span available by clicking on the 'Set Max Time' button (this sets the simulation start time from the latest start time of all boundaries and the simulation end time from the earliest end time of all boundaries) and then the simulation period may be modified accordingly.

Maximum dx for river branches

(distance between consecutive water level calculation 'h-points')

'Input' tab (.sim11) > Edit 'Network' > 'View' menu > Tabular View > Network: Branches > Maximum dx

Select appropriate 'Max dx' value for each branch

'Simulation specifications' > 'Computational control parameters' > Grid spacing

Select appropriate 'Maximum dx' value for each branch as:

• 'Global value' and
• 'Local values'

'River network' > 'Rivers' editor > 'Geometry' tab

The option to individually set a Max dx for specific branches is set in the 'Rivers' Editor.

'Input' tab (.sim11) > Edit 'Network' > 'View' menu > Tabular View > Network: Points > Change Type

Switch 'Chainage Type' for selected points (e.g. start/end points in branch) from 'System Defined' to 'User Defined' and, if needed, adjust chainage value.

'River network' > 'Branches' > Map view > 'Branches' ribbons menu > 'User defined chainage points' > 'Add' button

Add where appropriate 'User defined chainage points' at the Map view and adjust, where needed, their chainages at the 'Branches' tabular view.

Note: The concepts of user defined chainages have changed slightly. In MIKE HYDRO, we have branch vertices and user defined chainage points as separate features, and these two elements have replaced the functionality for ‘Points’ and ‘user defined/system defined chainages’ in MIKE 11.

'River network' menu > Target: User defined chainage > 'Create' button > click on map view to select points > 'Rivers' editor >  'Chainage points' tab

The number of chainage points can be defined by the user in Map view by creating user defined chainage points and then the chainage values may be adjusted in the 'Rivers' editor ('Chainage points' tab).

Note: In MIKE+ branches' vertices and user defined chainage points are set as separate features replacing the MIKE11 functionality for “points” and “user defined/system defined chainages”.

'Input' tab (.sim11) > Edit 'Network' > River network tools toolbar

Use buttons of 'River network tools' toolbar to add/delete/move digitization points.

'River network' > 'Branches' > Map view > 'Branches' ribbons menu > 'User defined chainage points' > 'Add' button

Vertices can be added (right click), deleted (double-left click), or moved (click and drag) while editing on the map view. In tabular view the user can click on the 'Edit coordinates of vertices' button ('Branches' dialog > 'General' tab) or import a shapefile by clicking on the 'Load shape' button.

'River network' menu > Target: Rivers > 'Edit' button > click on map view to insert/move/delete vertices

In MIKE+ Rivers, vertices can be added (left click), deleted (double-left click), or moved (click and drag) while editing on the map view, thereby directly modifying the branch.

Note: In MIKE+ Rivers the individual vertices are not visible in a table form, the chainages are only used to show the map correctly. Alternatively, the user can use the 'Import and export' tool ('Tools' menu) to import shapefiles/autocal files/etc of rivers/structures/etc.

'Input' tab (.sim11) > Edit 'Network' > 'View' menu > Tabular View > Network: Points >

The implementation in MIKE 11 included:

• Broad Crested Weir
• Special Weir
• Weir Formula 1
• Weir Formula 2 (Honma)
• Weir Formula 3 (Extended Honma)

'River network' > 'Structures' > 'Weirs' dialog

The implementation in MIKE HYDRO River is the same as in MIKE 11.

• Weir Formula 1= Villemonte Formula
• Weir Formula 2 = Honma Formula
• Weir Formula 3 = Extended Honma Formula

Special Weir has been replaced with the weir type “Broad Crested”. If same weirs' flow conditions are needed, specify the Q/h relations while unchecking the ”Allow for recalculation” flag in order to obtain the same setup as in MIKE 11 Special Weir.

Note: The name convention in MIKE+ Rivers has been modified in relation to MIKE 11.

'River network' > 'Weirs' editor

The implementation in MIKE+ is the same as in MIKE 11.

• Weir Formula 1= Villemonte Formula
• Weir Formula 2 = Honma Formula
• Weir Formula 3 = Extended Honma Formula

Special Weir has been replaced with the weir type “Broad Crested”. If same weirs' flow conditions are needed, specify the Q/h relations while unchecking the ”Allow for recalculation” flag in order to obtain the same setup as in MIKE 11 Special Weir.

Note: The name convention in MIKE+ Rivers has been modified in relation to MIKE 11.

'Input' tab (.sim11) > Edit 'Network' > 'View' menu > Tabular View > Network: Structures > 'Weirs' / 'Culverts' > Attributes > Valve

The weirs and culverts valve implementation in MIKE 11 includes the options:

• None
• Only Negative Flow
• Only Positive Flow
• No Flow

However, when applying the MIKE 11 Classic engine, the branch's flow direction is assumed to be positive (i.e. flow from upstream to downstream with increasing chainages).

'River network' > 'Structures' > 'Weirs' / 'Culverts' dialogs > 'General' tab > Attribute > Valve

In MIKE HYDRO, applying a valve regulation (only positive flow, or only negative flow) to culverts and weirs takes into account the branch's flow direction. For example, applying only a positive flow to a structure located on a branch with a negative 'Flow direction' will allow water to flow only in the direction of decreasing chainage values. This is the opposite of what the MIKE 11 Classic engine does. Therefore, after importing a MIKE 11 model, which used to be run with the MIKE 11 Classic engine into MIKE HYDRO, it is
necessary to change the flow direction for culverts and weirs, if any 'Valve' regulation is applied and if the branch is set to negative 'Flow direction'.

'River network' > 'Weirs' / 'Culverts' editors > 'Regulation' tab > 'Non return flap type' options

In MIKE+, applying a valve regulation (only positive flow, or only negative flow) to culverts and weirs takes into account the branch's flow direction. For example, applying only a positive flow to a structure located on a branch with a negative 'Flow direction' will allow water to flow only in the direction of decreasing chainage values. This is the opposite of what the MIKE 11 Classic engine does. Therefore, after importing a MIKE 11 model, which used to be run with the MIKE 11 Classic engine into MIKE+, it is
necessary to change the flow direction for culverts and weirs, if any 'Valve' regulation is applied and if the branch is set to negative 'Flow direction'.

Control Structures-
Rules

'Input' tab (.sim11) > Edit 'Network' > 'View' menu > Tabular View > Network: Structures > Control Str.

In MIKE 11, control structures are defined using control rules and control definitions.

'River network' > 'Control' > Sensors/Control rules

In MIKE HYDRO River, control structures are defined using sensors and control rules.

'River network' > 'Controls' editor > Sensors / Actions / Control rules

In MIKE+ Rivers, control structures are defined using sensors, actions and control rules.

The control definitions from MIKE 11 are listed in the Control rules editor in MIKE+ Rivers.

The priority criteria for the operation of the flow structure are defined in the ‘Rules’ tab in MIKE+ Rivers (also in MIKE HYDRO River), with the specific Conditions and respective Actions.

Notes:

• By default, a MIKE 11 model containing control-rules shows no sensors visible to the user. When this model is imported into MIKE+ Rivers (or MIKE HYDRO River) several sensors are created.
• When importing control rules from MIKE 11 or MIKE HYDRO River it is recommended to test each control rule separately to ensure it is working as expectedRelevant Knowledge Base article:

https://support.dhigroup.com/knowledgebase/article/KA-01114/en-us

'Input' tab (.sim11) > Edit 'HD Parameters' > 'Wave Approx' / 'Default Values' tabs

In MIKE 11, the Wave Approximation and Default computational control parameters can be found in the HD Parameters file.

The 'Water level exceedance factor' parameter can be found in the MIKE11.ini file that is stored in the installation folder (if the user needs to change the default values in MIKE11.ini file, the file needs to be copied in the model setup folder and modified accordingly before running the model).

'Simulation specifications' > 'Computational control parameters' > 'Wave approximation' / 'Computation parameters'

In MIKE HYDRO River, the Wave Approximation, the Default computational control parameters and some MIKE11.ini file parameters, including the 'Max. exceedance factor for depth above bank level', can be found in the Simulation specifications (Computational control parameters tabs).

Note: The MIKE11.ini file is not used when running a simulation in MIKE HYDRO.

'Simulation' menu > MIKE 1D engine configuration > check mainly 'HD Global' / 'HD River' groups of configuration items

Wave approximation, most MIKE 11/MIKE HYDRO River 'Default Values', as well as the 'Cross section extrapolation' and 'Cross section extrapolation height factor' parameters can be found within the 'MIKE1D engine configuration' dialog in MIKE+.

Note: The MIKE11.ini file is not used when running a simulation in MIKE+.

'Input' tab (.sim11) > Edit 'Cross sections'

In MIKE 11, when clicking 'Edit', the cross-sections file opens in the cross-sections editor within a separate user interface window (still within MIKE Zero).

Note: The cross-sections file can be opened from Windows explorer 

'River network' > 'Cross sections' > Tabular view

Cross sections are generally shown on the map in the same way as in MIKE 11. The only exception is that if a cross section has user specified coordinates, these are only used if both coordinate-sets are different from (0, 0).

Notes:

• MIKE HYDRO River stores the cross sections in the same file as MIKE 11 (file with extension .xns11). However, MIKE HYDRO River comes with a new cross section editor, which is available as an embedded editor from within MIKE HYDRO River (in the Cross sections menu).
• The cross-sections database file can also be opened from Windows explorer.
• When you delete a branch, all connected elements will also be deleted. The only exceptions to this behaviour are cross sections which are saved in a separate file and not automatically deleted when deleting a river branch.
• Cross sections can have polyline shapes, which means that (unlike MIKE 11) cross sections do not need to be straight lines.

River network > Cross sections

Cross sections are generally shown on the map in the same way as in MIKE 11. The only exception is that if a cross section has user specified coordinates, these are only used if both coordinate-sets are different from (0, 0).

Notes:

• The cross-sections file cannot be opened from Windows explorer (v. 2024 onwards).
• When you delete a branch, all connected elements will also be deleted. The only exceptions to this behaviour are cross sections which are saved in a separate file and not automatically deleted when deleting a river branch.

MIKE 11 model setup (.sim11) > 'Input' tab

MIKE 11 User Interface can open one model setup file (.sim11), which requires various input files to be associated with, e.g. river network (.nwk11), cross sections database (.xns11), boundary conditions (.bnd11), HD parameters (.hd11), AD model parameters (.ad11),...

MIKE HYDRO River model setup (.mhydro)

MIKE HYDRO River User Interface can open one model setup file (.mhydro), which requires one additional input file, namely the cross-sections database file (.xns11).

MIKE+ model setup (.mupp /.sqlite)

MIKE+ User Interface can open either a project file (.mupp) or a database file (.sqlite - even if it doesn't have a corresponding .mupp file, the .mupp file will be created automatically).

It still requires a cross-sections database file (.xns11), which however can be edited from the same User Interface.

Notes:

• The database (.sqlite or .postgis) is auto-saved! The model data and any change of value is saved to the database file right away. If you pause the mouse over any field you should be able to see the name of the table (e.g. 'msm_Project') and the name of the field (e.g. 'ComputationBegin' for the simulation start date - see screenshot below) within the database.
• The save button is only used to save the .mupp project file.
• The project .mupp file only stores "cosmetic" information, about layers added to the map, symbology or layout – i.e. how the various windows are docked/undocked, as well as the cross sections (.xns11) file.

MIKE 11

MIKE 11 can use both MIKE 11 Classic engine and MIKE 1D engine during the simulations.

MIKE HYDRO

MIKE HYDRO River can use only the MIKE 1D engine.

MIKE+

MIKE+ Rivers can use only the MIKE 1D engine.

Notes:

• MIKE 1D engine sometimes has more restrictive validations of input data than the MIKE 11 Classic engine, which means that you may sometimes need to adjust input data used by simulations made with MIKE 11 Classic engine, before these simulations can also run with MIKE 1D. If the MIKE 11 simulation cannot run with the MIKE 1D engine, you will also get errors when importing this model setup in MIKE+ Rivers. For this reason, the recommended steps to convert a MIKE 11 model to MIKE+ Rivers are:

• Run the MIKE 11 model setup using the MIKE 1D engine.
• Eventually adjust the model setup definition, according to the reported error messages, if any.
• Import in MIKE+ Rivers, when the simulation runs with MIKE 1D engine.

If you import the network file (*.nwk11) and the HD parameter file (*.hd11) separately, it is important to import the network file first. It is recommended to import the entire setup at once by importing the sim11-file.

For more information on importing old models you are referred to the Knowledge Base articles in https://support.dhigroup.com/knowledgebase/