TUFLOW Message 0021: Difference between revisions
| No edit summary | No edit summary | ||
| (One intermediate revision by one other user not shown) | |||
| Line 6: | Line 6: | ||
| |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. | |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  | For more details on managing multiple events and scenarios, refer to the <u>[https://docs.tuflow.com/classic-hpc/manual/latest/ TUFLOW 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> | 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> | <br> | ||
| |prelink=[[TUFLOW_Message_0020|Message 0020]] | |||
| |uplink=[[0xxx_TUFLOW_Messages|0xxx Messages]] | |uplink=[[0xxx_TUFLOW_Messages|0xxx Messages]] | ||
| |nextlink=[[TUFLOW_Message_0022|Message 0022]] | |||
| }} | }} | ||
Latest revision as of 09:52, 23 September 2024
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 in the batch file, or the Model Event ==  and Model Scenario ==  .tcf commands.
For more details on managing multiple events and scenarios, refer to the 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 |