Revision as of 11:47, 3 January 2019 view source Pavlina Monhartova (talk \| contribs) Bureaucrats, Administrators 5,365 edits No edit summary ← Older edit		Revision as of 12:50, 3 January 2019 view source Pavlina Monhartova (talk \| contribs) Bureaucrats, Administrators 5,365 edits No edit summary Newer edit →
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_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. ~~ForVPIs~~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. 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> <font color="blue"><tt>Read GIS Pits </tt></font> <font color="red"><tt>==</tt></font><tt> mi\~~1d_nwk_M04_channels_001~~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~~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~~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>

Check Files 1d pit A: Difference between revisions