QGIS ReFH2 to TUFLOW: Difference between revisions
Content deleted Content added
Tuflowduncan (talk | contribs) |
Tuflowduncan (talk | contribs) |
||
Line 88:
=Using TUFLOW Events=
In most hydraulic modelling applications there will be a requirement to run a number of return period design events, potentially with a number of different durations. TUFLOW’s event options makes the management of these simulations a simpler process. TUFLOW’s event management structure uses a variety of wildcard characters in the TCF file and the boundary condition database for event inputs. The wildcards are replaced with user defined event specific acronyms when a simulation is run from a batch file. This will significantly reduce the number of repetitive files required to execute a project. TUFLOW event management is shown in the following image.
<br>
[[File:Tuflow_Events.jpg]]<br>
Line 96 ⟶ 95:
The wildcard works on column 2. So we can use this to obtain the return period as specified in the batch file and read the relevant column from a csv file exported directly from ReFH2. For example, in the file directly exported from ReFH2, the 1 year net rainfall column is called "Total flow m3/s (1 year) - as 100% rural model”. We can set column 2 to look for the "Total flow m3/s (~ARI~) – as 100% rural model" bc_dbase setup to read the relevant net rainfall column for the return period of interest based on the ARI wildcard.
Once the bc_base has been set up then a .tef file can be generated which populates the ARI variable above with the relevant return period for the specific question.
Line 107 ⟶ 105:
</pre>
This will then run the 3 return periods (1yr, 2yr and 5 year) using the correct wildcard as specified in the tef file and using the relevant boundary data.
=Summary=
| |||