junction_gate#
Similar to the junction object, but with the possibility to close of one of the three connected tunnels
Input connections |
|
Output connections |
|
License |
SHOP_JUNC_GATE |
Release version |
13.0.0.a |
Warning
The junction_gate object is old and will be deprecated in the future. A junction_gate can be replaced with three connected tunnel objects with gates on at least one of the tunnels. A gate can be specified by giving in a gate_opening_curve on the tunnel object. The interlock_constraint object can be use to restrict how many gates can be open at the same time.
Examples#
Attributes#
add_slack#
Future deprecation: All junction_gates should be modelled by using the tunnel object (does not require additional license). Flag determining whether slack variables should be added to the mass balance of the junction gate (xUnit: NO_UNIT, yUnit: NO_UNIT)
height_1#
Future deprecation: All junction_gates should be modelled by using the tunnel object (does not require additional license). Physical height of the connection point between tunnel_1 and tunnel_2 coming into this junction (xUnit: METER, yUnit: METER)
loss_factor_1#
Future deprecation: All junction_gates should be modelled by using the tunnel object (does not require additional license). Friction loss factor for tunnel_1 into this junction multiplied with the square of the flow to get head loss (xUnit: S2/M5, yUnit: S2/M5)
loss_factor_2#
Future deprecation: All junction_gates should be modelled by using the tunnel object (does not require additional license). Friction loss factor for tunnel_2 into this junction multiplied with the square of the flow to get head loss (xUnit: S2/M5, yUnit: S2/M5)
schedule#
Future deprecation: All junction_gates should be modelled by using the tunnel object (does not require additional license). Schedule determining the opening status of this junction gate. -2 means that both tunnel_1 and tunnel_2 are open 0 means that the output from the junction_gate is closed 1 means that only tunnel_1 is connected and 2 means that only tunnel_2 is connected. If two junction_gates are connected in series. The lower junction gate can only have schedule values of 0 or 1 or 2 (xUnit: NO_UNIT, yUnit: NO_UNIT)
pressure_height#
Future deprecation: All junction_gates should be modelled by using the tunnel object (does not require additional license). Resulting pressure height from the optimization calculations (xUnit: NO_UNIT, yUnit: METER)
tunnel_flow_1#
Future deprecation: All junction_gates should be modelled by using the tunnel object (does not require additional license). Resulting flow in tunnel_1 (xUnit: NO_UNIT, yUnit: M3/S)
tunnel_flow_2#
Future deprecation: All junction_gates should be modelled by using the tunnel object (does not require additional license). Resulting flow in tunnel_2 (xUnit: NO_UNIT, yUnit: M3/S)