TUFLOW Message 0028: Difference between revisions
Jump to navigation
Jump to search
Content deleted Content added
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
{{TUFLOW_Message |
{{TUFLOW_Message |
||
|tuflow_message=ERROR 0028 - No "End Define" specified for "Define Event Name == |
|tuflow_message=ERROR 0028 - No "End Define" specified for "Define Event Name == <event_name>" |
||
|alt_msg=NA |
|alt_msg=NA |
||
|type=[[ERROR]] |
|type=[[ERROR]] |
||
Revision as of 14:47, 15 July 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
|