MIKE Flood to TUFLOW: Difference between revisions
Content deleted Content added
Ellis Symons (talk | contribs) |
Ellis Symons (talk | contribs) No edit summary |
||
Line 9:
* xsGenerator.exe (for MIKE11 conversion)
MIKE Zero is required to extract data from the MIKE FLOOD model. The tools required are freely available using the Demo version of Mike Zero.<br>For MIKE11 conversion, the xsGenerator utility has been made to automate some of the steps. The xsGenerator utility is freely available from the
=Creating a TUFLOW Geometry Control File from MIKE21=
Line 34:
</ol>
Unlike TUFLOW, the grid cell size of the model in MIKE is determined directly by the input grid file. For more discussion on grid cell size and the differences in how MIKE and TUFLOW handle the underlying terrain please see the
==Converting Manning's==
Line 46:
</ol>
More information on reading in manning’s grids into TUFLOW is provided in
==Model Domain==
Line 60:
</ol>
<br>More information on setting the model domain extent and rotation in TUFLOW is provided in
==TUFLOW Code Layer==
Line 104:
* Viewing <b>Item</b> which corresponds to the boundary name<br>[[File: MIKE21-HP-Boundary-Names.PNG|750px|]]
The Upstream boundary can be digitised in TUFLOW as a 2d_bc (type ‘HT’), or as a 2d_SA polygon. For more discussion on selecting an appropriate upstream boundary type, please see the
==Source Boundaries==
Line 110:
The location of source boundaries can be found in the MIKE21 control file (.m21) in the <b>Basic Parameters</b> >> <b>Source and Sink</b> tab. The location of the boundaries are specified as a point object using the local (j, k) coordinate system. These are required to be converted to absolute coordinates so an identical boundary location can be digitised in TUFLOW. The conversion process can be undertaken using identical steps as performed with converting upstream and downstream boundaries.
It is recommended that the source boundary point from MIKE be converted to a 2d_SA polygon in TUFLOW. The 2d_SA polygon should be enlarged to encompass a larger region such that it is able to apply flow to more than one cell. This is considered to give a more stable and accurate representation of flow distribution to the model. More information on how 2d_SA polygons distributes flow can be found in
The name of the boundary can be found from <B>Hydrodynamic Parameters</b> >> <b>Source and Sink</b> tab.<br>[[File: MIKE21-HP-Source-Names.PNG|750px|]]
Line 118:
The location of the 1D / 2D boundaries can be found in the MIKE Flood control file (.couple) under the <b>Link Definitions</b> tab. The (X, Y) coordinates specify the vertices of a polyline that can be digitised in TUFLOW using either ‘SX’ or ‘HX’ connections.<br>[[File: MIKEFlood-Linkages.PNG|750px|]]
More information on 1D/2D linking in TUFLOW can be found in
=Creating a Boundary Control Database from MIKE=
A Boundary Control Database (bc_dbase) consists of the values (time series or constant value) and the linking boundary names. The boundary names, constant values, and data source for time series, can be obtained from the steps outlined in:
*
*
==Converting DSF0 time series==
Line 136:
</ol>
The time series will need to be formatted so that the time column units are in hours. This can be done in MS Excel or equivalent. More information on setting up inflow boundaries
=Creating an Estry Control File from MIKE11=
Line 148:
==1D Network Conversion (xsGenerator.exe Utility)==
To make the conversion of the MIKE11 1D network easier, the xsGenerator utility has been built to automate the bulk of the conversion. The xsGenerator.exe utility is freely available to download from the <u>[https://www.tuflow.com
To undertake the automation, a number of files will be required as inputs:
Line 191:
<li> This will display all 1D boundaries<br>[[File: MIKE11-bnd11.PNG]]
</ol>
Identifying the boundary types and values is as simple as reading the Boundary Type, TS Type, and File/Value. The only thing to be careful of is that 1D/2D linking boundaries are usually specified as Water Level and won’t need to be transferred across (1D/2D linking conversion has already been discussed in
==1D Run Settings==
Line 206:
<li> You can obtain the start and end dates from this tab which need to be converted to hours for TUFLOW (in the screenshot below, the simulation duration is 3 hours)<br>[[File: MIKE21-Simulation-Period.PNG]]
</ol>
The 2D timestep should be set to an appropriate TUFLOW interval and not be copied directly from the MIKE21 model. It also up to the user to consider output types and time series Plot Output (PO) locations. More information on appropriate timestep intervals and map output types can be found in
=Discussion=
| |||