Tutorial Module04 Archive: Difference between revisions

A 1D model requires cross-sections for processing of the channel geometry. There are a number of different formats for cross-sections to be input to TUFLOW. In this module we will be using an offset-elevation approach (XZ). This is a typical format for inputting cross-sections however, other options include height-width (HW) and MIKE11 format inputs. These are not covered in this tutorial, however the general process is very similar. To save time, the locations and XZ profiles for the 1D cross sections are provided. The XZ profiles were automatically extracted from the DEM triangulation using the 12D software (www.12d.com) with the aid of the TUFLOW utility 12da_to_from_mif12da_to_from_GIS.exe using the -xs option (see [[12da_to_from_mif12da_to_from_GIS | 12da_to_from_mif12da_to_from_GIS wiki page]]). The SMS TUFLOW interface has a similar and easier process, noting that a licence for the SMS TUFLOW interface is required to save the cross-sections. It is more common for this information to come from surveyed cross-sections. If the survey has been provided as x-y-z points, or a a GIS layer of points, the xs_Generator utility can be used to create the cross-sections in a TUFLOW format. The xs_Generator utility is described in the [[XsGenerator |XsGenerator wiki page]].<br>

Now that we have looked at the cross section data, we must add 1D channels for the 1D network. In TUFLOW, cross sections can either be located at the ends of each channel reach, or at some point along the reach. The way that TUFLOW uses the cross-section depends upon the location, for example a "centre" cross-section has a higher priority than "end" sections if both "End" and "Centre" sections are defined. For more information on the 1D topography, youplease are encouragedrefer to readthe Section 4<u>[https://docs.6 of the 2010tuflow.com/classic-hpc/manual/latest/ TUFLOW manualManual]</u>.<br>

In this section we define lines where there is flow exchange between the 1D and 2D components of the model. At first it may seem slightly complicated, but it is actually very logical and the method allows the user to change the 2D cell size and orientation at a later stage without having to change the 1D/2D linking. Before we begin creating the link we will spend a bit of time describing how the link works. More details on the 1D/2D link can be found in Sectionthe 4<u>[https://docs.10tuflow.5 of the 2010com/classic-hpc/manual/latest/ TUFLOW manualManual]</u>.<br>

<li>Depending on the speed of your computer, you may have noticed in the previous three modules that when TUFLOW is running, it is hard to read the TUFLOW console output because it updates too quickly. We can reduce the frequency of output to the DOSconsole screenwindow and also the TUFLOW Log File (.tlf). Include the following command at the end of the .tcf with the other output commands:<br>

Using your preferred method for starting TUFLOW, run the recently created '''M04_5m_001.tcf'''. Please refer to <u>[[Tutorial_Module01_Archive#Running_TUFLOWRun_Simulation | moduleModule 1]]</u> for a detailed description of the various methods for running a TUFLOW simulation.<br>

If you look at the 1D results (by importing the time series (_TS.mif or _TS_P.shp from the 1D results folder, or opening the M04_5m_001_1d_Q.csv) the 1D channels are conveying flow. In order to get map output for the 1D we need to use Water Level Line (WLL) inputs. The underlying water level from the 1D model is displayed across this line and as such it should be digitised perpendicular to flow. The theory behind water level lines and their use is detailed in the Water Level Lines section of the<u>[https://docs.tuflow.com/classic-hpc/manual/latest/ TUFLOW Manual]</u>. <br>

This section contains links to some possible problems that may occur when progressing through the fourth tutorial module. If you experience an issue that is not detailed, please email [mailto:support@tuflow.com or add and describe the problem on the <u>[[Talk%3ATutorial_Module04_Archive | discussion pagesupport@tuflow.com]]</u>.<br>

*[[Only_TUFLOW_DOS_Window_ArchiveOnly_TUFLOW_Console_Window_Archive | Why does the TUFLOW DOSconsole Windowwindow open, though the TCF isn’t read and the simulation doesn’t execute?]]

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.

* Check the simulation logs in the DOSconsole window, .tlf and .hpc.tlf log files.