TUFLOW Message 2216 - Revision history

Emilie Nielsen at 23:16, 22 September 2024

2024-09-22T23:16:10Z

← Older revision		Revision as of 09:16, 23 September 2024
Line 3:		Line 3:
	\|alt_msg=NA		\|alt_msg=NA
	\|type=[[ERROR]]		\|type=[[ERROR]]
	\|message_desc=TUFLOW automatically connects 1D pit objects to 2D cells using a on-grade or sag approach. TUFLOW has been unable to find enough active cells to connect pit to. For more details on connecting 1D pits to 2D domain ~~see~~ ~~Section~~ 4.5.~~1.3 of 2010~~ TUFLOW ~~manual~~.		\|message_desc=TUFLOW automatically connects 1D pit objects to 2D cells using a on-grade or sag approach. TUFLOW has been unable to find enough active cells to connect pit to. For more details on connecting 1D pits to 2D domain, refer to the <u>[https://docs.tuflow.com/classic-hpc/manual/latest/ TUFLOW Manual]</u>.
	\|suggestions=Review pit location, active 2D cells and number of cells TUFLOW is connecting to. The number of cells automatically connects to can be controlled with the Conn_No attribute in the 1d_nwk layer. Alternatively a '''SX''' boundary can be manually specified in a 2d_bc layer, this gives the user control over the cells connected to the pit.		\|suggestions=Review pit location, active 2D cells and number of cells TUFLOW is connecting to. The number of cells automatically connects to can be controlled with the Conn_No attribute in the 1d_nwk layer. Alternatively a '''SX''' boundary can be manually specified in a 2d_bc layer, this gives the user control over the cells connected to the pit.

Melissa.Moghanloo at 04:12, 7 February 2023

2023-02-07T04:12:07Z

← Older revision		Revision as of 14:12, 7 February 2023
Line 6:		Line 6:
	\|suggestions=Review pit location, active 2D cells and number of cells TUFLOW is connecting to. The number of cells automatically connects to can be controlled with the Conn_No attribute in the 1d_nwk layer. Alternatively a '''SX''' boundary can be manually specified in a 2d_bc layer, this gives the user control over the cells connected to the pit.		\|suggestions=Review pit location, active 2D cells and number of cells TUFLOW is connecting to. The number of cells automatically connects to can be controlled with the Conn_No attribute in the 1d_nwk layer. Alternatively a '''SX''' boundary can be manually specified in a 2d_bc layer, this gives the user control over the cells connected to the pit.

	\|prelink=[[TUFLOW_Message_2215\|Message 2215]]
	\|uplink=[[2xxx_TUFLOW_Messages\|2xxx Messages]]		\|uplink=[[2xxx_TUFLOW_Messages\|2xxx Messages]]
	\|nextlink=[[TUFLOW_Message_2217\|Message 2217]]
	}}		}}

Melissa.Moghanloo at 04:25, 6 July 2022

2022-07-06T04:25:38Z

← Older revision		Revision as of 14:25, 6 July 2022
Line 5:		Line 5:
	\|message_desc=TUFLOW automatically connects 1D pit objects to 2D cells using a on-grade or sag approach. TUFLOW has been unable to find enough active cells to connect pit to. For more details on connecting 1D pits to 2D domain see Section 4.5.1.3 of 2010 TUFLOW manual.		\|message_desc=TUFLOW automatically connects 1D pit objects to 2D cells using a on-grade or sag approach. TUFLOW has been unable to find enough active cells to connect pit to. For more details on connecting 1D pits to 2D domain see Section 4.5.1.3 of 2010 TUFLOW manual.
	\|suggestions=Review pit location, active 2D cells and number of cells TUFLOW is connecting to. The number of cells automatically connects to can be controlled with the Conn_No attribute in the 1d_nwk layer. Alternatively a '''SX''' boundary can be manually specified in a 2d_bc layer, this gives the user control over the cells connected to the pit.		\|suggestions=Review pit location, active 2D cells and number of cells TUFLOW is connecting to. The number of cells automatically connects to can be controlled with the Conn_No attribute in the 1d_nwk layer. Alternatively a '''SX''' boundary can be manually specified in a 2d_bc layer, this gives the user control over the cells connected to the pit.

	\|discussion_page=* [[Talk:TUFLOW Message 2216\|Discuss Message 2216]]
	\|link3=''
	\|link4=''
	\|prelink=[[TUFLOW_Message_2215\|Message 2215]]		\|prelink=[[TUFLOW_Message_2215\|Message 2215]]
	\|uplink=[[2xxx_TUFLOW_Messages\|2xxx Messages]]		\|uplink=[[2xxx_TUFLOW_Messages\|2xxx Messages]]

tuflow>Par at 02:19, 18 February 2011

2011-02-18T02:19:10Z

← Older revision		Revision as of 12:19, 18 February 2011
Line 3:		Line 3:
	\|alt_msg=NA		\|alt_msg=NA
	\|type=[[ERROR]]		\|type=[[ERROR]]
			\|message_desc=TUFLOW automatically connects 1D pit objects to 2D cells using a on-grade or sag approach. TUFLOW has been unable to find enough active cells to connect pit to. For more details on connecting 1D pits to 2D domain see Section 4.5.1.3 of 2010 TUFLOW manual.
	\|message_desc=????
			\|suggestions=Review pit location, active 2D cells and number of cells TUFLOW is connecting to. The number of cells automatically connects to can be controlled with the Conn_No attribute in the 1d_nwk layer. Alternatively a '''SX''' boundary can be manually specified in a 2d_bc layer, this gives the user control over the cells connected to the pit.
	\|suggestions=????
	\|discussion_page=* [[Talk:TUFLOW Message 2216\|Discuss Message 2216]]		\|discussion_page=* [[Talk:TUFLOW Message 2216\|Discuss Message 2216]]
	\|link3=''		\|link3=''

tuflow>Par: Created page with '{{TUFLOW_Message |tuflow_message=ERROR 2216 - Could not find enough 2D cells to spread 1D pit connection over. |alt_msg=NA |type=ERROR |message_desc=???? |suggestions=???? |d...'

2010-10-01T02:24:32Z

Created page with '{{TUFLOW_Message |tuflow_message=ERROR 2216 - Could not find enough 2D cells to spread 1D pit connection over. |alt_msg=NA |type=ERROR |message_desc=???? |suggestions=???? |d...'

New page

{{TUFLOW_Message
|tuflow_message=ERROR 2216 - Could not find enough 2D cells to spread 1D pit connection over.
|alt_msg=NA
|type=[[ERROR]]
|message_desc=????
|suggestions=????
|discussion_page=* [[Talk:TUFLOW Message 2216|Discuss Message 2216]]
|link3=''
|link4=''
|prelink=[[TUFLOW_Message_2215|Message 2215]]
|uplink=[[2xxx_TUFLOW_Messages|2xxx Messages]]
|nextlink=[[TUFLOW_Message_2217|Message 2217]]
}}