Difference between revisions of "TUFLOW Message 2194"
Jump to navigation
Jump to search
Steph.dufour (talk | contribs) |
|||
| Line 4: | Line 4: | ||
|type=[[ERROR]] | |type=[[ERROR]] | ||
|message_desc=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. | |message_desc=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. | + | |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. |
|discussion_page=* [[Talk:TUFLOW Message 2194|Discuss Message 2194]] | |discussion_page=* [[Talk:TUFLOW Message 2194|Discuss Message 2194]] | ||
|link3='' | |link3='' | ||
Revision as of 17:38, 22 September 2014
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
|