Difference between revisions of "TUFLOW Message 2129"
Jump to navigation
Jump to search
m |
|||
Line 6: | Line 6: | ||
|type=[[ERROR]] | |type=[[ERROR]] | ||
|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 | + | |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 .tbc file). | ||
|discussion_page=* [[Talk:TUFLOW Message 2129|Discuss Message 2129]] | |discussion_page=* [[Talk:TUFLOW Message 2129|Discuss Message 2129]] |
Revision as of 15:27, 28 April 2022
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 .tbc file).
Up |
---|
2xxx Messages |