Difference between revisions of "TUFLOW Message 2051"
Jump to navigation
Jump to search
| Line 5: | Line 5: | ||
|message_desc=Connection object unused or not snapped to a 2D HX or 2D SX object. All connections (CN objects) must be snapped to a 1D/2D interface object. | |message_desc=Connection object unused or not snapped to a 2D HX or 2D SX object. All connections (CN objects) must be snapped to a 1D/2D interface object. | ||
|suggestions=Review boundary configuration, if a HX or SX boundary is desired ensure HX or SX object exists and CN object is correctly snapped. If no boundary is desired remove CN object. | |suggestions=Review boundary configuration, if a HX or SX boundary is desired ensure HX or SX object exists and CN object is correctly snapped. If no boundary is desired remove CN object. | ||
| − | + | ||
| − | |||
| − | |||
|prelink=[[TUFLOW_Message_2050|Message 2050]] | |prelink=[[TUFLOW_Message_2050|Message 2050]] | ||
|uplink=[[2xxx_TUFLOW_Messages|2xxx Messages]] | |uplink=[[2xxx_TUFLOW_Messages|2xxx Messages]] | ||
|nextlink=[[TUFLOW_Message_2052|Message 2052]] | |nextlink=[[TUFLOW_Message_2052|Message 2052]] | ||
}} | }} | ||
Revision as of 13:06, 6 July 2022
TUFLOW Message
ERROR 2051 - Connection object unused or not snapped to a 2D HX or 2D SX object.
Alternate Message
WARNING 2051 - Connection object unused or not snapped to a 2D HX or 2D SX object.
Description
Connection object unused or not snapped to a 2D HX or 2D SX object. All connections (CN objects) must be snapped to a 1D/2D interface object.
Suggestions
Review boundary configuration, if a HX or SX boundary is desired ensure HX or SX object exists and CN object is correctly snapped. If no boundary is desired remove CN object.
| Up |
|---|
 2xxx Messages
|