TUFLOW Message 2129: Difference between revisions
Jump to navigation
Jump to search
Content deleted Content added
No edit summary |
No edit summary |
||
| Line 9: | Line 9: | ||
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). |
||
|prelink=[[TUFLOW_Message_2128|Message 2128]] |
|||
|uplink=[[2xxx_TUFLOW_Messages|2xxx Messages]] |
|uplink=[[2xxx_TUFLOW_Messages|2xxx Messages]] |
||
|nextlink=[[TUFLOW_Message_2130|Message 2130]] |
|||
}} |
}} |
||
Revision as of 13:36, 7 February 2023
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
|