TUFLOW Message 2194: Difference between revisions
Jump to navigation
Jump to search
Content deleted Content added
No edit summary |
No edit summary |
||
| Line 6: | Line 6: | ||
|suggestions=Check data, remove duplicate values and sort by first column. Note for TUFLOW build 2012-05-AC, consecutive flow values in automatic 2D HQ boundary tables are now automatically removed. |
|suggestions=Check data, remove duplicate values and sort by first column. Note for TUFLOW build 2012-05-AC, consecutive flow values in automatic 2D HQ boundary tables are now automatically removed. |
||
|prelink=[[TUFLOW_Message_2193|Message 2193]] |
|||
|uplink=[[2xxx_TUFLOW_Messages|2xxx Messages]] |
|uplink=[[2xxx_TUFLOW_Messages|2xxx Messages]] |
||
|nextlink=[[TUFLOW_Message_2195|Message 2195]] |
|||
}} |
}} |
||
Latest revision as of 13:58, 7 February 2023
TUFLOW Message
ERROR 2194 - Column 1 values not ascending in ",a," table
Alternate Message
ERROR 2194 - Column 1 values not ascending in ",a," table.
Message Type
ERROR
Description
Column 1 values not ascending in a boundary condition table. Table data is output to the .tlf file and console. For a Head-Time the first column is the time data, time values should be unique and in ascending order. The same applies to all boundary condition types. For a HQ (stage-discharge, or rating curve) the height values should be increasing.
Suggestions
Check data, remove duplicate values and sort by first column. Note for TUFLOW build 2012-05-AC, consecutive flow values in automatic 2D HQ boundary tables are now automatically removed.
| Up |
|---|
 2xxx Messages
|