TUFLOW Message 2835: Difference between revisions
Jump to navigation
Jump to search
Content deleted Content added
No edit summary |
No edit summary |
||
| (4 intermediate revisions by 4 users not shown) | |||
| Line 5: | Line 5: | ||
|type=[[ERROR]] |
|type=[[ERROR]] |
||
|message_desc=Not expecting point / line / region for |
|message_desc=Not expecting point / line / region for BC type: "<>". A point / line / region is not valid for the boundary condition (BC) type "<>". |
||
<br> |
|||
|suggestions=Please contact [mailto:support@tuflow.com support@tuflow.com]. |
|||
From the 2023-03 release, a point-type QT boundary is not supported when using TUFLOW Classic / HPC (bringing the behaviour in line with Quadtree). |
|||
|suggestions=*Refer to the <u>[https://docs.tuflow.com/classic-hpc/manual/latest/ TUFLOW Manual]</u> for information on the BC type "<>" and its specifications. |
|||
*If a QT point was intended to be used as an internal inflow boundary, transitioning to a 2d_sa setup is recommended. For an external boundary, the preferred approach is to use a 2d_bc QT line snapped to the code polygon. |
|||
|prelink=[[TUFLOW_Message_2834|Message 2834]] |
|||
|uplink=[[2xxx_TUFLOW_Messages|2xxx Messages]] |
|uplink=[[2xxx_TUFLOW_Messages|2xxx Messages]] |
||
|nextlink=[[TUFLOW_Message_2836|Message 2836]] |
|||
}} |
}} |
||
Latest revision as of 17:15, 7 February 2025
TUFLOW Message
ERROR 2835 - Not expecting point for bc type: "<>".
Alternate Message
ERROR 2835 - Not expecting line for bc type: "<>".
ERROR 2835 - Not expecting region for bc type: "<>".
Message Type
ERROR
Description
Not expecting point / line / region for BC type: "<>". A point / line / region is not valid for the boundary condition (BC) type "<>".
From the 2023-03 release, a point-type QT boundary is not supported when using TUFLOW Classic / HPC (bringing the behaviour in line with Quadtree).
Suggestions
- Refer to the TUFLOW Manual for information on the BC type "<>" and its specifications.
- If a QT point was intended to be used as an internal inflow boundary, transitioning to a 2d_sa setup is recommended. For an external boundary, the preferred approach is to use a 2d_bc QT line snapped to the code polygon.
| Up |
|---|
 2xxx Messages
|