Difference between revisions of "TUFLOW Message 0029"
Jump to navigation
Jump to search
| Line 10: | Line 10: | ||
<tt> | <tt> | ||
Define Event Name == 100y | Define Event Name == 100y | ||
| − | + | :BC Event Source == _ARI_ <nowiki>|</nowiki> 100y | |
| − | + | :Output Folder == ..\results_100y | |
End Define | End Define | ||
Define Event Name == 06h<br> | Define Event Name == 06h<br> | ||
| − | + | :BC Event Source == _Durn_ <nowiki>|</nowiki> 06h | |
| − | + | :End Time == 9 | |
End Define</tt> | End Define</tt> | ||
Revision as of 08:14, 5 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 ==
- If Scenario ==
| Up |
|---|
 0xxx Messages
|