QGIS ARR to TUFLOW Example: Difference between revisions

* other options left as default (can be seen in image)

[[File: ARR_example_dialogARR_example_dialog_02.PNG | 650pxpng]]<br><br>

[[File: ARR_example_output_folderARR_example_output_folder_03.PNGpng | 500px]]<br><br>

[[File: ARR_example_output_folder_dataARR_example_output_folder_data_03.PNG | 500pxpng]]<br><br>

[[File: ARR_example_output_folder_rf_inflowARR_example_output_folder_rf_inflow_03.PNG | 500pxpng]]<br><br>

* WARNING: 10215 preburst rainfall depths exceeded storm initial loss (507.24% of entries)

[[File: ARR_Burst_Initial_Losses_plot.png | 500px]]

The plot above confirms the warning - a significant portionsome 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 event. 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>

<span style="color:blue;">Set Soil</span> <span style="color:red;">==</span> 1 <span style="color:green;">! globallyGlobally set all active cells to soil type 1</span>

2. The soil types have already been defined in the output '''soils.tsoilf''' file - SeeRefer Sectionto 6the <u>[https://docs.10tuflow.4 in thecom/classic-hpc/manual/latest/ TUFLOW Manual]</u> for more information. 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_tsoilfARR_example_tsoilf_02.PNGpng]]<Br>

3. The IL_test and CL_test variablesvalues are being initialisedset 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_trdARR_example_soil_infiltration_trd_01.PNGpng]]<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 bothBoth files were copied to the '''TUFLOW/model''' directory.<br>

<span style="color:blue;">Read Soils File</span> <span style="color:red;">==</span> ..\model\soils.tsoilf <span style="color:green;">! locationLocation of soils file (.tsoilf)</span>

<span style="color:blue;">Read File</span> <span style="color:red;">==</span> ..\model\soil_infiltration.trd <span style="color:green;">! readRead file containing variable values</span>

5. The boundary database and inflow files also need to be read in. Copy the '''bc_dbase.csv''' and the entire '''rf_inflow''' folder were copied to the '''TUFLOW/bc_dbase''' directory.<br>

<span style="color:blue;">BC Database</span> <span style="color:red;">==</span> ..\bc_dbase\bc_dbase.csv <span style="color:green;">! locationLocation of boundary database</span>

6. An event database has already been populatedcreated in the- '''Event_File.tef''' output. This file contains an event entry for each of the 1 magnitude, 8 durations (1 hr -> 12 hr), and 10 temporal patterns that was selected in the tool.<br>

7. The '''Event_File.tef''' also needs to be read into the TCF. Copy theThe '''Event_File.tef''' was copied into the '''TUFLOW/runs''' directory.<br>

<span style="color:blue;">Event File</span> <span style="color:red;">==</span> Event_File.tef <span style="color:green;">! locationLocation of event databasefile (.tef)</span>

8. When running the model, the following flags can be added to the batch file. The event names must match the names in the '''Event_File.tef''' as stated after the command <tt><font color="blue">Define Event</font> <font color="red">==</font></tt><br>