Difference between revisions of "TUFLOW Message 0028"
Jump to navigation
Jump to search
| Line 9: | Line 9: | ||
<tt> | <tt> | ||
| − | Define Event Name == 100y | + | <font color="blue">Define Event Name </font><font color="red">== </font>100y |
| − | :BC Event Source == _ARI_ <nowiki>|</nowiki> 100y | + | :<font color="blue">BC Event Source </font><font color="red">== </font>_ARI_ <nowiki>|</nowiki> 100y |
| − | :Output Folder == ..\results_100y | + | :<font color="blue">Output Folder </font><font color="red">== </font> ..\results_100y |
| − | End Define | + | <font color="blue">End Define</font> |
Define Event Name == 06h<br> | Define Event Name == 06h<br> | ||
Revision as of 09:57, 21 June 2022
TUFLOW Message
ERROR 0028 - No "End Define" specified for "Define Event Name == <event_name>"
Alternate Message
NA
Message Type
ERROR
Description
No End Define command was found to close of the Define Event == block for the event.
Suggestions
Check the event file. Add the End Define command where it is missing.
Tip: When using commands such as Define Event == indent the commands within the block that follows as this makes it much easier to interpret which commands apply to which event definition. For example:
Define Event Name == 100y
- BC Event Source == _ARI_ | 100y
- Output Folder == ..\results_100y
End Define
Define Event Name == 06h
- BC Event Source == _Durn_ | 06h
- End Time == 9
End Define
Other examples of commands that benefit from indenting are:
- Start 2D Domain ==
- If Scenario ==
| Up |
|---|
 0xxx Messages
|