Using ReFH2 to Generate TUFLOW Boundary Inputs: Difference between revisions

In most 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.

TUFLOW’s event management will be of use when running multiple return periods and durations events from ReFH2. Currently a single CSV file will be generated for a number of return periods from the ReFH2 software. Where multiple durations are used, this will generate multiple csv files. Each of these can be defined as a separate source csv file. For instance, in the bc_dbase file we can have the following where _Duration_ is the wildcard to specify the individual csv files references the different return period hyetographs for each duration as below.

For example, in the file directly exported from ReFH2, the 1 year net rainfall column is called “Total'''"Total net rain mm (1 year) - as 100% rural model”'''. We can set column 2 to look for the ‘Total'''"Total net rain mm (ARI) – as 100% rural model’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 ARI for the specific question. The tef'''TEF''' file also creates anew new output folder for each return period.

The '''.tcfTCF''' file can be named accordingly for example, '''Dummy_M01_~e1~_001.tcf''', and the batch file commands used to set the ~e1~ value.

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.