Tuflow

Tutorial Module01 Archive: Difference between revisions

Browse history interactively
← Older edit
Content deleted Content added
VisualWikitext
No edit summary
No edit summary
 
(16 intermediate revisions by 5 users not shown)
Line 31:
 
<ol>
<li>Set up the model directory and sub-directories as recommended in the list below (for a more detailed description , please seerefer the Folders and Filepath Section ofto the <u>[httphttps://wwwdocs.tuflow.com/Tuflow%20Documentation.aspx|classic-hpc/manual/latest/ TUFLOW User Manual])</u>). Alternatively, you can copy the TUFLOW folder and all sub-folders from the TUFLOW Folders Template folder in the supplied files to a local drive on your computer.<br>
''* If using 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>).
<br>
Line 108:
 
=== Run TUFLOW to Create Empty (Template) GIS Files===
We now need to run TUFLOW using the TUFLOW Control File (TCF). There are a number of ways TUFLOW can be setup to run. In each case the TUFLOW executable is started with the TCF as the input. For more information on running TUFLOW please refer to the ''Managing and Starting Simulations'' section of the <u>[httphttps://wwwdocs.tuflow.com/Tuflow%20Documentation.aspx|classic-hpc/manual/latest/ TUFLOW User Manual]</u>. The most common ways are outlined below. We will be using a batch file for this tutorial, however any of the methods below will work.
 
<ol>
Line 120:
<br>
<li> Start TUFLOW from a batch file using the TCF file we have created ('''M01_5m_001.tcf'''). Follow the steps outlined in, <u>[[Run TUFLOW From a Batch-file | Running TUFLOW from a Batch-file]]</u> to create the batch file.
<li> Double click the created batch file (.bat) from Windows Explorer to execute the simulation. A console (DOS) window should appear as shown below:<br>
[[File:Tute M01 DOS Empties.png|frame|none]]
<br>
Line 169:
=== Define Elevations ===
In the previous section, the extent and dimensions of the 2D domain were defined. We now need to assign elevations at each 2D cell centre, mid-side and corner. These points are known as Zpts.<br>
Knowledge of 2D domain geometry is fundamental to understanding how TUFLOW works. A brief description on the computational function of each of the Zpts in a TUFLOW cell is given in the <u>[[Zpt_Description | Zpt Description]]</u> page. It is also highly recommended to read the ''2D Model domain Schematisation'' Section of the <u>[http://www.tuflow.com/Tuflow%20Documentation.aspx|TUFLOW User Manual]</u>.<br>
<br>
There are two methods to assign the elevations to the Zpts. The first is to directly input the elevation model into TUFLOW as either a TIN or gridded DEM dataset. TUFLOW will assign the elevations from the elevation dataset to Zpts within the DEM / TIN. This offers the following benefits:<br>
Line 194:
 
* <u>[[Tute_M01_Active_Areas_MI_Archive|Define active area in Mapinfo]]</u>
* <u>[[Tute_M01_Active_Areas_Arc_ArchiveTUFLOWTute_M01_Active_Areas_ArcTUFLOW_Archive|Define active area in ArcGIS (arcTUFLOW)]]</u>
* <u>[[Tute_M01_Active_Areas_QGIS_Archive|Define active area in QGIS]]</u>
* <u>[[Tute_M01_Active_Areas_SMS_Archive|Define active area in SMS]]</u>
Line 388:
Open and view the TUFLOW results in your viewing package, for instructions on this please select your results package below.<br>
*<u>[[View_Results_in_SMS_10.11_Archive|SMS 10.1]]</u>
*<u>[[View_Results_in_SMS_11.11_Archive|SMS 11.1]]</u>
*<u>[[View_Results_in_MapInfoView_Results_in_MapInfo_Archive|MapInfo]]</u>
*<u>[[View_Results_in_ArcGISView_Results_in_ArcGIS_Archive|ArcGIS]]</u>
*<u>[[View_Results_in_QGIS_with_the_TUFLOW_ViewerView_Results_in_QGIS_with_the_TUFLOW_Viewer_Archive|QGIS using TUFLOW plugin]]</u>
*<u>[[View_Results_in_QGISView_Results_in_QGIS_Archive|QGIS using raster and shapefiles]]</u>
 
== Reviewing Model Performance ==
Line 409:
 
=== TUFLOW Log file ===
The first place to look is at the final output in the DOSconsole window. If you missed this, for example if the model was run in batch mode this information is contained in the TUFLOW Log File (.tlf). Earlier on we add the following command to the TCF:<br>
<font color="blue"><tt>Log Folder </tt></font> <font color="red"><tt>==</tt></font> <tt>Log</tt><br>
 
Line 463:
 
=== TUFLOW Messages Layers ===
TUFLOW writes a number of messages, in increasing order of severity these are: Check --> Warning --> Error. Each of the messages generated by TUFLOW has a four digit ID code. A description of each of these messages is given in the message database section of this wiki: <u>[[TUFLOW_Message_How_ToTUFLOW_Messages | (TUFLOW Messages Database)]]</u>.
When a numerical model such as TUFLOW struggles to converge to a solution, spurious results such as negative depths can be generated. When this occurs TUFLOW creates a warning and writes this to the _messages.csv file and also to a GIS file. This can be opened in excel, or your GIS package.
<ol>
Line 496:
 
== Conclusion ==
To conclude, in this module we have created a 2D TUFLOW model. We have setup the required GIS and text based inputs and ran the simulation. We have visualised the results and reviewed the performance of the model.<br>
 
The model results, depths and velocity outputs look sensible. However, the model has a slight issue with mass balance, which appears in the main channel areas. This is most likely caused by the inadequate representation of the creek with the cell size adopted in the tutorial model. This cell size has been chosen to allow the model to be simulated quickly on most computers.<br>
 
In Module 3 we will model the creek area as an embedded 1D open channel, this should minimise the mass area noted in this tutorial. Reducing the cell size also allows for a better representation of the channel in the 2D model.<br>
 
See the <u>[[Tutorial_Module01_Archive#Advanced_-_Model_Resolution_.28Optional.29 |Optional Section]]</u> below, in which we look at halving the cell size and the effect this has on the model results and simulation time.
 
Whilst reviewing the results, you may have noticed that the water was being held behind these road embankments (which were essentially acting as dams in the model. We will embed 1D culverts through the road embankments in <u>[[Tutorial_Module02_Archive |Module 2]]</u>. This will introduce the 1D control files and linking of the 1D model to the 2D.
 
==Troubleshooting==
This section contains links to some common issues that may occur when progressing through the first module of the TUFLOW tutorial model. If you experience an issue that is not detailed on here please either send an email to [mailto:support@tuflow.com support@tuflow.com].<br>
 
*<u>[[Save_Date_ErrorSave_Date_Error_Archive|Save date of .tab file is later than .mif or .mid]]</u><br>
*<u>[[Tutorial_Troubleshoot_2014|ERROR 2014 - No active cells within SA inflow polygon]]</u>
*<u>[[Only_TUFLOW_DOS_WindowOnly_TUFLOW_Console_Window_Archive | Why does the TUFLOW DOSconsole Windowwindow open, though the TCF isn’t read and the simulation doesn’t execute?]]</u>
 
== Advanced - Model Resolution (Optional) ==
Line 533:
<br>
===Results===
Using the methods described above <u>[[Tutorial_Module01_Archive#Viewing_the_ResultsViewing_Results | hereabove]]</u>, view the results in your preferred package. Do the results appear different? Is the increase in simulation time justified?
 
[[File:Tute M01 2p5m results SMS.png|450px]]
Line 554:
The model performs better with a smaller cell size, as the 5m resolution is a bit too coarse for representing the narrow in-bank flowpath in a 2D manner. In Module 3 we will overcome this issue by modelling the creek using a 1D model, which will be dynamically linked with the 2D model.<br>
<br>
It is worth noting the increase in runtime, by halving the cell size by a factor of 2, we have four times as many cells (each 5m x 5m cell is now four 2.5m x 2.5m cells), we also needed to reduce the timestep, as the Courant number is directly related to cell size (refer to the <u>[https://docs.tuflow.com/classic-hpc/manual/latest/ TUFLOW manualManual]</u>) this would normally be reduced by a factor 2 as well. This translates to an approximate increase in runtime of 8 (four times the number of cells and half the timestep). Choosing an appropriate cell size that allows representation of the hydraulics whilst resulting in realistic run times is an important part of the modelling process. With some planning you should be able to avoid a model that requires excessive run times!<br>
<br>
The following Wiki page gives some guidance on <u>[[Estimating_Runtimes | estimating model runtimes]]</u> based on the model area and cell size.
 
== Advanced - HPC Solver (Optional) ==
This section will introduce how to run the model TUFLOW’s HPC (Heavily Parallelised Compute) solver, and how to fix some common issues that may occur when trying to run a simulation using Graphics Processing Unit (GPU) hardware. Please see [[HPC_Features_Archive | HPC Features Archive]] for more information on TUFLOW HPC features supported in the 2017 release.
 
TUFLOW HPC can run between 10 and 100 times faster than TUFLOW Classic using NVidia Graphics Processing Units (GPU)(depending on the model configuration and hardware performance). <br><br>
Line 582:
===Results===
Using the methods described above in the <u>[[Tutorial_Module01_Archive#Viewing_Results | Viewing Results]]</u> section.
* Check the simulation logs in the DOSconsole window, .tlf and .hpc.tlf log files.
* View the results in your preferred package.
Do the logs and results appear different? Did the simulation run faster using the GPU hardware? For more information about computer hardware and simulation speed, please refer to the <u>[[Hardware_Benchmarking | Hardware Benchmarking Page]]</u>.
Line 601:
</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>
Retrieved from "https://wiki.tuflow.com/Tutorial_Module01_Archive"