TUFLOW Message 2060: Difference between revisions
Jump to navigation
Jump to search
Content deleted Content added
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
{{TUFLOW_Message |
{{TUFLOW_Message |
||
|tuflow_message=ERROR 2060 - Unrecognisable .tbc command or problem reading BC data in fixed field format. |
|tuflow_message=ERROR 2060 - Unrecognisable .tbc command or problem reading BC data in fixed field format.<br> |
||
Incorrect Line = "xxxxxx" |
|||
|alt_msg=NA |
|alt_msg=NA |
||
|type=[[ERROR]] |
|type=[[ERROR]] |
||
|message_desc=.tbc command is invalid or BC input file isn't in the correct data format. |
|||
|message_desc=Could not find a connection (CN object) snapped to the end of the 1D/2D interface (HX) line. Check that any connection object is snapped; add a connection to the end of the 1D/2D interface; or edit the 1D/2D interface line. 1D/2D interface lines based on the HX type must have as a minimum a connection at each of its ends, otherwise it is not clear how to transfer the water level gradient from the 1D domain. |
|||
|suggestions=Check which line in the input file is causing the issue from the error messaging and ensure that .tbc command has no misspelling, or the input data is in correct format. |
|||
|suggestions=Ensure that there is a CN object at each end of HX line connecting HX line to 1D node. The messages.mif or messages_P.shp file should contain the location that this error is occurring. Zoom into the HX line and check that the connection line is snapped to the end vertices of the line. This line can have CN connections snapped to intermediate vertices, but <u>'''must '''</u> have a CN line snapped to each end. |
|||
|discussion_page=* [[Talk:TUFLOW Message |
|discussion_page=* [[Talk:TUFLOW Message 2060|Discuss Message 2060]] |
||
|link3='' |
|link3='' |
||
|link4='' |
|link4='' |
||
Revision as of 13:05, 6 January 2020
TUFLOW Message
ERROR 2060 - Unrecognisable .tbc command or problem reading BC data in fixed field format.
Incorrect Line = "xxxxxx"
Alternate Message
NA
Message Type
ERROR
Description
.tbc command is invalid or BC input file isn't in the correct data format.
Suggestions
Check which line in the input file is causing the issue from the error messaging and ensure that .tbc command has no misspelling, or the input data is in correct format.
| Up |
|---|
 2xxx Messages
|