TUFLOW Message 0021: Difference between revisions

Content deleted Content added

Revision as of 12:00, 1 July 2022 view source Melissa.Moghanloo (talk \| contribs) Bureaucrats, Administrators 2,918 edits No edit summary ← Older edit		Latest revision as of 09:52, 23 September 2024 view source Emilie Nielsen (talk \| contribs) Administrators 6,125 edits No edit summary
(2 intermediate revisions by 2 users not shown)
Line 4: \|type=[[ERROR]] \|message_desc=An event (~e~) or scenario (~s~) flag exists in the filename for which no event/scenario has been specified. For example, Flood_~e1~_001.tcf has been started with no specification for the name of event ~e1~. \|suggestions=Ensure that each event/scenario flag in the filename has a name specified using either the -e/-s run time options in the batch file, or the <font color="blue"><tt>Model Event </tt></font><font color="red"><tt>== </tt></font> and <font color="blue"><tt>Model Scenario </tt></font><font color="red"><tt>== </tt></font> .tcf commands. For more details on managing multiple events and scenarios, ~~see~~refer ~~Section~~to 4the <u>[https://docs.~~12 of 2010~~tuflow.com/classic-hpc/manual/latest/ TUFLOW ~~manual~~Manual]</u>. For details on using batch files looping to run multiple events see <u>[[Run_TUFLOW_From_a_Batch-file#Looping_in_a_batch_file \| looping in a batch file on the wiki.]]</u> <br> ~~\|prelink=[[TUFLOW_Message_0020\|Message 0020]]~~ \|uplink=[[0xxx_TUFLOW_Messages\|0xxx Messages]] ~~\|nextlink=[[TUFLOW_Message_0022\|Message 0022]]~~ }}