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>

<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>

*[[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?]]

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