TUFLOW Message 0028: Difference between revisions
Jump to navigation
Jump to search
Content deleted Content added
Created page with '{{TUFLOW_Message |tuflow_message=ERROR 0028 - No "End Define" specified for "Define Event Name == ",a, |alt_msg=NA |type=ERROR |message_desc=???? |suggestions=???? |discussio...' |
No edit summary |
||
| (10 intermediate revisions by 2 users not shown) | |||
| 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]] |
||
|message_desc=No <font color="blue"><tt>End Define</tt></font> command was found to close of the <font color="blue"><tt>Define Event </tt></font><font color="red"><tt>== </tt></font> block for the event. |
|||
|message_desc=???? |
|||
|suggestions=Check the event file. Add the <font color="blue"><tt>End Define</tt></font> command where it is missing. |
|||
|suggestions=???? |
|||
|discussion_page=* [[Talk:TUFLOW Message 0028|Discuss Message 0028]] |
|||
'''Tip:''' When using commands such as <font color="blue"><tt>Define Event </tt></font><font color="red"><tt>== </tt></font> 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: |
|||
|link3='' |
|||
|link4='' |
|||
<tt> |
|||
|prelink=[[TUFLOW_Message_0027|Message 0027]] |
|||
<font color="blue">Define Event Name </font><font color="red">== </font>100y |
|||
:<font color="blue">BC Event Source </font><font color="red">== </font>_ARI_ <nowiki>|</nowiki> 100y |
|||
:<font color="blue">Output Folder </font><font color="red">== </font> ..\results_100y |
|||
<font color="blue">End Define</font> |
|||
<font color="blue">Define Event Name </font><font color="red">== </font>06h<br> |
|||
:<font color="blue">BC Event Source </font><font color="red">== </font> _Durn_ <nowiki>|</nowiki> 06h |
|||
:<font color="blue">End Time </font><font color="red">== </font> 9 |
|||
<font color="blue">End Define</font></tt> |
|||
Other examples of commands that benefit from indenting are: |
|||
* <font color="blue"><tt>Start 2D Domain </tt></font><font color="red"><tt>== </tt></font> |
|||
* <font color="blue"><tt>If Scenario </tt></font><font color="red"><tt>== </tt></font> |
|||
|uplink=[[0xxx_TUFLOW_Messages|0xxx Messages]] |
|uplink=[[0xxx_TUFLOW_Messages|0xxx Messages]] |
||
|nextlink=[[TUFLOW_Message_0029|Message 0029]] |
|||
}} |
}} |
||
Latest revision as of 09:59, 22 December 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
|