Difference between revisions of "TUFLOW Message 1005"
Jump to navigation
Jump to search
Chris Huxley (talk | contribs) |
Melissa1987 (talk | contribs) |
||
| (One intermediate revision by the same user not shown) | |||
| Line 5: | Line 5: | ||
|message_desc=1D boundary condition (1d_bc) object is not snapped to a 1D node. | |message_desc=1D boundary condition (1d_bc) object is not snapped to a 1D node. | ||
|suggestions=Check snapping and location of 1d_bc object to ensure it is at a valid 1D node (1d_nwk). | |suggestions=Check snapping and location of 1d_bc object to ensure it is at a valid 1D node (1d_nwk). | ||
| − | + | ||
| − | + | ||
| − | |||
| − | |||
|uplink=[[1xxx_TUFLOW_Messages|1xxx Messages]] | |uplink=[[1xxx_TUFLOW_Messages|1xxx Messages]] | ||
| − | |||
}} | }} | ||
Latest revision as of 13:36, 22 December 2022
TUFLOW Message
ERROR 1005 - Failed to find a node snapped to boundary condition with name ",a,
Alternate Message
NA
Message Type
ERROR
Description
1D boundary condition (1d_bc) object is not snapped to a 1D node.
Suggestions
Check snapping and location of 1d_bc object to ensure it is at a valid 1D node (1d_nwk).
| Up |
|---|
 1xxx Messages
|