TUFLOW Message 0115: Difference between revisions

Browse history interactively

← Older edit

Content deleted Content added

VisualWikitext

Revision as of 14:34, 29 January 2019 view source Pavlina Monhartova (talk \| contribs) Bureaucrats, Administrators 5,388 edits No edit summary ← Older edit		Latest revision as of 10:10, 22 December 2022 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 0115 - First column values not in ascending order. Incorrect values are: \|alt_msg=ERROR 0115 - Time data not in ascending order ~~\|alt_msg=NA~~ \|type=[[ERROR]] \|message_desc=Data in first column, should be unique and in ascending order. For aexample an XZ (offset - elevation) table, the X data (offset) should be unique and in ascending order. \|suggestions=Check data, remove duplicate values and sort by first column.<br> This error can occur when using rainfall control file (.trfc) and having more than 1000 hyetograph entries in the BC database. As 1000 entries is a default limit, TUFLOW will read the correct vallue in the "Time" column in the row 1000, but it will read 0 in the row 1001, ~~which~~ignoring ~~is not in~~the ~~ascending~~original ~~order~~value. Command <font color="blue"><tt> Maximum Hyetograph Points </tt></font> <font color="red"><tt>== </tt></font> <tt><max_pts></tt> can be used to increase the default limit. <br> ~~\|discussion_page=* [[Talk:TUFLOW Message 0115\|Discuss Message 0115]]~~ ~~\|link3=''~~ ~~\|link4=''~~ ~~\|prelink=[[TUFLOW_Message_0112\|Message 0112]]~~ \|uplink=[[0xxx_TUFLOW_Messages\|0xxx Messages]] ~~\|nextlink=[[TUFLOW_Message_0116\|Message 0116]]~~ }}