Difference between revisions of "TUFLOW Message 2313"
m |
|||
| (6 intermediate revisions by 3 users not shown) | |||
| Line 3: | Line 3: | ||
|alt_msg=NA | |alt_msg=NA | ||
|type=[[ERROR]] | |type=[[ERROR]] | ||
| − | |message_desc=The .tcf command <font color=" | + | |message_desc=The .tcf command <font color="blue"><tt>BC Event Source </tt></font><font color="red"><tt>== </tt></font><font color="black"><tt><bc_event_text> <nowiki>|</nowiki> <bc_event_name></tt></font> is used to define BC Event Text wildcard and the BC Event Name, which is to replace it in input files. For example:<br> |
| − | <font color=" | + | <font color="blue"><tt>BC Event Source </tt></font><font color="red"><tt>== </tt></font><font color="black"><tt>~ARI~ <nowiki>|</nowiki> 020y</tt></font><br> |
| − | Will set the event text of variable of ~ARI~, this wildcard can be used in input files, for example in the "source" column of the BC database (bc_dbase). This wildcard text will be replaced by the event name <bc_event_name>. In the example command above <tt>Inflows_~ARI~ | + | Will set the event text of variable of ~ARI~, this wildcard can be used in input files, for example in the "source" column of the BC database (bc_dbase). This wildcard text will be replaced by the event name <bc_event_name>. In the example command above <tt>Inflows_~ARI~_Hydrology.csv</tt> would become <tt>Inflows_020y_Hydrology.csv</tt><br> |
| − | For more details, including examples, | + | For more details, including examples, refer to the <u>[https://docs.tuflow.com/classic-hpc/manual/latest/ TUFLOW Manual]</u>. Each occurence of <bc_event_text> must be unique for simulation. |
| + | |||
| + | This message is occuring as each <font color="blue"><tt>BC Event Source </tt></font><font color="red"><tt>== </tt></font><font color="black"><tt><bc_event_text> <nowiki>|</nowiki> <bc_event_name></tt></font> is not setting a unique <bc_event_text>. Two commands can not set set the same text wildcard (e.g. ~ARI~). | ||
| + | |suggestions= For each <font color="blue"><tt>BC Event Source </tt></font><font color="red"><tt>== </tt></font><font color="black"><tt><bc_event_text> <nowiki>|</nowiki> <bc_event_name></tt></font> command ensure that the <bc_event_text> is unique. | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
|uplink=[[2xxx_TUFLOW_Messages|2xxx Messages]] | |uplink=[[2xxx_TUFLOW_Messages|2xxx Messages]] | ||
| − | |||
}} | }} | ||
Latest revision as of 09:52, 23 September 2024
TUFLOW Message
ERROR 2313 - Event Source Text ",a," used more than once.
Alternate Message
NA
Message Type
ERROR
Description
The .tcf command BC Event Source == <bc_event_text> | <bc_event_name> is used to define BC Event Text wildcard and the BC Event Name, which is to replace it in input files. For example:
BC Event Source == ~ARI~ | 020y
Will set the event text of variable of ~ARI~, this wildcard can be used in input files, for example in the "source" column of the BC database (bc_dbase). This wildcard text will be replaced by the event name <bc_event_name>. In the example command above Inflows_~ARI~_Hydrology.csv would become Inflows_020y_Hydrology.csv
For more details, including examples, refer to the TUFLOW Manual. Each occurence of <bc_event_text> must be unique for simulation.
This message is occuring as each BC Event Source == <bc_event_text> | <bc_event_name> is not setting a unique <bc_event_text>. Two commands can not set set the same text wildcard (e.g. ~ARI~).
Suggestions
For each BC Event Source == <bc_event_text> | <bc_event_name> command ensure that the <bc_event_text> is unique.
| Up |
|---|
 2xxx Messages
|