Inputs

struct Conductor <: AbstractEdge

Interface for conductors in a Network. Fieldnames can be provided via a YAML file, JSON file, or populated manually. Conductors are specified via two busses, the impedance in ohms per-unit length, and a length value.

Single phase models

The minimum inputs for a single phase conductor look like:

conductors:
  - busses: 
      - b1
      - b2
    r1: 0.1
    x1: 0.1
    length: 100

Note that the order of the items in the YAML file does not matter.

A conductor can also leverage a template, i.e. another conductor with a name that matches the template value so that we can re-use the impedance values:

conductors:
  - name: cond1
    busses: 
      - b1
      - b2
    r1: 0.1
    x1: 0.1
    length: 100
  - busses:
      - b2
      - b3
    template: cond1
    length: 200

The second conductor in the conductors above will use the r0 and x0 values from cond1, scaled by the length of 200 and normalized by Zbase.

Multi-phase models

Multi-phase conductors can be modeled as symmetrical or asymmetrical components. Similar to OpenDSS, line impedances can be specified via the zero and positive sequence impedances, (r0, x0) and (r1, x1) respectively; or via the lower-diagaonal portion of the phase-impedance matrix.

Using the Multi-phase models require specifing phases (and the zero and positive sequence impedances) like:

conductors:
  - busses: 
      - b1
      - b2
    phases:
      - 2
      - 3
    r0: 0.766
    x0: 1.944
    r1: 0.301
    x1: 0.627
    length: 100

When the sequence impedances are provided the phase-impedance matrix is determined using the math in Symmetrical Mutliphase Conductors.

Alternatively one can specify the rmatrix and xmatrix like:

conductors:
  - busses: 
      - b1
      - b2
    phases:
      - 1
      - 3
    rmatrix: 
      - [0.31]
      - [0.15, 0.32]
    xmatrix:
      - [1.01]
      - [0.5, 1.05]
    length: 100

struct Load <: AbstractBus

A Load input specifier, mapped from YAML, JSON, or manually populated.

The minimum required inputs include several options. All require a bus to place the load. For single phase models provide one of the following sets of values:

• bus, kws1
• bus, kws1, kvars1
• bus, kws1, q_to_p
• bus, csv

where csv is a path to a two column CSV file with a single line header like "kws1,kvars1". If only bus and kws1 are provided then the reactive load will be zero in the power flow model.

For unbalanced multiphase models one must provide one of:

• bus, [kws1, kvars1], [kws2, kvars2], [kws3, kvars3] <– brackets imply optional pairs, depending on the phases at the load bus
• bus, csv

where the csv has 2, 4, or 6 columns with a single line header like "kws1,kvars1,kws2,kvars2,kws3,kvars3" or "kws2,kvars2,kws3,kvars3".

Once the net::Network is defined a load can be accessed like:

ld_busses = collect(load_busses(net))
lb = ld_busses[1]  # bus keys are strings in the network
net[lb, :kws, 1]  # last index is phase integer

function Base.getindex(net::Network, bus::String, kws_kvars::Symbol, phase::Int)

Load getter for Network. Use like:

net["busname", :kws, 2]

net["busname", :kvars, 3]

The second argument must be one of :kws or :kvars. The third arbument must be one of [1,2,3]. If the "busname" exists and has a :Load dict, but the load (e.g. :kvars2) is not defined then zeros(net.Ntimesteps) is returned.