Revision as of 15:27, 4 August 2011 view source Bill Syme (talk \| contribs) Bureaucrats, Administrators 461 edits No edit summary ← Older edit		Revision as of 15:33, 4 August 2011 view source Bill Syme (talk \| contribs) Bureaucrats, Administrators 461 edits No edit summary Newer edit →
Line 1: {{TUFLOW_Message \|tuflow_message=ERROR 0021 - No Event/Scenario name specified for -e/s<#> in input filename. \|alt_msg=NA \|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 ~~an event~~a name specified using either the -e/-s run time ~~option~~options, or the <font color="green"><tt>Model Event == </tt></font> ~~command~~and <font color="green"><tt>Model Scenario == </tt></font> .tcf commands. For more details on managing multiple events and scenarios see Section 4.12 of 2010 TUFLOW manual. \|discussion_page=* [[Talk:TUFLOW Message 0021\|Discuss Message 0021]] \|link3=''

TUFLOW Message 0021: Difference between revisions