Struct power_flow_data::MultiSectionLineGroup30
source · pub struct MultiSectionLineGroup30 {
pub i: BusNum,
pub j: BusNum,
pub id: ArrayString<3>,
pub dum1: BusNum,
pub dum2: Option<BusNum>,
pub dum3: Option<BusNum>,
pub dum4: Option<BusNum>,
pub dum5: Option<BusNum>,
pub dum6: Option<BusNum>,
pub dum7: Option<BusNum>,
pub dum8: Option<BusNum>,
pub dum9: Option<BusNum>,
}Expand description
Multi-section line group.
Transmission lines commonly have a series of sections with varying physical structures. The section might have different tower configurations, conductor types and bundles or various combinations of these. The physical differences can result in the sections having different resistance, reactance and charging.
A transmission line with several distinct sections can be represented as one multi-section line group.
The DUM_i values on each record define the branches connecting bus i to bus j, and
are entered so as to trace the path from bus i to bus j.
§Example
For a multi-section line grouping consisting of three line sections (and hence two dummy buses):
| From | To | Circuit |
|---|---|---|
| I | D1 | C1 |
| D1 | D2 | C2 |
| D2 | J | C3 |
If this multi-section line grouping is to be assigned the line identifier id “&1”,
the corresponding multi-section line grouping data record is given by:
I, J, '&1', D1, D2
Or in v33 (and if I is the metered end):
I, J, '&1', 1, D1, D2
§Notes
The following notes apply to multi-section line groups:
- Up to 10 line sections (and hence 9 dummy buses) may be defined in each multi-section line grouping. A branch may be a line section of at most one multi-section line grouping.
- Each dummy bus must have exactly two branches connected to it, both of which must be members of the same multi-section line grouping. A multi-section line dummy bus may not be a converter bus of a DC transmission line. A FACTS control device may not be connected to a multi-section line dummy bus.
- The status of line sections and type codes of dummy buses are set such that the multi-section line is treated as a single entity with regards to its service status.
Fields§
§i: BusNum“From bus” number, or extended bus name enclosed in single quotes.
j: BusNum“To bus” number, or extended bus name enclosed in single quotes.
j is entered as a negative number or with a minus sign before the first character of
the extended bus name to designate it as the metered end;
otherwise, bus i is assumed to be the metered end.
id: ArrayString<3>Two-character upper-case alphanumeric multi-section line grouping identifier.
The first character must be an ampersand (“&”).
id = “&1” by default.
dum1: BusNumBus numbers, or extended bus names enclosed in single quotes, of the dummy buses connected by the branches that comprise this multi-section line grouping. No defaults.
dum2: Option<BusNum>§dum3: Option<BusNum>§dum4: Option<BusNum>§dum5: Option<BusNum>§dum6: Option<BusNum>§dum7: Option<BusNum>§dum8: Option<BusNum>§dum9: Option<BusNum>