Difference between revisions of "TUFLOW Message 2030"
Jump to navigation
Jump to search
Melissa1987 (talk | contribs) |
|||
| Line 6: | Line 6: | ||
|suggestions=Separate incompatible boundary types, for example a single 2D cell cannot be both a water level boundary and a flow boundary. The <u>[[Check_Files_2d_bcc_check | bcc_check]]</u> layer is useful identifying cells acting as boundaries. | |suggestions=Separate incompatible boundary types, for example a single 2D cell cannot be both a water level boundary and a flow boundary. The <u>[[Check_Files_2d_bcc_check | bcc_check]]</u> layer is useful identifying cells acting as boundaries. | ||
| − | + | ||
|uplink=[[2xxx_TUFLOW_Messages|2xxx Messages]] | |uplink=[[2xxx_TUFLOW_Messages|2xxx Messages]] | ||
| − | |||
}} | }} | ||
Latest revision as of 11:00, 23 December 2022
TUFLOW Message
ERROR 2030 - Trying to apply a HT or HS boundary to a 2D cell already assigned a link or a HQ, Q or S boundary.
Alternate Message
NA
Message Type
ERROR
Description
Trying to apply a water level boundary (eg. HT or HS) to a 2D cell already assigned a link or incompatible boundary (ie. a HQ, Q or S boundary).
Suggestions
Separate incompatible boundary types, for example a single 2D cell cannot be both a water level boundary and a flow boundary. The bcc_check layer is useful identifying cells acting as boundaries.
| Up |
|---|
 2xxx Messages
|