Tutorial Module04 Archive: Difference between revisions
Content deleted Content added
No edit summary |
|||
| (11 intermediate revisions by 4 users not shown) | |||
Line 1:
<ol>
=Introduction=
As discussed in Module 1 (<u>[[Tutorial_Module01_Archive#Reviewing_Model_Performance |
[[file:Poor_2d_rep.png|400px]]<br>
Using a cell size that is coarse relative to the width of the creek channel may reduce the accuracy of the computed conveyance in the channel and introduce a source of mass error to the model. There are two options for improving the representation of the creek channel:<br>
* decrease the width of the 2D cells; and/or
* model the channel as a 1D network, dynamically linked to the 2D domain (the floodplain).
In the optional section of module 1 (<u>[[Tutorial_Module01_Archive#Advanced_-_Model_Resolution_.28Optional.29 |
Setting up a 1D/2D model where the 1D channel cuts through the 2D domain is probably the most time-consuming type of a TUFLOW model to setup. However, the reduction in simulation time can be beneficial and make this a good approach. For this module, most of the time consuming data entry tasks have been undertaken, so you can progress through the module in a relatively short period of time. However, throughout the tutorial we will provide guidance on making this process as efficient as possible should you have to start from scratch.<br>
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>
For <u>'''SMS'''</u> Users
:* [[
For <u>'''ArcGIS, MapInfo and QGIS'''</u> Users
<ol>
Line 40:
<li> Interrogate one of the cross-section lines to inspect the attributes. Notice that each line has a unique name as shown in the '''Source''' attribute, e.g. FC01 ch0834.csv. This name describes the cross section as belonging to channel FC01 at chainage 0834. The '''Type''' attribute "XZ" indicates that this cross-section is an offset-elevation type section.</li>
<li> In the GIS platform a "hotlink" can be created to allow the user to open the .csv file in excel, allowing the user to easily visualise the section using an XY scatter chart type. To enable hotlinking select your GIS platform below:
* [[
* [[
* [[
</ol>
''Tip: The XY scatter plot can be setup as the default chart type in excel, this makes it simple to plot the cross-sections, simply open the .csv in Excel using the GIS hotlink functionality, select the data and the hit the F11 key to create a chart. Instructions for setting an x-y scatter as the default chart type can be found in this [[EXCEL_setting_default_chart | Excel tip]].<br>
''For MapInfo users with the miTools utility, the cross-sections can be viewed directly within MapInfo, instructions for doing so are in the [[
''Users with the SMS-TUFLOW interface can also directly view the cross-sections in the [[
==1D Channels==
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,
<br>
For this tutorial, we will locate most of the cross-sections at the ends of channels. There are a number of locations where a "centre" section will be used. The final channel will be a weir type channel; this represents a weir with a known stage-discharge curve. In later modules we will also use "centre" cross sections for the modelling of structures.<br>
Line 57:
<br>
As the cross sections have been provided, the digitisation of the channel is simply a matter of joining the dots. We are going to create a series of lines between the cross sections. It is important that the end of each channel snaps to a vertex along the cross-section line, so we will be using the snapping tools in the GIS. We have provided a 1d_nwk_M04_creek_001 GIS layer. This layer has the first few channels digitised for you. A revised culvert layer '''1d_nwk_M04_creek_001''' is also provided, this has the culverts connected to the new channels layer. The creation of the 1d network layers is described for the GIS packages below:
*[[
*[[
*[[
*[[
==1D/2D Links==
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
<br>
'''Description of linking concept'''<br>
Line 84:
<br>
Now that we have a background in the linking approach it is time to define the 1D/2D link. This process is described for the various GIS packages in the links below:
*[[
*[[
*[[
*[[
==2D Breaklines==
Line 96:
<br><br>
To include breaklines for the top of bank, follow the instructions outlined in your GIS package below.
*[[
*[[
*[[
*SMS: SMS automatically extracts elevations for the HX lines when we export the TUFLOW files. Please proceed to the next section.
Line 105:
<br>
As the HX line was created along the top of bank and was as wide as the cross-sections, we can snap the code polygon (which deactivates the 2D cells) to the HX line. To do this please select your GIS package from the list below:
*[[
*[[
*[[
*[[
==Define Boundary Conditions==
Line 117:
<br>
For the GIS changes please select your GIS package from the list below.
* [[
* [[
* [[
* [[
=Modify Simulation Control Files=
Now that we have made all of the necessary changes to the GIS layers, we need to update our control files to utilise the new GIS layers. Now that the 1D component of the model is becoming more complex we are going to use a separate control file for the 1D inputs. The new 1D control file will have the extension .ecf, this stands for <u>'''E'''</u>STRY <u>'''C'''</u>ontrol <u>'''F'''</u>ile. ESTRY was a 1D hydraulic modelling package before TUFLOW was created. The functionality of ESTRY has been incorporated in TUFLOW but for historic reasons the 1D control file is still referred to as the ESTRY Control File and has the .ecf file extension.<br>
'''SMS''' users do not need to modify the control files manually because SMS writes out the control cards and files automatically while exporting the TUFLOW project. Please proceed to ''[[
==TUFLOW Control File (TCF)==
<ol>
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 155:
</ol>
==ESTRY Control File (ECF)==
'''SMS''' users do not need to modify the control files manually because the control cards/files are automatically generated by SMS while exporting TUFLOW files. Follow ''[[
For all other model development platforms (eg. ArcGIS, QGIS, MapInfo etc.)<br>
Line 235:
=Run the Simulation=
Using your preferred method for starting TUFLOW, run the recently created '''M04_5m_001.tcf'''. Please refer to <u>[[Tutorial_Module01_Archive#
If the model fails to start correctly please refer to the <u>[[Tutorial_Module04_Archive#Troubleshooting |troubleshooting section]]</u> at the end of this page.<br>
Line 258:
[[File:Tute M04 results no 1d 02.jpg|500px]]
<br><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
<li> For the purpose of this tutorial the 1D_WLL GIS inputs have been provided for you.<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
*[[
*[[
*[[
*[[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?
| |||