Difference between revisions of "TUFLOW Message 2129"
Jump to navigation
Jump to search
| Line 7: | Line 7: | ||
|message_desc=No Boundary Control File (.tbc) specified. Each 2D domain must have a boundary control file specified. | |message_desc=No Boundary Control File (.tbc) specified. Each 2D domain must have a boundary control file specified. | ||
|suggestions=Specify a boundary control file in the .tcf with <font color="blue"><tt>BC Control File </tt></font> <font color="red"><tt>==</tt></font> <tt><filename.tbc></tt> for each 2D domain.<br> | |suggestions=Specify a boundary control file in the .tcf with <font color="blue"><tt>BC Control File </tt></font> <font color="red"><tt>==</tt></font> <tt><filename.tbc></tt> for each 2D domain.<br> | ||
| − | If there are no 2D boundaries to be applied a .tbc file with no commands in it can be specified (e.g. an empty .tbc file). | + | If there are no 2D boundaries to be applied a .tbc file with no commands in it can be specified (e.g. an empty/blank .tbc file). |
Latest revision as of 09:10, 9 December 2024
TUFLOW Message
ERROR 2129 - No Boundary File Specified for 2D Domain <2D domain name>.
Alternate Message
Older versions of TUFLOW may have reported the message below and disappeared from the screen:
No Boundary File specified for 2D Domain <2D Domain Name>. Bailing out.
Message Type
ERROR
Description
No Boundary Control File (.tbc) specified. Each 2D domain must have a boundary control file specified.
Suggestions
Specify a boundary control file in the .tcf with BC Control File == <filename.tbc> for each 2D domain.
If there are no 2D boundaries to be applied a .tbc file with no commands in it can be specified (e.g. an empty/blank .tbc file).
| Up |
|---|
 2xxx Messages
|