Difference between revisions of "TUFLOW Message 0028"

From Tuflow
Jump to navigation Jump to search
Line 5: Line 5:
 
|message_desc=No <font color="green"><tt>End Define</tt></font> command was found to close of the <font color="green"><tt>Define Event == </tt></font> block for the event.
 
|message_desc=No <font color="green"><tt>End Define</tt></font> command was found to close of the <font color="green"><tt>Define Event == </tt></font> block for the event.
 
|suggestions=Check the event file.  Add the <font color="green"><tt>End Define</tt></font> command where it is missing.
 
|suggestions=Check the event file.  Add the <font color="green"><tt>End Define</tt></font> command where it is missing.
 +
 +
'''Tip:''' When using commands such as <font color="green"><tt>Define Event ==</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:
 +
 +
<tt>
 +
Define Event Name == 100y
 +
:BC Event Source == _ARI_ <nowiki>|</nowiki> 100y
 +
:Output Folder == ..\results_100y
 +
End Define
 +
 +
Define Event Name == 06h<br>
 +
:BC Event Source == _Durn_ <nowiki>|</nowiki> 06h
 +
:End Time == 9
 +
End Define</tt>
 +
 +
Other examples of commands that benefit from indenting are:
 +
* <font color="green"><tt>Start 2D Domain ==</tt></font>
 +
* <font color="green"><tt>If Scenario ==</tt></font>
 +
 
|discussion_page=* [[Talk:TUFLOW Message 0028|Discuss Message 0028]]
 
|discussion_page=* [[Talk:TUFLOW Message 0028|Discuss Message 0028]]
 
|link3=''
 
|link3=''

Revision as of 11:09, 10 August 2011

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
Go-up.png 0xxx Messages