Difference between revisions of "TUFLOW Message 2026"
Jump to navigation
Jump to search
| Line 3: | Line 3: | ||
|alt_msg=NA | |alt_msg=NA | ||
|type=[[ERROR]] | |type=[[ERROR]] | ||
| − | |message_desc=1D node snapped to 2D SX object is different to 1D node at end of CN that is also snapped to the SX object. | + | |message_desc=1D node snapped to 2D SX object is different to 1D node at end of CN that is also snapped to the SX object. Two 1D nodes are present, one snapped to end of CN object, one snapped to end of SX object. |
| − | |suggestions= | + | |suggestions=Review boundary configuration. Seperate 2D SX objects should be used for seperate nodes, or link nodes using a "X" type 1D network channel and have only one SX object. |
|discussion_page=* [[Talk:TUFLOW Message 2026|Discuss Message 2026]] | |discussion_page=* [[Talk:TUFLOW Message 2026|Discuss Message 2026]] | ||
|link3='' | |link3='' | ||
Revision as of 16:32, 6 February 2011
TUFLOW Message
ERROR 2026 - 1D node snapped to 2D SX object is different to 1D node at end of CN that is also snapped to the SX object.
Alternate Message
NA
Message Type
ERROR
Description
1D node snapped to 2D SX object is different to 1D node at end of CN that is also snapped to the SX object. Two 1D nodes are present, one snapped to end of CN object, one snapped to end of SX object.
Suggestions
Review boundary configuration. Seperate 2D SX objects should be used for seperate nodes, or link nodes using a "X" type 1D network channel and have only one SX object.
| Up |
|---|
 2xxx Messages
|