Warning

This adaptor is not supported anymore because MIKE 11 was last released with MIKE 2023.
When running a simulation, MIKE OPERATIONS will look for a MIKE Zero installation matching the MIKE OPERATIONS version. For example, MIKE OPERATIONS 2025 will run the simulation with
C:\Program Files (x86)\DHI\MIKE Zero\2025\bin\x64\DHI.Mike1D.Application.exe
Over time, newer versions of the MIKE1D engine will not run with the older MIKE 11 models registered in MIKE OPERATIONS.
We recommand upgrading to MIKE+.

MIKE 11 Adapter¶

The MIKE 11 adapter enables use of MIKE 11 model setups within the MIKE WORKBENCH. The adapter supports the following MIKE 11 modules:

HD
RR
DA
FF
ICE
AD
WQ

Limitations¶

The nwk11-file is required to provide projection. Without its model objects can only be created without GIS information.
Model objects are only enabled if the model setup can be parsed with MIKE1D. If the setup contains details not supported by MIKE1D, some or all model objects will be ignored. The input and output time series will still be configured, but without the geographical information (schema layout) and model variables as described by model objects.
- If Mean Area Weighting of time series is used the Catchment model objects (including NAM parameters) cannot be created for the MIKE Workbench but input and output time series from RR11-file will be assigned to the MIKE11 model object instead. (the reason is lack of support in v2011 of MAW by MIKE1D; hence the RR11 is not read to the point where catchment model object can be created).
- Only Regular reaches are supported. Other types will prevent schema (mode objects) in the MIKE Workbench.
- CrossSectionIDs must be unique. If CrossSection ID as non-blank defined it must be unique in the xns11-file.

Model objects¶

The below list of model objects can be derived from a MIKE 11 setup.

Branch
- Has no parameters
Calculation point
- River
- Chainage
- Type (H/Q point)
Cross section
- Name
- Location
- Cross section Data
- Processed Data
Cross Section data can be included in scenario to visualize the complex properties
Boundary
- Name
- Location
- Type (e.g. Open, Closed, PointSource, Q/H,...)
- SubType (e.g. Water Level)
Catchment
- Name
- Catchment model type
- NAM model parameters (if type is NAM)
  - Area
  - ...
Area can be included in scenario to visualize the complex parameters
Structure
- Name
- Type (e.g. Weir, Control,...)
- Weir properties
Type can be included in scenario to visualize the complex parameters.
MIKE 11 model object
- No parameters but is used to tie all un-associated input and output time series to the model setup.

Configuration¶

The MIKE 11 adaptor can work with both MIKE 11 and MIKE 1D engines. When registering a model, the adaptor will read the sim11 file and look at the defined HD result and hotstart (if applicable) files. Both need to have the same extension (.res1d or .res11). This will decide which engine will be use by MIKE OPERATIONS to run the model.

For both engines, the adaptor can handle all necessary files (log files, result, hotstart, etc.).

Note

Note that MIKE 11 is not released with MIKE 2024 and future versions. This means that MIKE 11 models only works with the MIKE1D engine from MIKE OPERATIONS 2024.

Model Registration¶

To register a MIKE 11 model, right click the Model Setups node in the Scenario Explorer and select Register model.

Select MIKE 11 and click Next.

The MIKE 11 model registration information page will show.

Select a model file and specify a Model name.

If the projection is not specified in the network file of the model, the following information will be displayed.

Click Yes and the model registration wizard will parse the model and display model objects found.

Add a new initial condition by clicking the right-click menu Add New File.

Verify the model objects and click Prepare for Registration.

Click Finish.

If the projection used by the model is not supported by the GIS manager of MIKE Workbench, the information dialog below will be shown.

Click OK.

Specify a name of the model and the model group.

Folder is a read only field. The folder made from the root folder, shared by all models of the database workspace (connection), found in the Settings in the System Explorer as Models Folder.

This folder is used for simulation results.

Click Next.

Click Finish to complete the registration.

The model setup is now available in the scenario explorer in MIKE Workbench.

Launch command¶

The default launch command of the MIKE 11 model adapter is DHI.Mike1D.Application.exe.

This command is used for executing the MIKE 11 model when running simulations.

The launch command can be changed in the MIKE11 Adapter.xml created during model registration.

<?xml version="1.0"?>
<MIKE11Adapter>

  <!--  ... -->

  <RRFile>liver.RR11</RRFile>
  <LaunchCmd>DHI.Mike1D.Application.exe</LaunchCmd>
  <LaunchArguments>-stacktrace -mz</LaunchArguments>
  <LaunchSilentArguments>-stacktrace -mz -silent</LaunchSilentArguments>
  <EditModelCmd>MZShell.exe</EditModelCmd>
  <Folders>
    <String>RRCalibration</String>
  </Folders>
</MIKE11Adapter>

Updating the launch command requires that the model setup is exported e.g. using the Open in Native Tool or by using an export script, so that that the MIKE11 Adapter.xml can be changed.

After changing the MIKE11 Adapter.xml file, the exported model, should be zipped and imported again, e.g. by using an zip and import script in the script manager.

def ReZipSetup(modelSetupPath, directory):
    """
    <Script>
    <Author>admin</Author>
    <Description>Script to zip a folder and assign the result as content to a modelsetup, ths updating the blob</Description>
    <Parameters>
    <Parameter name="modelSetupPath" type="string">The full path of the model setup in the database (copy Full Path)</Parameter>
    <Parameter name="directory" type="string">The directoy path in windows where the setup has been unpacked</Parameter>
    </Parameters>
    </Script>
    """
    if (System.IO.Directory.Exists(directory) == False):
        return;

    scm = app.Modules.Get("Scenario Manager");
    modelsetup = scm.ModelSetupList.Fetch(modelsetupPath);
    zipptr = BaseAdapter.ZipFiles(directory, None, "no Adapter");
    modelsetup.Content = zipptr;
    scm.ModelSetupList.Update(modelsetup, True);

Warning

Be carefull when editing the model information and importing the changes, as the model information is used "as is" when running simulations.