Difference between revisions of "TUFLOW Message 2072"
Jump to navigation
Jump to search
| (2 intermediate revisions by the same user not shown) | |||
| Line 5: | Line 5: | ||
|message_desc=No Boundary (.tbc) File Specified. Each model domain, must have a .tbc specified. A blank .tbc can be specified. | |message_desc=No Boundary (.tbc) File Specified. Each model domain, must have a .tbc specified. A blank .tbc can be specified. | ||
|suggestions=Specify a .tbc file for each 2D domain using:<br> | |suggestions=Specify a .tbc file for each 2D domain using:<br> | ||
| − | <font color=" | + | <font color="blue"><tt>BC Control File </tt></font><font color="red"><tt>== </tt></font><font color="black"><tt><.tbc file></tt></font> |
| − | + | ||
| − | |||
| − | |||
| − | |||
|uplink=[[2xxx_TUFLOW_Messages|2xxx Messages]] | |uplink=[[2xxx_TUFLOW_Messages|2xxx Messages]] | ||
| − | |||
}} | }} | ||
Latest revision as of 11:56, 23 December 2022
TUFLOW Message
WARNING 2072 - No Boundary (.tbc) File Specified for 2D Domain <2D domain name>.
Alternate Message
NA
Message Type
WARNING
Description
No Boundary (.tbc) File Specified. Each model domain, must have a .tbc specified. A blank .tbc can be specified.
Suggestions
Specify a .tbc file for each 2D domain using:
BC Control File == <.tbc file>
| Up |
|---|
 2xxx Messages
|