Difference between revisions of "TUFLOW Message 0021"
Jump to navigation
Jump to search
| Line 1: | Line 1: | ||
{{TUFLOW_Message | {{TUFLOW_Message | ||
| − | |tuflow_message=ERROR 0021 - No Event name specified for -e<#> in input filename. | + | |tuflow_message=ERROR 0021 - No Event/Scenario name specified for -e/s<#> in input filename. |
|alt_msg=NA | |alt_msg=NA | ||
|type=[[ERROR]] | |type=[[ERROR]] | ||
| − | |message_desc=An event flag exists in the filename for which no event has been specified. For example, Flood_~e1~_001.tcf has been started with no specification for the name of event ~e1~. | + | |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 flag in the filename has | + | |suggestions=Ensure that each event/scenario flag in the filename has a name specified using either the -e/-s run time options, or the <font color="green"><tt>Model Event == </tt></font> 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]] | |discussion_page=* [[Talk:TUFLOW Message 0021|Discuss Message 0021]] | ||
|link3='' | |link3='' | ||
Revision as of 15:33, 4 August 2011
TUFLOW Message
ERROR 0021 - No Event/Scenario name specified for -e/s<#> in input filename.
Alternate Message
NA
Message Type
ERROR
Description
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, or the Model Event == and Model Scenario == .tcf commands.
For more details on managing multiple events and scenarios see Section 4.12 of 2010 TUFLOW manual.
| Up |
|---|
 0xxx Messages
|