Struct ConstrainedSolution 

pub struct ConstrainedSolution {
    pub stats: SolveStats,
    pub flows: Vec<(f64, f64)>,
    pub indeterminate: Vec<usize>,
}

The outcome of a constrained solve.

Fields

stats: SolveStats

flows: Vec<(f64, f64)>

Per switch, the flow (P, Q) leaving its from end, in per unit.

Exactly zero for an open switch, and for every switch named in indeterminate.

indeterminate: Vec<usize>

Switches whose flow the network does not determine, so this pinned it to zero to keep the system nonsingular.

Three ways in, all reported the same way because the caller’s question is the same one — is this number physical?:

• A loop of closed switches. θ_i = θ_j around a cycle is one redundant equation, and the flows around it are one free parameter. Regularize hides this by resolving the split with its own stiffness; there is no more information there than here.
• A self-loop, both ends on one bus. Nothing to tie.
• Both ends fixed — two Slack buses, or two PV buses for the reactive half. The constraint is vacuous and the flow is absorbed by whatever holds those buses.

The reactive half can be indeterminate while the active half is not (a switch between two PV buses), in which case the switch appears here and its Q is zero while its P is real. See ConstrainedSolution::flows.

Trait Implementations

impl Clone for ConstrainedSolution

fn clone(&self) -> Self

Returns a duplicate of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl Debug for ConstrainedSolution

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.