Release Information
MOUSE

Release Note - 2009

Introduction

Welcome to MOUSE Release 2009.

Hardware Requirements

The recommended minimum hardware requirements are:

Supported Operating Systems: XP Professional (32 and 64 bit), Vista Business (32 and 64 bit)
Processor: 2.0 GHz PC (or higher)
Memory (RAM): 2.0 GB (or higher)
Hard disk: 40 GB (or higher)
Monitor: SVGA, resolution 1024x768 in 16bit colour
Graphic Card: 32 MB RAM (or higher), 24 bit true colour
Media: CD-ROM/DVD drive, 20 x speed (or higher)
File system: NTFS

Installation^ top

To install MOUSE, please choose 'MOUSE in the 'MIKE BY DHI Setup' dialog that appears when inserting the MIKE software 2009 DVD and then press the 'Install' button. Installation of MOUSE requires administrative rights on your pc - and in order to afterwards run MOUSE as a normal user special steps must be undertaken. Please refer to the Product Invocation section for this.

License File and Dongle^ top

To use MOUSE in licensed-mode please follow these steps:

  1. Make sure that the provided dongle is attached to the computer (parallel or USB port - for Windows XP Professional x64 Edition USB port only)
  2. The dongle driver is installed automatically during the setup of the program.
  3. The MIKE software license file (DhiLicense.dat) may be retrieved using the Internet. A working Internet connection and a valid e-mail address are required. The license file may be retrieved in two ways:
  • During installation of MIKE software
  • After installation of MIKE software, by launching the License Updater through the start menu
  1. To retrieve your license file during installation of MIKE software, select “Local” when prompted to select the type of License Management, and then select “Internet” and follow the on-screen instructions
  2. To update your license file using the DHI Software License Updater, simply launch “Start->Programs->MIKE BY DHI 2009->DHI License Updater” and follow the on-screen instructions.
  3. Alternatively, the license file can simply be copied from the supply medium (attachment to e-mail from DHI or CD/DVD/floppy disk) in  \Program Files\DHI\2009\License or Program Files (x86)\DHI\2009\License.

Product Invocation^ top

To start MOUSE, select the 'MOUSE icon under the 'MOUSE'  group, or go to Start -> Programs -> MIKE BY DHI 2009 -> MOUSE  and select 'MOUSE'.

Starting MOUSE without a DHI configured Software Key and valid license files causes the program to run in Demo mode. If this happens, a message box will inform you during program initialization. Running in Demo mode, MOUSE supplies full access to all editors, computational engines and editing facilities. However, restrictions apply to the setups that can actually be executed as a model simulation.

To run MOUSE as a normal user (not adminstrator) the following steps must be undertaken (as well as that the adminstrator needs to have executed all tools and runoff & pipeflow simulation engines once - e.g. on of the example data):

 

Press the 'Create a new local database' button.

 

Fill the server name field, select database location and press 'Create local server'.

Close 602conf8.exe.

Now copy the files wb8.fil and empty.fil to this newly created database directory (these files are found in C:\Users\"adminstrators user name" \AppData\Local\DHI\2009\MOUSE). Create a shortcut to syrakus.exe and use the new server name as parameter - e.g. MOUSE 2009_user. So the shortcut for syrakus.exe (which will launch MOUSE) will be  "C:\Program Files\DHI\2009\bin\Syrakus.exe" MOUSE2009_user). After that every user on the computer will have its own database. After these steps the user can run MOUSE and save projects to  directories, he/she has rights to write in.

 

Support^ top

The Software Support Centre can be reached by mail, e-mail, phone or fax:

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

software@dhigroup.com
Tel: +45 4516 9333 (Open 7.30-16.00 GMT)
Fax: +45 4516 9292

New Features^ top

Misc.
Ability for the user to define an initial water level throughout the model area (done through the ADP file)

 

Known Defects and Workarounds^ top

 

 

MOUSE 2009 Service Pack 1 - May 2009

 

No changes have done for MOUSE in Service Pack 1 (SP1)

 

MOUSE Service Pack 2 - June 2009^ top

 

Module/Type Error/Inconvenience/New Feature Status Remarks
Summary The values reported in the MOUSE Engine summary in section ”Grid point result summary”, column ”Hmax/D” were not written correctly to the summary. Fixed  
ADP-file Unit handling in ADP-file not working for initial water level section Fixed This affects US setups only
Lintels Restriction in lintels which ensured that the flow trough the lintel could maximum be the flow approaching the lintel on the street level changed.The allowed flow through a lintel is now changed from the approaching flow to the approaching flow + the available volume in the node/dt. Changed  

 

 

MOUSE Service Pack 3 - November 2009^ top

 

Module/Type Error/Inconvenience/New Feature Status Remarks
       
LTS
  • Weir discharge in first timestep of a LTS job is using information from the last timestep in the last LTS job
  • Network is initialized in a LTS job based on the boundaries from previous job
 		 Fixed  
Misc
  • Now possible to have pumps operating outside the pump curve table range
     
 New feature See DHIAPP.INI and ADP file documentation for further

 

MOUSE Service Pack 4 - February 2010^ top

 

Module/Type

Error/Inconvenience/New Feature

Status

Remarks

MOUSE Engine

  • Issue fixed with respect to generation of numeric water in computations with Pressure Mains using implicit solution

  • Correction in the MIKE FLOOD River/Urban link. The problem occurs with some setups only and results in no flow exchange between the models (MOUSE/MIKE 11)

  • Weir not initialized correctly when jumping to new job in LTS simulation
     

  • PCS simulations: The pump statistics Excel report produced by PCS simulations was not produced if one or more pumps did not start during the simulation period. An error message is now presented if the MS Excel application is not installed on the computer where the Excel report should be produced

  • Pressure Main simulations: Three new error checks have been introduced for setups with PM network sections. If any of the errors are found then the simulation is rejected.

1/ It is checked that PM links do not connect to nodes with pumps. (Short circuit to other pump stations)

2/ It is checked that PM links do not connect to non-PM links, unless through PM Tail nodes.

3/ It is checked that PM Tail Nodes are not stand alone without PM links connected.

  • Sealed nodes, large diameter: The sealed nodes will have a slot defined automatically above ground level (similar to the Preismann slot for pipes). It was found that the volume of the node slot was too large for sealed nodes with large diameters. An alternative function has been introduced for nodes with diameters > 1.0 [m].

  • Loading of CRF files: CRF files with very large number of time series (catchments) caused the HD simulation to run OUT OF MEMORY. The situation seems to appear for models with more than 25000 catchments.

    By introducing a flexible CRF file buffer size these models can be executed. The out of memory error will be reported if it occurs.

    The buffer size can be controlled by en entry in the ‘dhiapp.ini’ file. The keyword for this is BNDBUFFERSIZE

  • Pollutant components: Adding pollution components to runoff (CRF) set as a network load boundary using a specific keyword (LOAD_CRF_CLASSIC_STYLE) in the DHIAPP.INI file would cause errorneous results. Keyword is no longer valid with SP4 and pollution components added to runoff set as a network load boundary does not require special action in the DHIAPP.INI file.

  • LTS: The constant time step is not handled correctly when the time step is defined in the .MJL file

  • Warning and error messages. Generally a number of new warning and error messages have been added.

Fixed

 

Tools

M11Extra: The number of decimal digits in the text output file can now be controlled by a command line option. E.g. /DEC=6 will produce output with six decimal digits.

New feature

 

 

 

MOUSE Service Pack 5 - June 2010^ top

 

Module/Type

Error/Inconvenience/New Feature

Status

Remarks
Tools

MergeERF tool could result in display of error message depending on the Windows Regional Setting for ‘Short date’ format

Fixed

  

MOUSE Engine
  • Irregular ending of a runoff computation causes false error messages If the keywords (AllowPMlinksConnectToValves, AllowPMlinksConnectToPumps) and in the DHIAPP.INI file are set to 1 the error messages on pumps and valves in pressure main network sections are relaxed to warnings
  • When water is reversed through a valve there is a sign error in the solution
  • When applying the alternative low flow option for a setup the water can not flow backwards in a pipe if the pipe starts empty
  • Simulation does not complete when simulation runs longer than the IIR-file (input file)
  • Allowable flow for pumps was underestimated for pipes running under pressure
  • Max Inflow on nodes errorneously would apply to flow for each catchment connected instead of the total amount of inflow
  • Change in concept: For natural channels the last CRS defines the length of the topography. If the length of the topography is shorter than the computed length for the link the last cross section will be used for the remaining part of the natural channel. And vice versa, if the length of the topography is longer than the link length only the topography specified until the computed length (or user specified length) will be used.

Fixed

 

 

 

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

software@dhigroup.com - www.dhigroup.com