Flood Modeller Tutorial Module01: Difference between revisions
Content deleted Content added
Tuflowduncan (talk | contribs) |
|||
| (31 intermediate revisions by 5 users not shown) | |||
Line 4:
1D-2D linked models are able to utilise the individual benefits of 1D and 2D solution schemes. In this example, the 1D Flood Modeller scheme is used to represent the watercourses where the flow is essentially uni-directional. A 2D scheme is suited to the representation of floodplains where more complex flow patterns may occur. <br>
<br>
As [[
[[file:Poor_2d_rep.png|400px]]<br>
Using a cell size that is coarse relative to the width of the watercourse channel may reduce the accuracy of the conveyance in the channel. There are two options for improving the representation of the creek channel:<br>
* decrease the width of the 2D cells; and/or
* model the channel as a 1D network, dynamically linked to the 2D domain (the floodplain).
In the [[
TUFLOW may be dynamically linked to 1D networks using the hydrodynamic solutions of ESTRY (TUFLOW 1D), Flood Modeller
Setting up a 1D/2D model where the 1D channel cuts through the 2D domain is probably the most time-consuming type of a model to setup. However, the reduction in simulation time can be beneficial and make this a good approach. For this module, the complete Flood Modeller 1D model has been provided, to allow for progressing through the module in a relatively short period of time.<br>
=Existing Model Data=
This tutorial builds upon the 2D TUFLOW domain that was constructed as part of [[Tutorial
The model developed in these tutorial modules already contains some culverts modelled as 1D elements. The culverts are modelled in ESTRY, TUFLOW's internal 1D engine. One of these culverts will be kept in ESTRY and the other will be added to the Flood Modeller model.<br>
The 2D boundary conditions (upstream inflows and downstream stage-discharge boundary) will be removed from the model. These will instead be represented in Flood Modeller as it is a more typical schematisation for a 1D/2D linked model.<br>
Line 25:
*1D/2D boundary links to connect the 1D ESTRY culverts to the 2D TUFLOW domain.
For further information on these elements, please refer to [[Tutorial
==Flood Modeller==
Line 34:
*<b>IEF</b>: A blank folder in which to store Flood Modeller Event Files used to simulate the model.
*<b>RES</b>: A blank folder in which to write the Flood Modeller result files.
For further information on each file type, please refer to the [
For this tutorial, the floodplain of the study area will be modelled entirely in TUFLOW.
The cross-sections in the Flood Modeller 1D model have been trimmed to the top of bank to ensure there is no double-counting of storage within the floodplain.
Line 79:
'''Mapinfo'''<br>
Add an extra command line after <font color="blue"><tt> Read GIS Code </tt></font><font color="red"><tt>==</tt></font>..\model\mi\
:<font color="blue"><tt>Read GIS Code BC </tt></font> <font color="red"><tt>== </tt></font> mi\
Note that the order of the commands is important. The layer '''2d_code_FMT_M01_001.MIF''' first activates cells within the modelled area then the layer '''2d_bc_FMT_M01_HX_001.MIF''' deactivates selected cells along the watercourse. ▼
▲Note that the order of the commands is important. The layer '''2d_code_FMT_M01_001.MIF''' first activates cells within the modelled area then the layer '''
'''Other GIS'''<br>
Add an extra command line after <font color="blue"><tt> Read GIS Code </tt></font><font color="red"><tt>==</tt></font>..\model\gis\2d_code_FMT_M01_001_R.shp
:<font color="blue"><tt>Read GIS Code BC </tt></font> <font color="red"><tt>== </tt></font> gis\2d_bc_FMT_M01_HX_001_R.shp <font color="green"><tt> ! Deactivates the cells where the watercourse has been modelled in 1D </tt></font>
Line 92 ⟶ 91:
<li> Topography amendments should be added in a new section at the bottom of the TGC. These are: </li>
'''Mapinfo'''<br>
:<font color="blue"><tt>Read GIS Z HX Line MAX </tt></font> <font color="red"><tt>==</tt></font> mi\
The two GIS layers must be read in together on the same command line. This tells TUFLOW to associate the points within the '''2d_bc_FMT_M01_HX_001_P.MIF''' layer (defining elevation) with the polylines within the '''
'''Other GIS'''<br>
Line 113 ⟶ 112:
'''Mapinfo'''
:Put an exclamation mark before the line reading. This tells TUFLOW to treat this command line as a comment:<br>
:<font color="blue"><tt>Read GIS BC</tt></font> <font color="red"><tt>== </tt></font> mi\
'''Other GIS'''
:Put an exclamation mark before the line reading:<br>
Line 120 ⟶ 119:
<li> Update the 1D/2D boundary links at the ESTRY culverts with the new layer:</li>
'''Mapinfo'''
:<font color="blue"><tt>Read GIS BC</tt></font> <font color="red"><tt>== </tt></font> mi\
'''Other GIS'''
:<font color="blue"><tt>Read GIS BC</tt></font> <font color="red"><tt>== </tt></font> gis\2d_bc_M04_culverts_001_L.shp <font color="green"><tt>! This command reads in SX boundaries linking the 1D ESTRY culverts to the 2D domain</tt></font>
Line 126 ⟶ 125:
<li> Add reference to the 1D/2D boundary links that connect Flood Modeller to the 2D floodplain:</li>
'''Mapinfo'''
:<font color="blue"><tt>Read GIS BC </tt></font> <font color="red"><tt>== </tt></font> mi\
'''Other GIS'''
:<font color="blue"><tt>Read GIS BC </tt></font> <font color="red"><tt>== </tt></font> gis\2d_bc_FMT_M01_HX_001_p.shp | gis\
<li> Save the file. The boundary control file is now ready to be used.
Line 138 ⟶ 137:
<li> Read in the GIS layer of the Flood Modeller Nodes </li>
<li> Read in the GIS layers to create Water Level Lines along the Flood Modeller component of the model (optional) </li>
<li>
<li> Update reference to the boundary control file (.tbc) and geometry control file </li>
<br>
Line 153 ⟶ 152:
<li> We need to read in the GIS layers of the Flood Modeller Nodes. Place the below command line anywhere in the .tcf. It is good practice to create a section within the .tcf to reference all 1D commands: <br> </li>
'''Mapinfo'''<br>
:<font color="blue"><tt>Read GIS X1D Nodes</tt></font> <font color="red"><tt>== </tt></font>..\model\mi\
'''Other GIS'''<br>
:<font color="blue"><tt>Read GIS X1D Nodes</tt></font> <font color="red"><tt>== </tt></font>..\model\gis\1d_x1d_FMT_M01_nodes_001_P.shp <font color="green"><tt>! GIS layer referencing node IDs from Flood Modeller </tt></font>
Line 159 ⟶ 158:
<li> Add commands to read in the GIS layers referencing Water Level Lines drawn along the Flood Modeller component of the model: <br> </li>
'''Mapinfo'''<br>
:<font color="blue"><tt>Read GIS X1D Network</tt></font> <font color="red"><tt>== </tt></font>..\model\mi\
:<font color="blue"><tt>Read GIS X1D WLL</tt></font> <font color="red"><tt>== </tt></font> ..\model\mi\
'''Other GIS'''<br>
:<font color="blue"><tt>Read GIS X1D Network</tt></font> <font color="red"><tt>== </tt></font>..\model\gis\1d_x1d_FMT_M01_nwk_001_L.shp <font color="green"><tt>! GIS layer representing channels to allow for the digitisation of Water Level Lines (optional)</tt></font>
:<font color="blue"><tt>Read GIS X1D WLL</tt></font> <font color="red"><tt>== </tt></font> ..\model\gis\
<li> Add commands to read in the an Esty Control File which contains references to some of the culverts present on the floodplain: <br> </li>
<li> Finally, update the links to the Geometry control file and Boundary Condition control file:</li>▼
:<font color="blue"><tt>ESTRY Control File</tt></font> <font color="red"><tt>== </tt></font>..\model\FMT_M01_001.ecf <font color="green"><tt>!Reference the ESTRY Control File </tt></font>
▲<li> Finally, update the links to the Geometry control file,
:<font color="blue"><tt>Geometry Control File</tt></font> <font color="red"><tt>== </tt></font>..\model\FMT_M01_001.tgc
:<font color="blue"><tt>BC Control File</tt></font> <font color="red"><tt>== </tt></font>..\model\FMT_M01_001.tbc
:<font color="blue"><tt>BC
This concludes the changes that we need to make to the .tcf
</ol>
==Flood Modeller Simulation Files==
Line 205 ⟶ 208:
<li> Add the 'Additional Output' tab by clicking View> Tabs > Additional Output. On the 'Additional Output' tab, select the check box for '2D Flow...'. This will add extra output to check the Flood Modeller and TUFLOW link. We will review this additional output in the following section.</li>
<li> Save the Scenario Data. </li>
</ol>
=Run the Simulation=
Line 211 ⟶ 215:
<br>
In the <b>Complete_Model\FMT_M01\Flood_Modeller\IEF</b> folder a batch file has been provided. To use the batch file in this tutorial:<br>
*Ensure that you [
*Move the batch file to the <b>FMT_Tutorial\FMT_M01\Flood_Modeller\IEF</b> folder
*Open the batch file in a text editor. On the 'set FloodModeller=' line, change the path from the one provided to the full path to the ISISf32.exe file that you set up with the installation folders.
Line 217 ⟶ 221:
*Double click the batch file in your file explorer to run the file
<br>
When the simulation is running, the Flood Modeller status window will open. Flood Modeller will then open a
[[file:
The simulation will take a few minutes depending on the hardware setup.<br>
<br>
=Review the Results=
Modelled results can be processed, reviewed and visualised in many different packages.<br>
For a complete introduction to the different options, [
<br>
==TUFLOW HPC==
To run the linked TUFLOW-Flood Modeller Pro model using HPC we simply need to add a single line to the Tuflow Control File. The HPC solver will only speed up the 2D calculations within the linked 1D-2D model, it will not speed up the 1D calculations that take place in the Flood Modeller Engine.
The relatively small nature of this specific model means that use of HPC on multiple CPU cores may not lead to significant improvements to model run times. However, should the machine have an NVIDIA GPU card present then it is possible to run the HPC solver on the GPU to significantly improve model runs times. The larger the 2D domain, the more significant the improvements to model run times through the use of the HPC solver.
To utilise the HPC solver:-
<ol>
<li> Save the TUFLOW runfile ( <b>FMT_M01_001.tcf</b>) as <b>FMT_M01_002.tcf</b>.</li>
<li> Add the following command to the TCF file:
:<font color="blue"><tt> Solution Scheme </tt></font> <font color="red"><tt>== </tt></font>HPC <font color="green"><tt>! Use HPC solver to run the simulation</tt></font>
<li> If you have a CUDA enabled NVIDIA GPU device, you can also add the following command to run the HPC solver using GPU hardware:
:<font color="blue"><tt> Hardware </tt></font> <font color="red"><tt>== </tt></font>GPU <font color="green"><tt>! Run HPC solver on GPU</tt></font>
<li> Save the TCF file and run the model.Troubleshooting for GPU Simulation
</ol>
===Troubleshooting for GPU Simulation===
If you receive the following error when trying to run the TUFLOW HPC model using GPU hardware:
<pre>TUFLOW GPU: Interrogating CUDA enabled GPUs …
TUFLOW GPU: Error: Non-CUDA Success Code returned
</pre>
or
<pre>ERROR 2785 - No GPU devices found, enabled or compatible.
</pre>
Please try the following steps:
<ol>
<li> Check if your GPU card is an NVIDIA GPU card. Currently, TUFLOW does not run on AMD type GPU.
<li> Check if your NVIDIA GPU card is CUDA enabled and whether the latest drivers are installed. Please see <u>[[GPU_Setup | GPU Setup]]</u>.
</ol>
<br>
If you experience an issue that is not detailed above please send an email to [mailto:support@tuflow.com support@tuflow.com]<br>
=Conclusion=
We introduced the user to the linking of a TUFLOW 2D domain to a 1D Flood Modeller model.<br>
For further training opportunities see <u>[https://tuflow.com/training/training-course-catalogue/ TUFLOW Training Catalogue]</u> and/or contact <u>[mailto:training@tuflow.com training@tuflow.com]</u>. <br>
<br>
{{Tips Navigation
|uplink=[[Flood_Modeller_Tutorial_Model| Back to Flood Modeller Tutorial Model]]
}}
| |||