Sets the active BC Database file as described in Sections 3.17.1 and 3.17.2. The file is usually created using spreadsheet software such as Microsoft Excel.
If the BC Database is specified in the TUFLOW .tcf file, it is set as the active database for both 2D and 1D models. However, the active database can be changed at any stage in the .tbc and .ecf files by repeating the command with the new database set as the <.csv_file>.
A BC Database must be specified before any of the other BC commands are used.
BC Event Name ==
(Optional)
Sets the active BC name to be substituted where (see BC Event Text) occurs in the BC Database. See Section 3.17.3 for a description of how the BC event commands operate.
This command is normally specified in the .tcf file, and only used in the .tbc file if the event boundaries vary by event within the model. For example, it may be set to “Q100” to read in the 100 year catchment inflows, then set as “H010” to read in the 10 year ocean levels for the downstream boundary. Note that, in this case, the locations of the catchment inflows and downstream boundaries would have to be placed in two separate GIS layers, with each layer read using Read MI BC after the relevant BC Event Name command as shown below:
BC Event Name == H010
Read MI BC == mi\1d_bc_head_boundaries.mif
BC Event Name == Q100
Read MI BC == mi\1d_bc_flow_boundaries.mif
BC Event Text ==
(Optional)
Sets the text in the BC Database that is to be substituted by the BC Event Name command value. See Section 3.17.3 for a description of how the BC event commands operate.
For 2D/1D models this command only needs to be specified in the .tcf file. It would be only used in the .ecf file for 1D only models or if for some reason the value needs to change (this should be very unlikely) prior to reading the 1D BCs. Also see BC Event Text for the .tcf file if the model is 2D/1D.
The value can be changed at any stage by repeating this command in the .ecf file, although it is strongly recommended that the value is standardised across all models and the command is specified only once.
EB Data ==
(1D & 2D/1D. Optional)
Read boundary condition tables from a file in ESTRY’s fixed field format. The command can be used any number of times to access more than one file, and the file may contain other information besides boundary condition data tables.
Read MI BC == <.mif/.mid_file>
(Mandatory if not using fixed field text entry)
Reads the location and attributes of 1D model boundary conditions as described in Section 3.17.