Difference between revisions of "TUFLOW Message 0115"
| Line 1: | Line 1: | ||
{{TUFLOW_Message | {{TUFLOW_Message | ||
|tuflow_message=ERROR 0115 - First column values not in ascending order. Incorrect values are: | |tuflow_message=ERROR 0115 - First column values not in ascending order. Incorrect values are: | ||
| − | |alt_msg= | + | |alt_msg=ERROR 0115 - Time data not in ascending order |
|type=[[ERROR]] | |type=[[ERROR]] | ||
|message_desc=Data in first column, should be unique and in ascending order. For a XZ (offset - elevation), the X data (offset) should be unique and in ascending order. | |message_desc=Data in first column, should be unique and in ascending order. For a XZ (offset - elevation), the X data (offset) should be unique and in ascending order. | ||
Revision as of 11:35, 2 July 2019
TUFLOW Message
ERROR 0115 - First column values not in ascending order. Incorrect values are:
Alternate Message
ERROR 0115 - Time data not in ascending order
Message Type
ERROR
Description
Data in first column, should be unique and in ascending order. For a XZ (offset - elevation), the X data (offset) should be unique and in ascending order.
Suggestions
Check data, remove duplicate values and sort by first column.
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 ignoring the original value. Command Maximum Hyetograph Points == <max_pts> can be used to increase the default limit.
| Up |
|---|
 0xxx Messages
|