Difference between revisions of "TUFLOW Message 3201"

From Tuflow
Jump to navigation Jump to search
Line 5: Line 5:
  
 
|type=[[ERROR]]  
 
|type=[[ERROR]]  
|message_desc=<font color="blue"><tt>Quadtree BC Parallel Inertia Approach </tt></font><font color="red"><tt>== </tt></font><font color="black"><tt>Method B</tt></font> Materials may use use either fixed mannings, depth-varying mannings, or log-law roughness formulations for bed resistance.
+
|message_desc=<font color="blue"><tt>Quadtree BC Parallel Inertia Approach </tt></font><font color="red"><tt>== </tt></font><font color="black"><tt>Method B</tt></font> extracts velocities from faces parallel to the model boundary (“QT”, “HT” and “HX” types) to calculate the transverse momentum, or parallel inertia at the boundary. For example, to calculate the parallel inertia at the face highlighted by orange circle in the image below, the transverse velocity from the non-BC-face below is needed. However, if the boundary cells are distributed across multiple CPU or GPU devices (illustrated by the red dot line), it can require velocity information from a face within another device. This could cause memory access violation during the simulation, thus the ERROR message is generated to stop the simulation.
When utilising log-law roughness, a maximum limit for equivalent mannings number is required as the formulation becomes singular at shallow depths.
 
This limit, provided as the fixed mannings n value in the material data, must be greater than zero.
 
  
 
[[File:Proxy face error.PNG|600px|caption]]
 
[[File:Proxy face error.PNG|600px|caption]]
  
|suggestions=Ensure that all materials that utilise log-law roughness have positive values for mannings n.
+
|suggestions=Revise quadtree refinement polygon to ensure the cell size does not change immediately inside the model boundary. The image below shows a good example, where 2 rows of cells have the same size and this ensures the face the boundary faces selected by the <font color="blue"><tt>Quadtree BC Parallel Inertia Approach </tt></font><font color="red"><tt>== </tt></font><font color="black"><tt>Method B</tt></font> are always within the same CPU/GPU device.
 +
 
 +
[[File:Proxy face error fix.PNG|600px|caption]]
  
 
|uplink=[[3xxx_TUFLOW_Messages|3xxx Messages]]
 
|uplink=[[3xxx_TUFLOW_Messages|3xxx Messages]]
 
}}
 
}}

Revision as of 12:39, 10 July 2025

TUFLOW Message
ERROR 3201: Error in U face proxy: face <id>, proxy face = <id>, proxy cells <id> and <id> not within the same sub-subdomain

Alternate Message
NA

Message Type
ERROR

Description
Quadtree BC Parallel Inertia Approach == Method B extracts velocities from faces parallel to the model boundary (“QT”, “HT” and “HX” types) to calculate the transverse momentum, or parallel inertia at the boundary. For example, to calculate the parallel inertia at the face highlighted by orange circle in the image below, the transverse velocity from the non-BC-face below is needed. However, if the boundary cells are distributed across multiple CPU or GPU devices (illustrated by the red dot line), it can require velocity information from a face within another device. This could cause memory access violation during the simulation, thus the ERROR message is generated to stop the simulation.

caption

Suggestions
Revise quadtree refinement polygon to ensure the cell size does not change immediately inside the model boundary. The image below shows a good example, where 2 rows of cells have the same size and this ensures the face the boundary faces selected by the Quadtree BC Parallel Inertia Approach == Method B are always within the same CPU/GPU device.

caption


Up
Go-up.png 3xxx Messages