Check Files 1d pit A - Revision history

Emilie Nielsen at 00:21, 23 September 2024

2024-09-23T00:21:59Z

← Older revision		Revision as of 10:21, 23 September 2024
Line 9:		Line 9:
	\| ID\|\|The pit ID.		\| ID\|\|The pit ID.
	\|-		\|-
	\| Type\|\|The pit type, see the <u>[https://~~downloads~~.tuflow.com/~~TUFLOW~~/~~Releases~~/~~Latest~~/~~TUFLOW%20Manual.pdf~~ TUFLOW Manual]</u> for a list of pit types.<br>		\| Type\|\|The pit type, see the <u>[https://docs.tuflow.com/classic-hpc/manual/latest/ TUFLOW Manual]</u> for a list of pit types.<br>
	For example a "Q" stands Q pit, while a "Q(VPI)" type is a Virtual Pipe Inlet.		For example a "Q" stands Q pit, while a "Q(VPI)" type is a Virtual Pipe Inlet.
	\|-		\|-

Emilie Nielsen at 04:39, 6 August 2024

2024-08-06T04:39:39Z

← Older revision		Revision as of 14:39, 6 August 2024
Line 9:		Line 9:
	\| ID\|\|The pit ID.		\| ID\|\|The pit ID.
	\|-		\|-
	\| Type\|\|The pit type, see the <u>[https://downloads.tuflow.com/TUFLOW/Releases/Latest/TUFLOW%20Manual.pdf TUFLOW Manual]</u> for a list of pit types.<br> ~~For example a "Q" stands Q pit, while a "Q(VPI)" type is a Virtual Pipe Inlet.~~		\| Type\|\|The pit type, see the <u>[https://downloads.tuflow.com/TUFLOW/Releases/Latest/TUFLOW%20Manual.pdf TUFLOW Manual]</u> for a list of pit types.<br>
			For example a "Q" stands Q pit, while a "Q(VPI)" type is a Virtual Pipe Inlet.
	\|-		\|-
	\| VP_Network_ID\|\| Virtual Pipe Network ID (as an integer) used to determine which outlet(s) the flow into the inlet pits discharges from.		\| VP_Network_ID\|\| Virtual Pipe Network ID (as an integer) used to determine which outlet(s) the flow into the inlet pits discharges from.
Line 30:		Line 31:
	\|-		\|-
	\| Lag_Approach\|\|Sets the lag approach. <br>		\| Lag_Approach\|\|Sets the lag approach. <br>
	*"None" or blank - No lag is applied.		*'''None''' or blank: No lag is applied.
	*"Shift~~" -~~ Shift method applied.		*'''Shift''': Shift method applied.
	*"Decay~~" -~~ Decay method applied.		*'''Decay''': Decay method applied.
	\|-		\|-
	\| Lag_Value\|\|Lag value in hours.		\| Lag_Value\|\|Lag value in hours.
Line 40:		Line 41:
	\| Q_factor\|\|This is the multiplication factor applied to the discharge to allow for any blockage and/or if Number_of pits is greater than 1.		\| Q_factor\|\|This is the multiplication factor applied to the discharge to allow for any blockage and/or if Number_of pits is greater than 1.
	\|-		\|-
	\| i_1d_layer\|\|The integer index of the GIS layer that the pit came from. For example an ~~'''i_1d_layer'''~~ value of 4 would be the 4th input layer (1d_nwk_M08_pits_001) below.<br>		\| i_1d_layer\|\|The integer index of the GIS layer that the pit came from. For example an i_1d_nwk value of 4 would be the 4th input layer (1d_nwk_M08_pits_001) below.<br>
	<font color="blue"><tt>Read GIS Pits </tt></font> <font color="red"><tt>==</tt></font><tt> ~~gis\1d_nwk_M04_pits_001.shp~~</tt><br>		<font color="blue"><tt>Read GIS Pits </tt></font> <font color="red"><tt>==</tt></font><tt> 1d_nwk_M04_pits_001_P</tt><br>
	<font color="blue"><tt>Read GIS Pits </tt></font> <font color="red"><tt>==</tt></font><tt> ~~gis\1d_nwk_M05_pits_001.shp~~</tt><br>		<font color="blue"><tt>Read GIS Pits </tt></font> <font color="red"><tt>==</tt></font><tt> 1d_nwk_M05_pits_001_P</tt><br>
	<font color="blue"><tt>Read GIS Pits </tt></font> <font color="red"><tt>==</tt></font><tt> ~~gis\1d_nwk_M07_pits_998.shp~~</tt><br>		<font color="blue"><tt>Read GIS Pits </tt></font> <font color="red"><tt>==</tt></font><tt> 1d_nwk_M07_pits_998_P</tt><br>
	<font color="blue"><tt>Read GIS Pits </tt></font> <font color="red"><tt>==</tt></font><tt> ~~gis\1d_nwk_M08_pits_001.shp~~</tt>		<font color="blue"><tt>Read GIS Pits </tt></font> <font color="red"><tt>==</tt></font><tt> 1d_nwk_M08_pits_001_P</tt>

	\|}		\|}


			{{Tips Navigation
			\|uplink=[[TUFLOW_Check_Files \| TUFLOW Check Files]]
			}}

Emilie Nielsen at 00:35, 30 July 2024

2024-07-30T00:35:13Z

← Older revision		Revision as of 10:35, 30 July 2024
Line 9:		Line 9:
	\| ID\|\|The pit ID.		\| ID\|\|The pit ID.
	\|-		\|-
	\| Type\|\|The pit type, see TUFLOW ~~manual~~ for a list of pit types.<br> For example a "Q" stands Q pit, while a "Q(VPI)" type is a Virtual Pipe Inlet.		\| Type\|\|The pit type, see the <u>[https://downloads.tuflow.com/TUFLOW/Releases/Latest/TUFLOW%20Manual.pdf TUFLOW Manual]</u> for a list of pit types.<br> For example a "Q" stands Q pit, while a "Q(VPI)" type is a Virtual Pipe Inlet.
	\|-		\|-
	\| VP_Network_ID\|\| Virtual Pipe Network ID (as an integer) used to determine which outlet(s) the flow into the inlet pits discharges from.		\| VP_Network_ID\|\| Virtual Pipe Network ID (as an integer) used to determine which outlet(s) the flow into the inlet pits discharges from.
Line 28:		Line 28:
	\|-		\|-
	\| Number_of\|\|The number of pits.		\| Number_of\|\|The number of pits.
			\|-
			\| Lag_Approach\|\|Sets the lag approach. <br>
			*"None" or blank - No lag is applied.
			*"Shift" - Shift method applied.
			*"Decay" - Decay method applied.
			\|-
			\| Lag_Value\|\|Lag value in hours.
	\|-		\|-
	\| Invert\|\|The elevation from the 2D cell the pit connects to or that entered via a 1d_nwk layer.		\| Invert\|\|The elevation from the 2D cell the pit connects to or that entered via a 1d_nwk layer.
Line 34:		Line 41:
	\|-		\|-
	\| i_1d_layer\|\|The integer index of the GIS layer that the pit came from. For example an '''i_1d_layer''' value of 4 would be the 4th input layer (1d_nwk_M08_pits_001) below.<br>		\| i_1d_layer\|\|The integer index of the GIS layer that the pit came from. For example an '''i_1d_layer''' value of 4 would be the 4th input layer (1d_nwk_M08_pits_001) below.<br>
	<font color="blue"><tt>Read GIS Pits </tt></font> <font color="red"><tt>==</tt></font><tt> mi\1d_nwk_M04_pits_001.~~MIF~~</tt><br>		<font color="blue"><tt>Read GIS Pits </tt></font> <font color="red"><tt>==</tt></font><tt> gis\1d_nwk_M04_pits_001.shp</tt><br>
	<font color="blue"><tt>Read GIS Pits </tt></font> <font color="red"><tt>==</tt></font><tt> mi\1d_nwk_M05_pits_001.~~MIF~~</tt><br>		<font color="blue"><tt>Read GIS Pits </tt></font> <font color="red"><tt>==</tt></font><tt> gis\1d_nwk_M05_pits_001.shp</tt><br>
	<font color="blue"><tt>Read GIS Pits </tt></font> <font color="red"><tt>==</tt></font><tt> mi\1d_nwk_M07_pits_998.~~MIF~~</tt><br>		<font color="blue"><tt>Read GIS Pits </tt></font> <font color="red"><tt>==</tt></font><tt> gis\1d_nwk_M07_pits_998.shp</tt><br>
	<font color="blue"><tt>Read GIS Pits </tt></font> <font color="red"><tt>==</tt></font><tt> mi\1d_nwk_M08_pits_001.~~MIF~~</tt>		<font color="blue"><tt>Read GIS Pits </tt></font> <font color="red"><tt>==</tt></font><tt> gis\1d_nwk_M08_pits_001.shp</tt>

	\|}		\|}

ShuangGao at 03:38, 7 January 2019

2019-01-07T03:38:35Z

← Older revision		Revision as of 13:38, 7 January 2019
Line 9:		Line 9:
	\| ID\|\|The pit ID.		\| ID\|\|The pit ID.
	\|-		\|-
	\| Type\|\|The pit type, see TUFLOW manual for a list of pit types.<br> For example an "Q" ~~type pit is a standard~~ Q pit, while an "Q(VPI)" type is a Virtual Pipe Inlet.		\| Type\|\|The pit type, see TUFLOW manual for a list of pit types.<br> For example a "Q" stands Q pit, while a "Q(VPI)" type is a Virtual Pipe Inlet.
	\|-		\|-
	\| VP_Network_ID\|\| Virtual Pipe Network ID (as an integer) used to determine which outlet(s) the flow into the inlet pits discharges from.		\| VP_Network_ID\|\| Virtual Pipe Network ID (as an integer) used to determine which outlet(s) the flow into the inlet pits discharges from.

ShuangGao at 03:27, 7 January 2019

2019-01-07T03:27:44Z

← Older revision		Revision as of 13:27, 7 January 2019
Line 9:		Line 9:
	\| ID\|\|The pit ID.		\| ID\|\|The pit ID.
	\|-		\|-
	\| Type\|\|The pit type, see TUFLOW manual for a list of pit types.<br>		\| Type\|\|The pit type, see TUFLOW manual for a list of pit types.<br> For example an "Q" type pit is a standard Q pit, while an "Q(VPI)" type is a Virtual Pipe Inlet.
	\|-		\|-
	\| VP_Network_ID\|\|~~Used~~ to determine which outlet(s) the flow into the inlet pits discharges from.		\| VP_Network_ID\|\| Virtual Pipe Network ID (as an integer) used to determine which outlet(s) the flow into the inlet pits discharges from.
	\|-		\|-
	\| Inlet_Type\|\|For a VPI or Q pit, the name of a pit inlet type in the Pit Inlet Database. Not used for other pits.		\| Inlet_Type\|\|For a VPI or Q pit, the name of a pit inlet type in the Pit Inlet Database. Not used for other pits.

Pavlina Monhartova at 02:52, 3 January 2019

2019-01-03T02:52:10Z

← Older revision		Revision as of 12:52, 3 January 2019
Line 21:		Line 21:
	\| Width\|\|For C pits the diameter of the pit cross-section in the vertical plane. For R and W pits, the width of the pit section in the vertical plane. For all pits the width is used to determine the number of 2D cells to connect.		\| Width\|\|For C pits the diameter of the pit cross-section in the vertical plane. For R and W pits, the width of the pit section in the vertical plane. For all pits the width is used to determine the number of 2D cells to connect.
	\|-		\|-
	\| Conn_2D\|\|Used to control the connection type. For pits this field must be blank or set to “SX”. If set to blank, is treated as a SX connection~~. Other options maybe provided in the future~~.		\| Conn_2D\|\|Used to control the connection type. For pits this field must be blank or set to “SX”. If set to blank, is treated as a SX connection.
	\|-		\|-
	\| Conn_No\|\|Overwrite the automatically determined number of connected 2D cells.		\| Conn_No\|\|Overwrite the automatically determined number of connected 2D cells.

Pavlina Monhartova at 02:50, 3 January 2019

2019-01-03T02:50:43Z

← Older revision		Revision as of 12:50, 3 January 2019
Line 17:		Line 17:
	\| VP_Sur_Index\|\|Only used for VPI pits if using the HPC solver. In the event that the total flow into the VPIs on the same VP_Network_ID exceeds the maximum outflow capacity (see Qmax below), one or more of the VPI flow rates must be modified. The VPIs with the lowest surcharge index are given priority.		\| VP_Sur_Index\|\|Only used for VPI pits if using the HPC solver. In the event that the total flow into the VPIs on the same VP_Network_ID exceeds the maximum outflow capacity (see Qmax below), one or more of the VPI flow rates must be modified. The VPIs with the lowest surcharge index are given priority.
	\|-		\|-
	\| VP_QMax\|\|VPI and VPO if using the HPC solver: For VPOs the maximum flow that can discharge back into the 2D domain. ~~ForVPIs~~ the maximum surcharge capacity or flow back on to the 2D domain. To prevent a VPI from surcharging enter a QMax of 0.0 (zero).		\| VP_QMax\|\|Only used for VPI and VPO if using the HPC solver. For VPOs the maximum flow that can discharge back into the 2D domain. For VPIs the maximum surcharge capacity or flow back on to the 2D domain. To prevent a VPI from surcharging enter a QMax of 0.0 (zero).
	\|-		\|-
	\| Width\|\|For C pits the diameter of the pit cross-section in the vertical plane. For R and W pits, the width of the pit section in the vertical plane. For all pits the width is used to determine the number of 2D cells to connect.		\| Width\|\|For C pits the diameter of the pit cross-section in the vertical plane. For R and W pits, the width of the pit section in the vertical plane. For all pits the width is used to determine the number of 2D cells to connect.
Line 34:		Line 34:
	\|-		\|-
	\| i_1d_layer\|\|The integer index of the GIS layer that the pit came from. For example an '''i_1d_layer''' value of 4 would be the 4th input layer (1d_nwk_M08_pits_001) below.<br>		\| i_1d_layer\|\|The integer index of the GIS layer that the pit came from. For example an '''i_1d_layer''' value of 4 would be the 4th input layer (1d_nwk_M08_pits_001) below.<br>
	<font color="blue"><tt>Read GIS Pits </tt></font> <font color="red"><tt>==</tt></font><tt> mi\~~1d_nwk_M04_channels_001~~.MIF</tt><br>		<font color="blue"><tt>Read GIS Pits </tt></font> <font color="red"><tt>==</tt></font><tt> mi\1d_nwk_M04_pits_001.MIF</tt><br>
	<font color="blue"><tt>Read GIS Pits </tt></font> <font color="red"><tt>==</tt></font><tt> mi\~~1d_nwk_M05_bridge_001~~.MIF</tt><br>		<font color="blue"><tt>Read GIS Pits </tt></font> <font color="red"><tt>==</tt></font><tt> mi\1d_nwk_M05_pits_001.MIF</tt><br>
	<font color="blue"><tt>Read GIS Pits </tt></font> <font color="red"><tt>==</tt></font><tt> mi\~~1d_nwk_M07_trunk_998~~.MIF</tt><br>		<font color="blue"><tt>Read GIS Pits </tt></font> <font color="red"><tt>==</tt></font><tt> mi\1d_nwk_M07_pits_998.MIF</tt><br>
	<font color="blue"><tt>Read GIS Pits </tt></font> <font color="red"><tt>==</tt></font><tt> mi\1d_nwk_M08_pits_001.MIF</tt>		<font color="blue"><tt>Read GIS Pits </tt></font> <font color="red"><tt>==</tt></font><tt> mi\1d_nwk_M08_pits_001.MIF</tt>

Pavlina Monhartova at 01:47, 3 January 2019

2019-01-03T01:47:05Z

← Older revision		Revision as of 11:47, 3 January 2019
Line 34:		Line 34:
	\|-		\|-
	\| i_1d_layer\|\|The integer index of the GIS layer that the pit came from. For example an '''i_1d_layer''' value of 4 would be the 4th input layer (1d_nwk_M08_pits_001) below.<br>		\| i_1d_layer\|\|The integer index of the GIS layer that the pit came from. For example an '''i_1d_layer''' value of 4 would be the 4th input layer (1d_nwk_M08_pits_001) below.<br>
	<font color="blue"><tt>Read GIS ~~Network~~ </tt></font> <font color="red"><tt>==</tt></font><tt> mi\1d_nwk_M04_channels_001.MIF</tt><br>		<font color="blue"><tt>Read GIS Pits </tt></font> <font color="red"><tt>==</tt></font><tt> mi\1d_nwk_M04_channels_001.MIF</tt><br>
	<font color="blue"><tt>Read GIS ~~Network~~ </tt></font> <font color="red"><tt>==</tt></font><tt> mi\1d_nwk_M05_bridge_001.MIF</tt><br>		<font color="blue"><tt>Read GIS Pits </tt></font> <font color="red"><tt>==</tt></font><tt> mi\1d_nwk_M05_bridge_001.MIF</tt><br>
	<font color="blue"><tt>Read GIS ~~Network~~ </tt></font> <font color="red"><tt>==</tt></font><tt> mi\1d_nwk_M07_trunk_998.MIF</tt><br>		<font color="blue"><tt>Read GIS Pits </tt></font> <font color="red"><tt>==</tt></font><tt> mi\1d_nwk_M07_trunk_998.MIF</tt><br>
	<font color="blue"><tt>Read GIS ~~Network~~ </tt></font> <font color="red"><tt>==</tt></font><tt> mi\1d_nwk_M08_pits_001.MIF</tt>		<font color="blue"><tt>Read GIS Pits </tt></font> <font color="red"><tt>==</tt></font><tt> mi\1d_nwk_M08_pits_001.MIF</tt>

	\|}		\|}

Pavlina Monhartova at 01:44, 3 January 2019

2019-01-03T01:44:50Z

← Older revision		Revision as of 11:44, 3 January 2019
Line 15:		Line 15:
	\| Inlet_Type\|\|For a VPI or Q pit, the name of a pit inlet type in the Pit Inlet Database. Not used for other pits.		\| Inlet_Type\|\|For a VPI or Q pit, the name of a pit inlet type in the Pit Inlet Database. Not used for other pits.
	\|-		\|-
	\| VP_Sur_Index\|\|Only used for VPI pits if using the HPC solver. In the event that the total flow into the VPIs on the same VP_Network_ID exceeds the maximum outflow capacity ~~of the VPOs of that VP_Network_ID~~ (see Qmax below), one or more of the VPI flow rates must be modified~~. The surcharge index is used to determine how VPI flows are adjusted~~. The VPIs with the lowest surcharge index are given priority.		\| VP_Sur_Index\|\|Only used for VPI pits if using the HPC solver. In the event that the total flow into the VPIs on the same VP_Network_ID exceeds the maximum outflow capacity (see Qmax below), one or more of the VPI flow rates must be modified. The VPIs with the lowest surcharge index are given priority.
	\|-		\|-
	\| VP_QMax\|\|VPI and VPO if using the HPC solver: For VPOs the maximum flow that can discharge back into the 2D domain. ForVPIs the maximum surcharge capacity or flow back on to the 2D domain. To prevent a VPI from surcharging enter a QMax of 0.0 (zero).		\| VP_QMax\|\|VPI and VPO if using the HPC solver: For VPOs the maximum flow that can discharge back into the 2D domain. ForVPIs the maximum surcharge capacity or flow back on to the 2D domain. To prevent a VPI from surcharging enter a QMax of 0.0 (zero).

Pavlina Monhartova at 01:41, 3 January 2019

2019-01-03T01:41:01Z

← Older revision		Revision as of 11:41, 3 January 2019
Line 1:		Line 1:
	This GIS layer contains information on the 1D pits for the simulation.<br>		This GIS layer contains information on the 1D pits for the simulation.<br>
	The values for the 1D tabular ~~pitdata~~ (e.g. time-series) can be found in the [[Check_Files_1d_pit_inlet_tables \|_1d_pit_inlet_tables_check.csv]] file.<br>		The values for the 1D tabular pit data (e.g. time-series) can be found in the [[Check_Files_1d_pit_inlet_tables \|_1d_pit_inlet_tables_check.csv]] file.<br>
	<br>		<br>
	'''Attributes of pit_A_check'''<br>		'''Attributes of pit_A_check'''<br>