Difference between revisions of "TUFLOW Message 0029"
Jump to navigation
Jump to search
| Line 8: | Line 8: | ||
Tip: When using commands such as <font color="green"><tt>Define Event ==</tt></font> indent the commands that follow. For example: | Tip: When using commands such as <font color="green"><tt>Define Event ==</tt></font> indent the commands that follow. For example: | ||
| − | <tt>Define Event Name == 100y | + | <tt>Define Event Name == 100y<br> |
| − | + | BC Event Source == _ARI_ <nowiki>|</nowiki> 100y<br> | |
| − | + | Output Folder == ..\results_100y | |
End Define | End Define | ||
Revision as of 21:04, 4 August 2011
TUFLOW Message
ERROR 0029 - "End Define" found in incorrect location.
Alternate Message
NA
Message Type
ERROR
Description
An End Define command was found outside a Define Event == / End Define block.
Suggestions
Scan the console window or .tlf file to establish where TUFLOW is in the event file. Check the event file and locate the problematic End Define.
Tip: When using commands such as Define Event == indent the commands that follow. 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 ==
| Up |
|---|
 0xxx Messages
|