TUFLOW Message 2060: Difference between revisions
Jump to navigation
Jump to search
Content deleted Content added
No edit summary |
No edit summary |
||
| (9 intermediate revisions by 4 users not shown) | |||
| Line 1: | Line 1: | ||
{{TUFLOW_Message |
{{TUFLOW_Message |
||
|tuflow_message=ERROR |
|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 (e.g. bd_dbase.csv, HT/QT table, and etc) 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 message, and ensure that .tbc command has no misspelling, or the input data is in the correct format. |
|||
|suggestions=Ensure that there is a CN object at each end of HX line connecting HX line to 1D node. |
|||
|discussion_page=* [[Talk:TUFLOW Message 2061|Discuss Message 2061]] |
|||
|link3='' |
|||
|link4='' |
|||
|prelink=[[TUFLOW_Message_2060|Message 2060]] |
|||
|uplink=[[2xxx_TUFLOW_Messages|2xxx Messages]] |
|uplink=[[2xxx_TUFLOW_Messages|2xxx Messages]] |
||
|nextlink=[[TUFLOW_Message_2062|Message 2062]] |
|||
}} |
}} |
||
Latest revision as of 11:50, 23 December 2022
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 (e.g. bd_dbase.csv, HT/QT table, and etc) isn't in the correct data format.
Suggestions
Check which line in the input file is causing the issue from the error message, and ensure that .tbc command has no misspelling, or the input data is in the correct format.
| Up |
|---|
 2xxx Messages
|