Tuflow and estry manual Version 3

3.17Boundary Conditions and Linking 2D/1D Models

1D and 2D domains use the same approach to setting up boundary conditions. They both access the same boundary condition database, although separate databases can be set up if desired. They also use the same commands in the text files.

3.17.1Boundary Condition (BC) Database

A boundary condition (BC) database is setup using spreadsheet software such as Microsoft Excel. Two types of files are required:

1. 
   A database or list of BC events including information on where to find the BC data.
   
2. 
   One or more files containing the BC data.
   

The database file must be .csv (comma delimited) formatted. It must contain a row with the pre-defined keywords Name and Source as listed in Table 4 .21. Other keywords control how data is extracted from the source.

The BC data files can be in a variety of formats as described for the Source keyword in Table 4 .21. Additional formats can be incorporated upon request. It is strongly recommended that all .csv files originate from one spreadsheet with a worksheet dedicated to each .csv file.

Both 1D and 2D domains can access the same files.

The active BC Database is specified using BC Database (.tcf file), BC Database (.ecf file) and/or BC Database (.tbc file). Note, specifying BC Database in the .tcf file automatically applies to both 1D and 2D domains (ie. there is no need to specify the command in the .ecf or .tbc files). The active database can be changed at any point by repeating the command in any of these files.

At Build 2003 06 AE, the maximum line length (ie. number of characters including spaces and tabs) in a source file was increased from 1,000 to 10,000 characters.
Table 4.21 BC Database Keyword Descriptions