Tuflow and estry manual Version 3

3.17.3Using the BC Event Name Command

The BC Event Text and BC Event Name commands (.tcf file) minimise data repetition by removing the need to create a separate BC database .csv file for each BC event. These commands are also available in the .ecf file for 1D only models (BC Event Text and BC Event Name) and .tbc file (BC Event Text and BC Event Name).

How the commands work is illustrated in the example below.

A BC database file worksheet is created as illustrated below and the following lines occur in all .tcf files. (Tip: Specify these lines in a separate file and use the Read File command in all the .tcf files to read these commands. This saves repeating these lines, and other commands common to all .tcf files.)

BC Database == ..\bc dbase\PR_bc_dbase.csv

BC Event Text == __event__

The above commands set the active BC Database for TUFLOW and ESTRY to ..\bc dbase\PR_bc_dbase.csv, and defines the text “__event__” as that which defines the BC event name as discussed below.

In the .tcf file for the 100 year flood simulation, the following command occurs:

BC Event Name == Q100

TUFLOW and ESTRY will now replace the first occurrence of “__event__” with “Q100” in each line of the BC database. If “__event__” does not occur the line remains unchanged. In the example below, the following occurs:

• 
  For the BC event “Oxley Ck Inflow”, the BC data is read from file “Q100.csv” rather than “__event__.csv” as indicated in the spreadsheet.
  
• 
  Similarly, the same applies for “h Downstream” and “Paradise Ck Inflow” BC events.
  

The file Q100.csv is created from the worksheet “Q100.csv” as shown below.

To set up other simulations, for example a five year flood simulation, it is simply a process of creating the Q005.csv file, copying the Q100.tcf file to a Q005.tcf file and changing BC Event Name to:
BC Event Name == Q005

There is no need to create another BC database file.