Release Note 2014

DHI Remote Simulation

Introduction


Welcome to DHI Remote Simulation Release 2014.

With this release, DHI offers access to remote simulation for corporate clients. The idea is that a user from a client computer is able to start a simulation remotely on a corporate hosted heavy duty computer. The remote simulation installation components are divided into a client component and a server component. Please consult the installation section of this Release Note, or the DHI Remote Simulation User Guide to get familiar with the solution.


System requirements


The recommended minimum system requirements are:

Operating systems

Fully supported operating systems *
Windows 7 Professional Service Pack 1 (32 and 64 bit), Windows 8 Pro (64 bit) and Windows Server 2008 R2 Standard Service Pack 1 (64 bit). For the latest update, please refer to the FAQ.

Non-supported but partially tested operating systems **
Windows XP Professional Service Pack 3 (32 bit), Windows 8 Pro (32 bit) and Windows Server 2012 Standard (64 bit). For the latest update, please refer to the FAQ.
Processor 2.0 GHz Intel Pentium or higher and compatibles, or equivalents
Memory (RAM) 2 GB (or higher)
Hard disk 40 GB (or higher)
Monitor SVGA, resolution 1024x768 in 16 bit colour
Graphics adapter 64 MB RAM (256 MB RAM or higher recommended), 24 bit true colour
Media DVD drive compatible with dual-layer DVDs is required for installation
File system NTFS
Software requirements .NET Framework 3.5 SP1 and .NET Framework 4.0 (Full Profile)

* Fully supported operational systems are systems that have been tested in accordance with MIKE by DHI's Quality Assurance procedures and where warranty and software maintenance agreement conditions apply.

** Non-supported but partially tested operating systems are systems, which are not officially supported by the MIKE by DHI software products. These operating systems have only undergone very limited testing for the purpose of MIKE by DHI software, but the software and key features are likely to work. Installation of MIKE by DHI software on a non-supported operating system is done so at the user's own risk. The MIKE by DHI software warranty and software maintenance agreement conditions do not apply for unsupported operating systems and DHI is under no obligation to provide assistance or troubleshooting for cases where the software is being used on a non-supported operating system.

Please note that single user installations are not allowed on server operating systems. Also, when running a fully supported operating system as a 'guest operating system' on a virtualisation platform, it is automatically downgraded to a non-supported operating system under the conditions provided above.


Installation

^ top

DHI remote simulation consists of a client part and a server part. The client part is by default always installed when installing any of the MIKE Zero based products and MIKE URBAN. To install the server components, choose a custom installation and select the Remote Simulation Server Components during the installation process. The server components should not be installed on client PCs, unless it is the intention to also use the PC as a server environment. The setup programme automatically installs all necessary remote simulation files and folders on your PC. Additionally, a 'MIKE by DHI 2014' entry is created, containing icons for various remote simulation utilities and links to documentation.


Licence file & dongle

^ top

DHI Remote Simulation requires a network licence management scheme. To use DHI Remote Simulation in licenced mode, please follow these steps:

  1. A DHI Network License Manager must be installed and configured on a system in your network. Please refer to the relevant documentation for the DHI Network License Manager.
  2. During installation of MIKE Zero or MIKE URBAN, choose 'Network mode' and configure the installation to point to the machine hosting the DHI Network License Manager, or:
  3. After completed installation, start the DHI License Administration tool (Under Start -> Programs -> MIKE by DHI 2014), go to the 'license mode control' tab, and configure your system to run in network mode with the designated DHI Network License Manager.

Product invocation

^ top

To start DHI Remote Simulation, go to Start -> Programs -> MIKE by DHI 2014 -> DHI Remote Simulation and select 'DHI Remote Simulation Console'. Starting DHI Remote Simulation without a valid licence will cause the programme to abort as demo mode is not supported.

When the 'DHI Remote Simulation Console' is running, you need to configure the connection to the server components of remote simulation. This requires the system administrator to have configured the server components. For details on setting up and configuring DHI Remote Simulation, consult the User Guide.


Support

^ top

For general support, please refer to our FAQ.

If you experience any difficulties, or if you have any questions, you can contact the Software Support Centre by mail, e-mail, phone or fax:

Software Support Centre
DHI
Agern Allé 5
DK-2970 Hørsholm
Denmark

mikebydhi@dhigroup.com
Tel: +45 4516 9333
Fax: +45 4516 9292

Or you can find your local support centre with support in your local language here.


New features

^ top

DHI Remote Simulation offers the following new features as of Release 2014:

  1. DHI Remote simulation now supports all engines, which are part of the MIKE Zero shell environment, including MIKE HYDRO simulations.
  2. Support for MIKE URBAN CS with the MOUSE engine has been included. MIKE URBAN must be installed on the machine(s) hosting the DHI Remote Simulation server environment, and the MIKE URBAN CS setup must be exported to a .mex file, which can be referenced from the DHI Remote Simulation Console. The .mex file must be exported using the "Advanced..." button of the MIKE URBAN Computation dialogue.
  3. Support for MIKE URBAN CS with the MIKE 1D engine has been included. MIKE URBAN must be installed on the machine(s) hosting the DHI Remote Simulation server environment, and the MIKE URBAN CS setup must be exported to a .m1dx file, which can be referenced from the DHI Remote Simulation Console. The .m1dx file must be exported using the 'Advanced...' button of the MIKE URBAN Computation dialogue.
  4. Support for MIKE 11 with the MIKE 1D engine has been included. When selecting a .sim11 as input file, users may now choose between the classic MIKE 11 engine and the MIKE 1D engine.
  5. MIKE FLOOD with MPI is now supported for local MPI configurations.
  6. GPU and GPU SP (Single Precision) MIKE 21 FM engines can now be chosen for MIKE 21 FM (HD only) simulations, if the DHI Remote Simulation Server environment supports GPU simulations. A NVIDIA Tesla GPU with CUDA compute capability of at least 2.0 and TCC (Tesla Compute Cloud) enabled is required.

Known defects & workarounds

^ top

  1. The model definition needs to use default file location for the output. Typically this is in a folder called '<model filename> - Result Files'. You may be able to upload and start simulations without following this scheme, but the results may not be downloadable. This is especially important to ensure when using a coupled model setup. All simulations must use the default simulation folder.
  2. Using the 'Save Output Files' table in AUTOCAL, the Remote Simulation Client requires that a copy of the file exists before uploading the simulation to the server.
  3. Using a MIKE 11.ini file next to the model setup file is not supported. A simple workaround is to copy the MIKE 11.ini into the MIKE Zero installation bin folder on the server running the feature service. Please note this may change the behavior for all MIKE 11 simulations.
  4. If res11read.exe is used in AUTOCAL to extract data from a res11 file, and the '-someres' or the '-compare' option is used in the setup file, then the files mentioned in these options must be specified in the 'Save Output Files' table.
  5. When creating a new simulation, special characters ('*', '?', '/', '\', ':', '<', '>') used by the operating system for file and path manipulation should be avoided in the simulation name as this may cause a failure when downloading results.
  6. By default, the services installed as part of the server components use the system account of the server. Running DHI Remote Simulation using the mpi adaptor requires the application, data, and feature services to be changed to run in a domain account. The domain account needs to have access to the shared 'basedatastorageurl' (see table 4.4 in the manual).

Fixed issues

^ top

A service pack includes fixes to inconveniences and errors and minor modifications to the official release.
Please note that the service packs are accumulative, i.e. corrections and fixes released with a previous service pack are included in the newest service pack as well.

Release 2014 Service Pack 3

Module/type

Error/Inconvenience/New feature

Status

No changes Unchanged
Release 2014 Service Pack 2

Module/type

Error/Inconvenience/New feature

Status

Remote Simulation Console When using a .sim11 file as input for a MIKE 1D simulation, the result file is not transferred correctly Fixed
Remote Simulation Console Remote Simulation Console fails to run the MIKE Zero based models, if the setup is configured to store result files in the same folder as the input file Fixed

Release 2014 Service Pack 1

Module/type

Error/Inconvenience/New feature

Status

Remote Simulation Console Improvements to customisation of download folder Fixed
Remote Simulation Console Occasional crash on shutdown when used on Windows XP 32 bit, or when used by different user profiles on the same workstation Fixed

Release 2014

Module/type

Error/Inconvenience/New feature

Status

General Support for MIKE URBAN CS (MIKE 1D and MOUSE), MIKE 11 using MIKE 1D and FM Series with GPU engine variants New features added
General Various minor improvements Fixed

MIKE by DHI - Agern Allé 5 - DK-2970 Hørsholm, Denmark - Tel: +45 4516 9200, Fax: +45 4516 9292

mikebydhi@dhigroup.com - www.mikebydhi.com