Difference between revisions of "TUFLOW Message 0040"
Jump to navigation
Jump to search
| (5 intermediate revisions by the same user not shown) | |||
| Line 3: | Line 3: | ||
|alt_msg=NA | |alt_msg=NA | ||
|type=[[ERROR]] | |type=[[ERROR]] | ||
| − | |message_desc=No <font color=" | + | |message_desc=No <font color="blue"><tt>End If</tt></font> command was found to close of the <font color="blue"><tt>If Scenario </tt></font><font color="red"><tt>== </tt></font> block. |
| − | |suggestions=Add the <font color=" | + | |suggestions=Add the <font color="blue"><tt>End If</tt></font> command where it is missing. |
| − | '''Tip:''' When using commands such as <font color=" | + | '''Tip:''' When using commands such as <font color="blue"><tt>If Scenario </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: |
<tt> | <tt> | ||
| − | If Scenario == 1974 | + | <font color="blue">If Scenario </font><font color="red">== </font>1974 |
| − | :Read GIS Z Shape == mi\2d_zsh_road_remove.mif | + | :<font color="blue">Read GIS Z Shape </font><font color="red">== </font> mi\2d_zsh_road_remove.mif |
| − | Else If Scenario == exg <nowiki>|</nowiki> OpA | + | <font color="blue">Else If Scenario </font><font color="red">== </font> exg <nowiki>|</nowiki> OpA |
| − | :Read GIS Z Shape == mi\2d_zsh_road_exg.mif | + | :<font color="blue">Read GIS Z Shape </font><font color="red">== </font> mi\2d_zsh_road_exg.mif |
| − | Else If Scenario == OpB | + | <font color="blue">Else If Scenario </font><font color="red">== </font> OpB |
| − | :Read GIS Z Shape == mi\2d_zsh_road_OpB.mif | + | :<font color="blue">Read GIS Z Shape </font><font color="red">== </font> mi\2d_zsh_road_OpB.mif |
| − | End If | + | <font color="blue">End If </font> |
</tt> | </tt> | ||
Other examples of commands that benefit from indenting are: | Other examples of commands that benefit from indenting are: | ||
| − | * <font color=" | + | * <font color="blue"><tt>Start 2D Domain </tt></font><font color="red"><tt>== </tt></font> |
| − | * <font color=" | + | * <font color="blue"><tt>Define Event </tt></font><font color="red"><tt>== </tt></font> |
| − | |||
| − | |||
| − | |||
| − | |||
|uplink=[[0xxx_TUFLOW_Messages|0xxx Messages]] | |uplink=[[0xxx_TUFLOW_Messages|0xxx Messages]] | ||
| − | |||
}} | }} | ||
Latest revision as of 10:03, 22 December 2022
TUFLOW Message
ERROR 0040 - No End If specified for If Scenario.
Alternate Message
NA
Message Type
ERROR
Description
No End If command was found to close of the If Scenario == block.
Suggestions
Add the End If command where it is missing.
Tip: When using commands such as If Scenario == 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:
If Scenario == 1974
- Read GIS Z Shape == mi\2d_zsh_road_remove.mif
Else If Scenario == exg | OpA
- Read GIS Z Shape == mi\2d_zsh_road_exg.mif
Else If Scenario == OpB
- Read GIS Z Shape == mi\2d_zsh_road_OpB.mif
End If
Other examples of commands that benefit from indenting are:
- Start 2D Domain ==
- Define Event ==
| Up |
|---|
 0xxx Messages
|