QGIS ARR to TUFLOW: Difference between revisions
Content deleted Content added
Ellis Symons (talk | contribs) |
Ellis Symons (talk | contribs) |
||
Line 81:
====Output====
The tool produced the following outputs:<br>
[[File: ARR_example_output_folder.PNG |
[[File: ARR_example_output_folder_data.PNG |
[[File: ARR_example_output_folder_rf_inflow.PNG |
====Log File====
The following warning was found in the log file:<br>
* WARNING: 102 preburst rainfall depths exceeded storm initial loss (50.2% of entries)
<br>
This is can be checked by looking at the '''burst_initial_loss.csv''' and '''burst_initial_loss.png'''<br>
[[File: ARR_Burst_Initial_Losses_plot.png | 500px]]
<br>
The plot above confirms the warning - a significant portion of the initial loss values are negative. This warning should be taken seriously and ARR offers a number of ways to proceed in Book 2, Section 5.9.9. The tool itself also offers support for modelling a complete storm. For the purpose of this example and simplicity, the model will be assumed to be insensitive to initial loss and negative values will be changed to 0 mm.<br><br>
====TUFLOW Setup====
The following is an example of how the output files are all pieced together and read into TUFLOW. The examples aren't complete control file examples, but rather show the commands to be inserted into each control file with a brief explanation on what's going on.<br><br>
1. Starting with the spatial distribution of the rainfall losses which is defined in the '''Geometry Control File (TGC)'''.<br>
'''''Geometry Control File'''''
<span style="color:blue;">Set Soil</span> <span style="color:red;">==</span> 1 <span style="color:green;">! globally set all active cells to soil type 1</span>
<span style="color:blue;">Read GIS Soil</span> <span style="color:red;">==</span> <path to GIS file> <span style="color:green;">! Can be used to spatially vary soil type using polygons</span>
<br>
2. The soil types have already been defined in the output '''soils.tsoilf''' file - See Section 6.10.4 in the TUFLOW Manual. This file defines soil type 1 as using the initial/continuing loss method. The values '''<<IL_test>>''' and '''<<CL_test>>''' are variables because they have the triangular brackets '''<<>>''' ("test" in this case is the catchment name).<br>
: [[File: ARR_example_tsoilf.PNG]]<Br>
3. The IL_test and CL_test variables are being initialised in '''soil_infilatration.trd'''. This file is using <tt>IF statements</tt> to set the values based on the event.<br>
: [[File: ARR_example_soil_infiltration_trd.PNG]]<br>
4. Both the '''soils.tsoilf''' and '''soil_infiltration.trd''' need to be read into the '''TUFLOW Control File (TCF)''' (order does not matter). Copy both files to the '''TUFLOW/model''' directory.<br>
'''''TUFLOW Control File'''''
<span style="color:blue;">Read Soils File</span> <span style="color:red;">==</span> ..\model\soils.tsoilf <span style="color:green;">! location of soils.tsoilf</span>
<span style="color:blue;">Read File</span> <span style="color:red;">==</span> ..\model\soil_infiltration.trd <span style="color:green;">! read file containing variable values</span>
<br>
5. The boundary database and inflow files also need to be read in. Copy the '''bc_dbase.csv''' and the entire '''rf_inflow''' to the '''TUFLOW/bc_dbase''' directory.<br>
'''''TUFLOW Control File'''''
<span style="color:blue;">BC Database</span> <span style="color:red;">==</span> ..\bc_dbase\bc_dbase.csv <span style="color:green;">! location of boundary database</span>
<br>
6. An event database has already been populated in the '''Event_File.tef''' output. This file contains an event entry for the one magnitude that was selected, 8 durations (1 hr -> 12 hr), and 10 temporal patterns.<br>
: [[File: ARR_example_tef.PNG]]
<br>
7. The '''Event_File.tef''' also needs to be read into the TCF. Copy the '''Event_File.tef''' into the '''TUFLOW/runs''' directory.<br>
'''''TUFLOW Control File'''''
<span style="color:blue;">Event File</span> <span style="color:red;">==</span> Event_File.tef <span style="color:green;">! location event database</span>
8. When running the model, the flags can be added to the batch file. The event names must match the names in the '''Event_File.tef''' as stated in the command <tt><font color="blue">Define Event</font> font color="red">==</font></tt><br>
'''''Run Batch File'''''
TUFLOW.exe -b -e1 1p -e2 060m -e3 TP01 my_model.tcf
TUFLOW.exe -b -e1 1p -e2 060m -e3 TP02 my_model.tcf
TUFLOW.exe -b -e1 1p -e2 060m -e3 TP03 my_model.tcf
TUFLOW.exe -b -e1 1p -e2 060m -e3 TP04 my_model.tcf
TUFLOW.exe -b -e1 1p -e2 060m -e3 TP05 my_model.tcf
... and so on
An example of a naming convention that could be used with the ARR2016 output is: '''<Model_Name>_~e1~~e2~_~e3~_~s1~_00X.tcf''' where
| |||