Tutorial Module04 Archive: Difference between revisions
Content deleted Content added
No edit summary |
|||
| (4 intermediate revisions by 3 users not shown) | |||
Line 29:
As with Modules 2 and 3 the GIS inputs are demonstrated in ArcGIS, MapInfo, SMS and QGIS. At each stage please select your GIS package for instructions.
==1D Cross-Sections==
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
<br>
For each cross-section there is an individual comma separated variable (.csv) file. The 1d_xs layer contains a link to the source .csv file at every cross-section location. <br>
Line 149:
<li>After this command in the .tcf, add the following command to link the new 1D control file:</li>
<font color="blue"><tt>ESTRY Control File </tt></font> <font color="red"><tt>== </tt></font> <tt>..\model\M04_1d_001.ecf</tt><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
<font color="blue"><tt>Screen/Log Display Interval </tt></font> <font color="red"><tt>== </tt></font> <tt>40</tt><br>
TUFLOW will write the output every 40 timesteps. For the 1.5 second timestep this means we will get output every 60 seconds of simulation time.<br>
Line 281:
If the TUFLOW simulation fails to start TUFLOW will output the error in a number of locations. Firstly, check the Console Window or the TUFLOW Log File (.tlf) (located in the '''TUFLOW\runs\log\''' folder with the name '''M04_5m_001.tlf'''). This file can be opened in a text editor and the error is generally located at the end of the file. You can however search for "Error" if you can not see the error. In most cases there is also a spatial location for the error message (if the error reported in the log file is prefixed by XY:). To check the location of the geographic errors, open the '''M04_5m_001_messages.mif''' or '''M04_5m_001_messages_P.shp''' file in your GIS package.<br>
<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
*[[Save_Date_Error_Archive|Save date of .tab file is later than .mif or .mid]]
Line 288:
*[[TUFLOW_Message_2060 | Error 2060 - Could not find a CN connection snapped to the end of HX line]]
*[[TUFLOW_Message_2024 | Error 2024 - Could not find a 1D node snapped to CN line.]]
*[[
= 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).
Line 309:
==Results==
Using the methods described above in the <u>[[Tutorial_Module01_Archive#Viewing_Results | Viewing Results]]</u> section of Module 1.
* Check the simulation logs in the
* View the results in your preferred package.
Do the logs and results appear different to the TUFLOW Classic simulation?
| |||