Difference between revisions of "TUFLOW Message 0021"
Melissa1987 (talk | contribs) |
Melissa1987 (talk | contribs) |
||
| Line 9: | Line 9: | ||
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> | 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]] | |prelink=[[TUFLOW_Message_0020|Message 0020]] | ||
|uplink=[[0xxx_TUFLOW_Messages|0xxx Messages]] | |uplink=[[0xxx_TUFLOW_Messages|0xxx Messages]] | ||
|nextlink=[[TUFLOW_Message_0022|Message 0022]] | |nextlink=[[TUFLOW_Message_0022|Message 0022]] | ||
}} | }} | ||
Revision as of 12:00, 1 July 2022
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.
For details on using batch files looping to run multiple events see looping in a batch file on the wiki.
| Up |
|---|
 0xxx Messages
|