Difference between revisions of "TUFLOW Message 2313"

From Tuflow
Jump to navigation Jump to search
 
(2 intermediate revisions by one other user not shown)
Line 7: Line 7:
 
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>
 
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, see Section 4.12 of 2010 TUFLOW manual. Each occurence of <bc_event_text> must be unique for simulation.
+
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~).
 
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.
 
|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.
|discussion_page=* [[Talk:TUFLOW Message 2313|Discuss Message 2313]]
+
 
|link3=''
 
|link4=''
 
|prelink=[[TUFLOW_Message_2311|Message 2311]]
 
 
|uplink=[[2xxx_TUFLOW_Messages|2xxx Messages]]
 
|uplink=[[2xxx_TUFLOW_Messages|2xxx Messages]]
|nextlink=[[TUFLOW_Message_2314|Message 2314]]
 
 
}}
 
}}

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