View source for Tutorial M01

= Introduction = 
Read the <u>[[Tutorial_Introduction | Tutorial Model Introduction]]</u> before starting this tutorial. It outlines programs requiring installation and provides the tutorial dataset download link.<br>

In this module, a fully two-dimensional (2D) model is built with a number of TUFLOW control files and Geographic Information System (GIS) layers.<br>

The TUFLOW control files are:<br>
:* TUFLOW Simulation Control File (TCF)
:* TUFLOW Geometry Control File (TGC)
:* TUFLOW Boundary Control File (TBC)
:* TUFLOW Boundary Condition Database (bc_dbase)
:* TUFLOW Materials File (materials)<br>

The GIS layers are:<br>
:*TGC layers:
<ol><ol><li> 2d_loc: A layer defining the origin and orientation of the 2D grid. 
<li> 2d_code: A layer containing polygons that define the cell codes (active or inactive status).
<li> *.flt: A DEM dataset defining the ground elevations within the 2D study area.
<li> 2d_mat: A layer defining the land-use (material) types within the 2D study area.</ol></ol>
:*TBC layers:
<ol><ol><li> 2d_bc: A layer defining the locations of external 2D boundaries.
<li> 2d_sa: A layer to define internal 2D flow boundaries.
</ol></ol>
:*TCF layers:
<ol><ol><li>2d_po: A time series data output from 2D domains, for a range of hydraulic parameters.
</ol></ol>
<br>

= Project Initialisation = 
TUFLOW models are separated into a series of folders which contain the input and output files. The recommended set up for the model directory and sub-folders is shown below. For a more detailed description, see the Folders and File Types Section of the <u>[https://downloads.tuflow.com/_archive/TUFLOW/Releases/2018-03/TUFLOW%20Manual.2018-03.pdf 2018 TUFLOW Manual]</u>. <br>
<ol>
[[File:Tute M01 Directory Structure v3.png|left]]
{| class="wikitable"

! style="background-color:#005581; font-weight:bold; color:white;"| Sub-Folder
! style="background-color:#005581; font-weight:bold; color:white;" width=10%| Input / Output
! style="background-color:#005581; font-weight:bold; color:white;" width=75%| Description
|-
| bc_dbase|| Input || Boundary condition database(s) and input time-series data.
|-
| check|| Output || GIS and other check files to carry out quality control checks (use Write Check Files).
|-
| model|| Input ||Geometry (TGC), Boundary (TBC) and other model control text files (i.e. no GIS files).
|-
| model\gis|| Input || GIS layers that are inputs to the 2D and 1D model domains are contained within this folder, model\gis is typically used for all QGIS and ArcGIS files.
|-
| model\mi|| Input || GIS layers that are inputs to the 2D and 1D model domains are contained within this folder, model\mi is typically used for MapInfo formatted GIS files.
|-
| results|| Output|| TUFLOW outputs the results to this folder in a specified formats.
|-
| runs|| Input|| TUFLOW Control Files (TCF).
|-
| runs\log|| Output || TUFLOW log files (TLF) and messages layers.
|}
</ol>
The TUFLOW folders can be set up manually, automatically running TUFLOW model with <font color="blue"><tt> Create Empty GIS Files </tt></font> command or automatically through GIS programs:
:*<u>[[Configure_TUFLOW_Project | QGIS]]</u>
:*SMS - the folder structure listed above is automatically created before running the model using the 'Export TUFLOW files' command (see <u> [[Run TUFLOW from within SMS | Run TUFLOW from within SMS]])</u>.
:*ArcMap (10.1 and newer) - the ArcTUFLOW Toolbox can be used to automatically create the model folders, model projection, TUFLOW control files and run TUFLOW to create the template files.

The following points on TUFLOW folders and filenames are worth noting: 
:*TUFLOW accepts any folder structure, though the above listed format is most commonly used and is recommended. <br>
:*TUFLOW accepts spaces and special characters (such as ! or #) in filenames and paths, but other software may not. It is recommended that spaces and other special characters are not used in the simulation path and filenames. <br>
:*Folder paths, filenames, file extensions and TUFLOW commands are not case sensitive in any TUFLOW control files. <br>
:*Any directories that don't apply can be omitted, for example, if using QGIS or ArcMap the model\mi directory is not required. <br>
<br>

= Model Familiarisation=
Become familiar with the model location, using an aerial image and DEM:<br>
:*<u>[[Draft_site_familiarisation | QGIS]]</u>
<br>

= TUFLOW Geometry Control File (TGC) =
The TGC file is a series of commands that build the geometry model. At its minimum, the TGC contains:
:*Information on the size and orientation of the grid;
:*Grid cell codes (whether cells are active or inactive);
:*Bed / ground elevations; and
:*Bed material type or flow resistance value.

Commands in the TGC file are applied in sequential order; the order (layering) of these commands is critical. The last occurrence of a command prevails, it is possible to override previous information with new data to modify the model in selected areas. This is useful but is also something to be aware of as to not override commands by mistake. 

=== 2D Domain ===
Grid formats currently supported by TUFLOW include the ESRI ASCII Grid format (.asc) and binary grids (.flt). The Digital Elevation Model (DEM) is provided in .flt format. <br>

Defining the location and orientation of the TUFLOW 2D domain can be undertaken using four different methods: <br>
:*Specifying origin coordinates and a second set of coordinates for a point along the X-axis of the domain; <br>
:*Specifying the origin coordinate and domain orientation angle; <br>
:*Digitising a line (2d_loc) to represent the bottom edge of the 2D domain (with the line starting at the origin and finishing at a secondary location along the X-axis); or <br>
:*Digitising location polygon. <br>

The first method is covered in this tutorial as it is required to use a licence-free version of TUFLOW. The third method is the most commonly used. <br>
<ol>
<li>Create a new text file called '''M01_001.tgc''' and save it in '''Module_01\TUFLOW\model''' folder. Notice the use of ‘001’ for numbering. This is part of a naming convention, allowing for the iteration of both GIS and TUFLOW control files. This way allows files to be recognised from a specific run and also reverted back to a working iteration in model development. <br>
<li>Open the created '''M01_001.tgc''' in a text editor and specify the location and dimensions of the TUFLOW domain (rectangular computational area) and the cell size: <br>

<font color="blue"><tt>Origin </tt></font> <font color="red"><tt>== </tt></font> <font color="black"><tt>292725, 6177615</tt></font> <font color="green"><tt>  ! Bottom left corner (origin) of the 2D grid</tt></font><br>
<font color="blue"><tt>Orientation </tt></font> <font color="red"><tt>== </tt></font> <font color="black"><tt>293580, 6177415</tt></font> <font color="green"><tt>  ! Point along the X-axis determining the orientation of the 2D grid </tt></font><br>
<font color="blue"><tt>Cell Size </tt></font> <font color="red"><tt>== </tt></font> <font color="black"><tt>5</tt></font> <font color="green"><tt>  ! 2D cell size in metres</tt></font><br>
<font color="blue"><tt>Grid Size (X,Y) </tt></font> <font color="red"><tt>== </tt></font> <font color="black"><tt>850, 1000</tt></font> <font color="green"><tt>  ! 2D grid extent dimensions in metres</tt></font><br>
</ol>

=== Active and Inactive Areas of the 2D Domain ===
By default, every grid cell in a TUFLOW model is set as active and TUFLOW allows water to flow anywhere within the extents of the 2D domain. It is rare for a catchment to be a perfect rectangle. To reduce output file sizes and run times, permanently dry areas can be removed from the model. This can be an iterative process (i.e. run the model initially and refine). For the purpose of the tutorial a polygon is provided to define the active area. <br>
<ol>
<li>Set all 2D cells within the model domain rectangle to inactive by adding the following command to the TGC file:<br>
<font color="blue"><tt>Set Code </tt></font> <font color="red"><tt>== </tt></font> <font color="black"><tt>0</tt></font> <font color="green"><tt>  ! Sets all cells to inactive</tt></font>
<li>Define active areas: <br>
:*<u>[[Draft_define_active_area | QGIS]]</u>
<li>Set all cells within the code polygon to active. The command needs to be written after the <font color="blue"><tt> Set Code </tt></font> <font color="red"><tt>== </tt></font> <font color="black"><tt>0 </tt></font> command to overwrite the inactive cells within the polygon: <br> 
<font color="blue"><tt>Read GIS Code </tt></font> <font color="red"><tt>== </tt></font> <font color="black"><tt>gis\2d_code_M01_001_R.shp</tt></font> <font color="green"><tt>  ! Sets cell codes according to attributes in the GIS layer</tt></font> <br>
</ol>
Note: As mentioned, the order of commands in the TGC is critical. The final cell value (such as for code, elevation or material) is specified by the file lowest in the TGC. Consider the above two commands to set active and inactive cells, if the <font color="blue"><tt>Read GIS Code </tt></font> was written before the <font color="blue"><tt>Set Code </tt></font> command, all the cells within the code polygon would be first set to active and then overwritten to be all inactive, no hydraulic simulation could occur.<br>

=== Topography ===
The points that assign elevations at each 2D cell centre, mid-side and corner are called Zpts. For a description on the computational function of each of the Zpts in a TUFLOW cell, see <u>[https://wiki.tuflow.com/index.php?title=Zpt_Description  Zpt Description]</u>. <br>

A DEM is used to assign elevations to the Zpts: <br>
<ol>
<li>Copy the DEM (both '''DEM.flt''' and '''DEM.hdr''') from the '''DEM''' folder into the '''Module_01\TUFLOW\model\grid''' folder.<br>
<li>Set a global elevation for the Zpts by adding the following line to the TGC file:<br>
<font color="blue"><tt>Set Zpts </tt></font> <font color="red"><tt>== </tt></font> <font color="black"><tt> 100</tt></font> <font color="green"><tt>  ! Sets every 2D elevation zpt to 100 metres</tt></font> <br>
<li>Assign elevations to the Zpts from the DEM. The command needs to be written after the <font color="blue"><tt> Set Zpts </tt></font> <font color="red"><tt>== </tt></font> <font color="black"><tt>100 </tt></font> command to overwrite global Zpts where the DEM data are available: <br> 
<font color="blue"><tt>Read GRID Zpts </tt></font> <font color="red"><tt>== </tt></font> <font color="black"><tt> grid\DEM.flt</tt></font> <font color="green"><tt>  ! Assigns the elevation of zpts from the grid</tt></font> <br>
</ol>
Note: The above data layering technique is common. After the first simulation, it is a good modelling practice to review the check files to confirm the topography in the model is as expected. Searching for a value of '100' is an easy way to identify if there are any gaps in the DEM dataset that were not expected (these should be fixed). <br>

=== Materials ===
Surface roughness or bed resistance values (e.g. Manning’s n) are assigned to material IDs. In order for TUFLOW to associate the Manning’s n to the Material ID, a TUFLOW materials file is required.  This can be either a text file format .tmf, or a .csv file. This tutorial model utilises the csv format.<br>
<ol>
<li>Copy the '''materials.csv''' file from the '''Module_01\Tutorial_Data''' folder into the '''Module_01\TUFLOW\model''' folder. As a minimum this file must contain two columns; the first being the Material ID (as specified in the GIS layer), and the second being the Manning’s n.  Additional data such as loss parameters and depth varying Manning's n values (applicable for direct rainfall modelling) are covered in later modules. <br>
<br>
[[File:Materials 02.png]]<br>
<br>
<li>Set a global material ID for all cells by adding the following line to the TGC file:<br>
<font color="blue"><tt>Set Mat </tt></font> <font color="red"><tt>== </tt></font> <font color="black"><tt>1</tt></font> <font color="green"><tt>  ! Sets all cells to a material ID of 1</tt></font><br>
<li>Define spatial material definition:
:*<u>[[Draft_mat_in_QGIS | QGIS]]</u>
<li>Assign materials from the GIS layer to overwrite the global material at all cells that fall within the material polygons: <br>
<font color="blue"><tt>Read GIS Mat </tt></font> <font color="red"><tt>== </tt></font> <font color="black"><tt>gis\2d_mat_M01_001_R.shp</tt></font> <font color="green"><tt>  ! Sets material values according to attributes in the GIS layer</tt></font><br>
<li>Save the TGC file.

</ol>
Note: As discussed in the previous sections, the order (layering) of these commands is important.<br>
<br>

= TUFLOW Boundary Control File (TBC) =
In this step the TBC and Boundary Condition Database (bc_dbase) are introduced. The TBC file contains information regarding the location of boundary conditions and internal links within the model. These include, but are not limited to: <br>

:*Upstream and downstream flow boundaries <br>
:*Downstream water level boundaries <br>
:*Water sources <br>
:*Direct rainfall
:*Infiltration <br>
:*1D/2D links <br>

=== Spatial Definition of Boundary Conditions ===
The following upstream and downstream boundaries are used in this tutorial: <br>

:*A flow vs time (QT) boundary and a source-area (SA) boundary is used for the inflows. <br>
:*A stage vs discharge (HQ) boundary is used for the outflow. <br>

Set up boundary condition layers: <br> 

:*<u>[[Draft_boundary_conditions | QGIS]]</u>

=== TUFLOW Boundary Control File (TBC) ===
The boundary condition layers are read into TUFLOW in a new text file, the TBC. <br>
<ol>
<li>Create a new text file and save as '''M01_001.tbc''' in the '''Module_01\TUFLOW\model''' folder. <br>
<li>Open the file in a text editor and add the boundary conditions: <br>
<font color="blue"><tt>Read GIS BC </tt></font> <font color="red"><tt>== </tt></font> <font color="black"><tt>gis\2d_bc_M01_001_L.shp</tt></font> <font color="green"><tt>  ! Reads in 2D boundaries</tt></font> <br>
<font color="blue"><tt>Read GIS SA </tt></font> <font color="red"><tt>== </tt></font> <font color="black"><tt>gis\2d_sa_M01_001_R.shp</tt></font> <font color="green"><tt>  ! Reads in 2D source area boundaries</tt></font> <br>
<li>Save the TBC.
</ol>
<br>

= TUFLOW Boundary Condition Database (bc_dbase) =
The bc_dbase is a comma delimited file with .csv extension. It can be opened in any spreadsheet software or a text editor.<br>
A hydrograph is associated with all of the upstream boundaries:<br>
<ol>
<li>Open the template bc database '''TUFLOW Tutorial Model BC Database.xlsx''' from the '''Module_01\Tutorial_Data''' folder. <br>
<li>There are two sheets in the file, 'bc_dbase' and '01p2hr'. Complete the bc_dbase worksheet. <br>
<li>Enter the name of the first upstream boundary condition under the 'Name' heading. The name must appear exactly as it does in the boundary condition layer, (i.e. FC01). <br>
<li>Enter the text '01p2hr.csv' under the 'Source' heading. It is a source file for TUFLOW to extract the timeseries data. <br>
<li>Enter the text 'time' and 'inflow_FC01' under the 'Column 1' and 'Column 2' heading. These correspond to the data headers in the source timeseries file. <br>
<li>Add FC02 data for use in a future tutorial.
<li>Repeat the above process for the boundary condition within the '''2d_sa_M01_001_R.shp''' layer (i.e. FC04, FC05, FC06 and FC07): <br>
<br>
[[File:M01 bc dbase 003.png]]<br>
<br>
<li>Switch to the '01p2hr' sheet, and review the provided hydrographs. Note: the 'Inflow_FC02' hydrograph is not used in this tutorial. <br>
<br>
[[File:M01 100y2hr 002.png]] <br>
<br>
<li>Save both of the sheets in a csv format that TUFLOW can read. In the '''Module_01\TUFLOW\bc_dbase''' directory, there should be two new files, '''bc_dbase.csv''' and '''01p2hr.csv'''. <br>
</ol>
<br>

= 2D Time Series Plot Output =
The 2D plot output (2d_po) objects allow for a wide range of hydraulic parameters to be output from the 2D domain as time-series data at pre-defined locations. <br>
:*<u>[[Time-Series_Plot_Output | QGIS]]</u><br>
<br>

= TUFLOW Control File (TCF) =
The TCF file references all the control files, specifies time and output controls. This is the last step before running the simulation.<br>
<ol>
<li>Open '''Create_Empties.tcf''' in a text editor from the '''Module_01\TUFLOW\runs''' folder and save a copy as '''M01_5m_001.tcf'''. <br><br>

<li>Comment out (or delete) the 'Write Empty GIS Files' line, using a comment character (!): <br>

<font color="green"><tt>! MODEL INITIALISATION</tt></font><br>
<font color="blue"><tt>Tutorial Model</tt></font> <font color="red"><tt>== </tt></font> <font color="black"><tt> ON</tt></font> <font color="green"><tt>  ! Required command to run this tutorial model licence free </tt></font> <br>
<font color="blue"><tt>GIS Format</tt></font> <font color="red"><tt>== </tt></font> <font color="black"><tt> SHP</tt></font> <font color="green"><tt>  ! Specify SHP as the output format for all GIS files</tt></font> <br>
<font color="blue"><tt>SHP Projection</tt></font> <font color="red"><tt>== </tt></font> <font color="black"><tt> ..\model\gis\Projection.prj </tt></font> <font color="green"><tt>  ! Sets the GIS projection for the TUFLOW Model </tt></font> <br>
<font color="green"><tt>! Write Empty GIS Files == ..\model\gis\empty  ! Creates template GIS layers, commented out as files were already created</tt></font> <br><br>

<li> Define the solution scheme and specify Sub-Grid Sampling (SGS) commands: <br>
<font color="green"><tt>! SOLUTION SCHEME</tt></font> <br>
<font color="blue"><tt>Solution Scheme </tt></font> <font color="red"><tt>== </tt></font> <font color="black"><tt> HPC</tt></font> <font color="green"><tt>  ! Heavily Parallelised Compute, uses adaptive timestepping</tt></font> <br>
<font color="blue"><tt>Hardware </tt></font> <font color="red"><tt>== </tt></font> <font color="black"><tt> GPU</tt></font> <font color="green"><tt>  ! Comment out if GPU card is not available or replace with "Hardware == CPU" </tt></font> <br>
<font color="blue"><tt>SGS </tt></font> <font color="red"><tt>== </tt></font> <font color="black"><tt> ON</tt></font> <font color="green"><tt>  ! Switches on Sub-Grid Sampling</tt></font> <br>
<font color="blue"><tt>SGS Sample Frequency</tt></font> <font color="red"><tt>== </tt></font> <font color="black"><tt> 11</tt></font> <font color="green"><tt>  ! Sets SGS Sample Frequency to 11</tt></font> <br>
<font color="blue"><tt>SGS Approach</tt></font> <font color="red"><tt>== </tt></font> <font color="black"><tt> Method C</tt></font> <font color="green"><tt>  ! Sets SGS Sample Approach to Method C</tt></font> <br>
For information on SGS, see Section 3.2 of the latest <u>[https://downloads.tuflow.com/TUFLOW/Releases/2020-10/TUFLOW%20Release%20Notes.2020-10-AD.pdf Release Notes])</u>
<br><br>


<li> Update the model inputs section. These commands reference the TGC, TBC, bc_dbase and materials file created in the above steps:<br>
<font color="green"><tt>! MODEL INPUTS</tt></font> <br>
<font color="blue"><tt>Geometry Control File </tt></font> <font color="red"><tt>== </tt></font> <font color="black"><tt>..\model\M01_001.tgc</tt></font> <font color="green"><tt>  ! Reference the TUFLOW Geometry Control File</tt></font> <br>
<font color="blue"><tt>BC Control File </tt></font> <font color="red"><tt>== </tt></font> <font color="black"><tt> ..\model\M01_001.tbc</tt></font> <font color="green"><tt>  ! Reference the TUFLOW Boundary Conditions Control File</tt></font> <br>
<font color="blue"><tt>BC Database </tt></font> <font color="red"><tt>== </tt></font> <font color="black"><tt> ..\bc_dbase\bc_dbase.csv</tt></font> <font color="green"><tt>  ! Reference the Boundary Conditions Database</tt></font> <br>
<font color="blue"><tt>Read Materials File </tt></font> <font color="red"><tt>== </tt></font> <font color="black"><tt>..\model\materials.csv</tt></font> <font color="green"><tt>  ! Reference the Materials Definition File</tt></font> <br><br>

<li>Add the following time control commands: <br> 
<font color="green"><tt>! TIME CONTROL</tt></font> <br>
<font color="blue"><tt>Timestep </tt></font> <font color="red"><tt>== </tt></font> <font color="black"><tt> 1</tt></font> <font color="green"><tt>  ! Specifies the first 2D computational timestep of 1 second</tt></font> <br>
<font color="blue"><tt>Start Time </tt></font> <font color="red"><tt>== </tt></font> <font color="black"><tt> 0</tt></font> <font color="green"><tt>  ! Specifies a simulation start time of 0 hours</tt></font> <br>
<font color="blue"><tt>End Time </tt></font> <font color="red"><tt>== </tt></font> <font color="black"><tt> 3</tt></font> <font color="green"><tt>  ! ! Specifies a simulation end time of 3 hours</tt></font> <br><br>
<li>Add the following output folder commands: <br> 
<font color="green"><tt>! OUTPUT FOLDERS</tt></font> <br>
<font color="blue"><tt>Log Folder </tt></font> <font color="red"><tt>== </tt></font> <font color="black"><tt> log</tt></font> <font color="green"><tt>  ! Location of the log output files (e.g. .tlf and _messages files)</tt></font> <br>
<font color="blue"><tt>Output Folder </tt></font> <font color="red"><tt>== </tt></font> <font color="black"><tt> ..\results\</tt></font> <font color="green"><tt>  ! Location of the 2D output files and prefixes them with the .tcf filename</tt></font> <br>
<font color="blue"><tt>Write Check Files </tt></font> <font color="red"><tt>== </tt></font> <font color="black"><tt> ..\check\</tt></font> <font color="green"><tt>  ! Location of the 2D check files and prefixes them with the .tcf filename</tt></font> <br><br>
<li>Add the following output settings commands: <br> 
<font color="green"><tt>! OUTPUT SETTINGS</tt></font> <br>
<font color="blue"><tt>Map Output Format </tt></font> <font color="red"><tt>== </tt></font> <font color="black"><tt> XMDF FLT</tt></font> <font color="green"><tt>  ! Result file types</tt></font> <br>
<font color="blue"><tt>Map Output Data Types </tt></font> <font color="red"><tt>== </tt></font> <font color="black"><tt> h V d dt</tt></font> <font color="green"><tt>  ! Outputs water levels, velocities, depths, minimum timestep</tt></font> <br>
<font color="blue"><tt>Map Output Interval </tt></font> <font color="red"><tt>== </tt></font> <font color="black"><tt> 300</tt></font> <font color="green"><tt>  ! Outputs map data every 300 seconds (5 minutes)</tt></font> <br>
<font color="blue"><tt>FLT Map Output Interval </tt></font> <font color="red"><tt>== </tt></font> <font color="black"><tt> 0</tt></font> <font color="green"><tt>  ! Outputs only maximums for grids</tt></font> <br>
<font color="blue"><tt>SGS Map Extent Trim </tt></font> <font color="red"><tt>== </tt></font> <font color="black"><tt> ALL</tt></font> <font color="green"><tt>  ! Specifies partially wet cells as dry</tt></font> <br>
<font color="blue"><tt>SGS Depth Output </tt></font> <font color="red"><tt>== </tt></font> <font color="black"><tt> Cell Average</tt></font> <font color="green"><tt>  ! Specifies cell average depth output</tt></font> <br><br>

<li>Reference the 2d_po layers. When reading in time-series layers, such as 2d_po files, its necessary to use a <font color="blue"><tt>Time Series Output Interval </tt></font> command. This command specifies the output interval in seconds for the time-series based output: <br>
<font color="green"><tt>! TIME SERIES PLOT OUTPUT</tt></font> <br>
<font color="blue"><tt>Read GIS PO </tt></font> <font color="red"><tt>== </tt></font> <font color="black"><tt> ..\model\gis\2d_po_M01_001_L.shp</tt></font> <font color="green"><tt>  ! Reads in plot output line</tt></font> <br>
<font color="blue"><tt>Read GIS PO </tt></font> <font color="red"><tt>== </tt></font> <font color="black"><tt> ..\model\gis\2d_po_M01_001_P.shp</tt></font> <font color="green"><tt>  ! Reads in plot output point</tt></font> <br>
<font color="blue"><tt>Time Series Output Interval </tt></font> <font color="red"><tt>== </tt></font> <font color="black"><tt> 60</tt></font> <font color="green"><tt>  ! Outputs time series data every 60 seconds</tt></font> <br><br>

<li>Save the TCF file. The TUFLOW simulation is ready to be run for the first time.
</ol>
The comments (following the exclamation marks) are not required and these commands are generally self-explanatory. However, for this tutorial model they are included to clarify the purpose of each line. <br>
<br>

= Running the Simulation =
Set up a simple batch file (.bat) to run TUFLOW. This approach calls the TUFLOW executable file (.exe) and runs the TCF file.
<ol>
<li>Create a new text file in the '''Module_01\TUFLOW\runs''' folder and save as '''_run_M01_HPC.bat'''. 
<li>Open the '''_run_M01_HPC.bat''' in a text editor and include a file path to the executable from the '''exe\2020-10-AD''' folder and the TCF name: <br>
<font color="black"><tt>"..\..\..\exe\2020-10-AD\TUFLOW_iSP_w64.exe" M01_5m_001.tcf</tt></font> <br>
Note: A relative path is used for the executable and the TCF, full file path can also be used.
<li>Save the batch file and double click it in file explorer to run the simulation. 
</ol>
This opens the TUFLOW DOS console window and the simulation begins running. The simulation usually takes a few minutes to process (depending on the computer hardware). While the model is running, it is a good practise to fill out a modelling log. It includes developer notes keeping a record of TUFLOW simulations and changes from one version to the next, for more information see <u>[https://wiki.tuflow.com/index.php?title=TUFLOW_Modelling_Log here]</u>. A template is included in the '''Module_01\Tutorial_Data''' folder.<br>
If the simulation is successful, the console window should look like the image below.
<ol>
<br>
[[File:Simulation_Finished_2.png]]<br>
<br>
</ol>If the model did not finish running, work though the troubleshooting steps:
:*<u>[[Draft_Troubleshooting | Troubleshooting]]</u>
<br>

= Check Files =
TUFLOW writes a series of check files during the model initialisation process when the <font color="blue"><tt>Write Check Files </tt></font> command is specified in the TCF. The files are either in a tabular form (.csv) or GIS (.shp, .mif) and contain information on the input data processed by TUFLOW.<br>
While the model is running, review the added features are specified correctly: <br>

:*<u>[[Draft_M01_check_files | QGIS]]</u>
<br>

= Results=
Two map output formats specified for this tutorial:
:*FLT - Grid based output format writing map output data types separately; and
:*XMDF - Mesh based output format containing all map output data types in a single file.
When the model is finished, review the results: <br>
:*<u>[[Draft_viewing_results_M01 | QGIS]]</u>
<br>

= Reviewing Model Performance =
There are a number of useful outputs from TUFLOW for reviewing the model performance.<br>
=== TUFLOW Log File ===
The first place to look is in the TUFLOW Log File (TLF). The <font color="blue"><tt>Log Folder </tt></font> <font color="red"><tt>== </tt></font> <font color="black"><tt> log</tt></font> command in the TCF controls where the log file is written. <br>
Navigate to the '''Module_01\TUFLOW\runs\log''' folder and open the '''M01_5m_001.tlf''' file in a text editor. Scroll down to the bottom to 'Simulation Summary'. This includes information about the computation time, messages, volume calculations and mass error. <br>
<ol>
<br>
[[File:Simulation Summary 02.PNG]]<br>
<br>
</ol>

=== HPC TUFLOW Log File ===
As the model is using the HPC solution scheme, there is a second log file automatically written from the same command. Navigate to the '''Module_01\TUFLOW\runs\log''' folder and open the '''M01_5m_001.hpc.tlf''' file. The HPC solution scheme, by default, uses adaptive timestepping to progress through the simulation. The timestep is adjusted so it complies with the mathematical stability criteria of a 2D SWE explicit solution. This is controlled by three control numbers, further information is provided <u>[https://wiki.tuflow.com/index.php?title=HPC_Adaptive_Timestepping  here]</u>. <br>
Scroll down the '''hpc.tlf''' to 'iStep'. This is the point at which the model successfully compiled and began running. The three HPC control numbers are listed in the columns after time. Then the number of wet cells, the volume of water, the dt (minimum timestep) and the efficiency of the solver. As the model starts to gain wet cells dt drops, but should eventually stabilise. Similarly, model efficiency should increase as the model progresses.<br>
<br>
<ol>
[[File:Simulation HPC.PNG]]<br>
</ol>
<br>

=== Other Model Performance Indicators ===
For more information on how to review HPC models, see <u>[[HPC_Model_Review | HPC Model Review]]</u>.<br>
<br>

= Conclusion = 
:*Simple 2D TUFLOW model was created with required GIS and text based inputs.
:*Check files were used to review the model setup.
:*Results were visualised and the performance of the model reviewed. <br> 
<br>

= Troubleshooting = 
When running a TUFLOW model, error messages might be triggered and the simulation might pause or fail. These are shown in the DOS console window, messages layer and the .tlf files. Double click the hyperlink associated with the message in the .tlf file to open a Wiki page with description of the message and suggestions on how to solve it. If the issue is not detailed on the wiki pages, email [mailto:support@tuflow.com support@tuflow.com]. <br>
<br>

= Increasing Model Resolution (Optional) =
This section includes an optional exercise to reduce the cell size from 5m to 2.5m. Consider the impact this has on the model results and the runtime.<br>
To reduce the cell size in the model: <br>
<ol>
<li>Save the TUFLOW control file '''M01_5m_001.tcf''' as '''M01_2.5m_001.tcf'''. 
<li>Save the geometry control file '''M01_001.tgc''' as '''M01_2.5m_001.tgc'''. 
<li>Modify the cell size in the geometry control file to '2.5' meters.
<li>In the TCF, change the SGS Sample Frequency to '5' and update the reference to the new TGC.
<li>Update the batch file with the updated TCF file and run the simulation. 
<br></ol>
<br>
{{Tips Navigation
|uplink=[[Draft_Tutorial_Introduction| Back to Tutorial Introduction Main Page]]
}}