Difference between revisions of "TUFLOW Message 2320"

Latest revision as of 02:21, 29 May 2024

TUFLOW Message
ERROR 2320 - FC commands not yet supported in HPC or GPU solver.

Alternate Message
ERROR 2320 - Read TGF command not yet supported in HPC or GPU solver.
ERROR 2320 - Read TGA command not yet supported in HPC or GPU solver.
ERROR 2320 - TUFLOW 2016-03 GPU Solver does not support 1D links.
ERROR 2320 - GLO commands not yet supported in HPC or GPU solver.
WARNING 2320 - HPC or GPU Solver ignoring Read GIS Objects/Receptors commands.

Message Type
WARNING
ERROR

Description
Some TUFLOW Classic functionalities are not supported by the TUFLOW HPC solver.

Suggestions

If using a 2d_fc layer, change to a 2d_lfcsh layer which is supported by TUFLOW HPC.
The 2016-03 TUFLOW GPU solver is a legacy feature, TUFLOW HPC (on GPU hardware) should be used instead.
GLO commands are supported in TUFLOW HPC from the 2023-03-AD build and onwards.
Read GIS Objects/Receptors commands are supported in TUFLOW HPC from the 2023-03-AA build and onwards.

Up
2xxx Messages

@@ Line 1: / Line 1: @@
 {{TUFLOW_Message
-|tuflow_message=ERROR 2313 - Event Source Text ",a," used more than once.
+|tuflow_message=ERROR 2320 - FC commands not yet supported in HPC or GPU solver.
-|alt_msg=NA
+|alt_msg=ERROR 2320 - Read TGF command not yet supported in HPC or GPU solver.<br>
-|type=[[ERROR]]
+ERROR 2320 - Read TGA command not yet supported in HPC or GPU solver.<br>
-|message_desc=The .tcf command <font color="green"><tt>BC Event Source == <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>
+ERROR 2320 - TUFLOW 2016-03 GPU Solver does not support 1D links.<br>
-<font color="green"><tt>BC Event Source == ~ARI~ <nowiki>|</nowiki> 020y</tt></font><br>
+ERROR 2320 - GLO commands not yet supported in HPC or GPU solver.<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>
+WARNING 2320 - HPC or GPU Solver ignoring Read GIS Objects/Receptors commands.<br>
+|type=[[WARNING]]<br>
+[[ERROR]]<br>
+|message_desc= Some TUFLOW Classic functionalities are not supported by the TUFLOW HPC solver.
-For more details, including examples, see Section 4.12 of 2010 TUFLOW manual. Each occurence of <bc_event_text> must be unique for simulation.
+|suggestions=
+* If using a 2d_fc layer, change to a 2d_lfcsh layer which is supported by TUFLOW HPC.
+* The 2016-03 TUFLOW GPU solver is a legacy feature, TUFLOW HPC (on GPU hardware) should be used instead.
+* GLO commands are supported in TUFLOW HPC from the 2023-03-AD build and onwards.
+* Read GIS Objects/Receptors commands are supported in TUFLOW HPC from the 2023-03-AA build and onwards.
-This message is occuring as each <font color="green"><tt>BC Event Source == <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="green"><tt>BC Event Source == <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]]
-|nextlink=[[TUFLOW_Message_2320|Message 2320]]
 }}

Difference between revisions of "TUFLOW Message 2320"

Latest revision as of 02:21, 29 May 2024

Navigation menu

Search