TUFLOW Message 2194: Difference between revisions

Browse history interactively

Content deleted Content added

VisualWikitext

Revision as of 15:39, 8 August 2010 view source tuflow>Par Created page with '{{TUFLOW_Message \|tuflow_message=???? \|message_desc=Column 1 values not ascending in a boundary condition table. Table data is output to the .tlf file and console. \|suggestions=...'		Latest revision as of 13:58, 7 February 2023 view source Melissa.Moghanloo (talk \| contribs) Bureaucrats, Administrators 2,918 edits No edit summary
(4 intermediate revisions by 3 users not shown)
Line 1: {{TUFLOW_Message \|tuflow_message=~~????~~ERROR 2194 - Column 1 values not ascending in ",a," table \|~~message_desc~~alt_msg=ERROR 2194 - Column 1 values not ascending in ",a ~~boundary condition~~," table~~. Table data is output to the .tlf file and console~~. \|type=[[ERROR]] ~~\|suggestions=????~~ \|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. ~~\|discussion_page=* [[Talk:TUFLOW Message 2194\|Discuss Message 2194]]~~ \|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. ~~\|link3=''~~ ~~\|link4=''~~ ~~\|prelink=[[TUFLOW_Message_2193\|Message 2193]]~~ \|uplink=[[2xxx_TUFLOW_Messages\|2xxx Messages]] ~~\|nextlink=[[TUFLOW_Message_2195\|Message 2195]]~~ }}