TUFLOW Message 0060: Difference between revisions

Browse history interactively

← Older edit

Content deleted Content added

VisualWikitext

Revision as of 12:17, 13 August 2018 view source ShuangGao (talk \| contribs) Bureaucrats, Administrators 1,087 edits No edit summary ← Older edit		Latest revision as of 09:07, 4 January 2024 view source Abigail.lillo (talk \| contribs) Bureaucrats, Administrators 539 edits No edit summary
(12 intermediate revisions by 3 users not shown)
Line 1: {{TUFLOW_Message \|tuflow_message=ERROR 0060 - Command line is missing "<font color="red"><tt>==</tt></font>"<br> Problematic Line: <line> \|alt_msg=WARNING 0060 - Command line is missing "<font color="red"><tt>==</tt></font>"<br> Problematic Line: <line> \|type=[[ERROR]]<br> [[WARNING]] \|message_desc=The 2016 version of TUFLOW is more rigorous in checking that each line in the control files contains a valid command (comments and blank lines are excluded). This checking provides a more meaningful error if the control file command is missing the double equal. For example if "<font color="blue"><tt>If Scenario </tt></font> <font color="red"><tt>=</tt></font><tt> 5m</tt>" (note single =) is used instead of "<font color="blue"><tt>If Scenario </tt></font> <font color="red"><tt>==</tt></font><tt> 5m</tt>".<br> This error is also triggered when control files are separated into sections with symbols like dashes, underscores and these are not commented out at the start, e.g. " __________ " instead of " <font color="green"><tt>!__________</tt></font> ". <br> <br> To revert back to the previous command line processing the .tcf command below can be used: <font color="blue"><tt>Command Line Processing </tt></font> <font color="red"><tt>==</tt></font><tt> Pre 2016</tt><br> The Pre 2016 method for processing lines is also used if the "<font color="blue"><tt>Defaults </tt></font> <font color="red"><tt>==</tt></font><tt> Pre 2016</tt>" is set in the .tcf. \|suggestions=Ensure that the TUFLOW command ~~line~~lines ~~listed above is~~are valid and ~~contains~~contain the <font color="red"><tt>==</tt></font> operator or are commented out.<br> Valid commands that do not have the <font color="red"><tt>==</tt></font> operator are listed below: <pre> ELSE Line 28 ⟶ 29: OUTPUT FILE NONE </pre> If you have checked all the commands are valid but still receive this error, please also check whether your control files contain any Byte Order Mark <u>(https://en.wikipedia.org/wiki/Byte_order_mark)</u>. The Byte Order Mark can be found in some text files to indicate the byte order. The use of Byte Order Mark of is optional, but it may cause command line reading error ~~during TUFLOW pre-processing~~. An example of UTC-8-BOM encoding file viewed with HEX mode is shown below, and the first 3 characters can prevent TUFLOW from recognising the first line as commented line.<br> [[File:~~Remove_Byte_Order_Mark_002~~Remove_Byte_Order_Mark_001.PNG\|600px]]<br><br> These Byte Order Marks can be removed using Notepad++, by going to ''Encoding'' -> ''Convert to UTF-8'' and save the file.<br> [[File:~~Remove_Byte_Order_Mark_001~~Remove_Byte_Order_Mark_002.PNG\|400px]]<br><br> ~~If unsure about why you receiving this message please contact <font color="blue"><u>support@tuflow.com</u></font> and attach the log file and control file inputs.~~ ~~\|discussion_page=* [[Talk:TUFLOW Message 0013\|Discuss Message 0013]]~~ ~~\|link3=''~~ ~~\|link4=''~~ ~~\|prelink=[[TUFLOW_Message_0012\|Message 0012]]~~ \|uplink=[[0xxx_TUFLOW_Messages\|0xxx Messages]] ~~\|nextlink=[[TUFLOW_Message_0020\|Message 0020]]~~ }}