TUFLOW Message 2051: Difference between revisions
		
		
		
		Jump to navigation
		Jump to search
		
Content deleted Content added
| No edit summary | No edit summary | ||
| Line 4: | Line 4: | ||
| |type=[[ERROR]] <br> [[WARNING]] | |type=[[ERROR]] <br> [[WARNING]] | ||
| |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 objects, if a HX or SX boundary is desired ensure CN object is correctly snapped.  If no boundary desired remove CN object. | |||
| |suggestions=???? | |||
| |discussion_page=* [[Talk:TUFLOW Message 2051|Discuss Message 2051]] | |discussion_page=* [[Talk:TUFLOW Message 2051|Discuss Message 2051]] | ||
| |link3='' | |link3='' | ||
Revision as of 14:21, 11 February 2011
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 objects, if a HX or SX boundary is desired ensure CN object is correctly snapped.  If no boundary desired remove CN object.
| Up | 
|---|
|  2xxx Messages |