Struct SolveContext 

pub struct SolveContext<'a> {
    pub buses: &'a mut [Bus],
    pub lines: &'a [Line],
    pub transformers: &'a mut [Transformer],
    pub shunts: &'a [ShuntAdm],
    pub tap_changers: &'a mut [Option<TapChanger>],
    pub regulation: &'a [TapRegulation],
    pub ybus: &'a mut YBusSparse,
}

The network a solve runs against.

Constructed once by the caller and passed to solve_with_loops. The branch and tap fields are optional in the sense that a caller with no tap control simply never supplies them — SolveContext::new leaves them empty, and only Invalidates::Admittances loops read them.

Fields

buses: &'a mut [Bus]

lines: &'a [Line]

transformers: &'a mut [Transformer]

shunts: &'a [ShuntAdm]

tap_changers: &'a mut [Option<TapChanger>]

Parallel to transformers. Empty when the importer retained no tap tables, which is what makes tap control silently inapplicable rather than an error.

regulation: &'a [TapRegulation]

The regulating controls read from the network document.

ybus: &'a mut YBusSparse

Implementations

impl<'a> SolveContext<'a>

pub fn new(buses: &'a mut [Bus], ybus: &'a mut YBusSparse) -> Self

Buses and a Y-bus: everything a loop that never moves a tap needs.

pub fn with_branches( self, lines: &'a [Line], transformers: &'a mut [Transformer], shunts: &'a [ShuntAdm], ) -> Self

The branch data the Y-bus is built from. Required before any tap loop can restamp it.

pub fn with_taps( self, tap_changers: &'a mut [Option<TapChanger>], regulation: &'a [TapRegulation], ) -> Self

The tap tables and the regulating controls that act on them.

pub fn restamp_ybus(&mut self)

Rebuild the Y-bus from the current branch data.

Called by the driver after an Invalidates::Admittances loop moved a tap. A tap change alters admittance values and not the sparsity pattern, so this produces a structurally identical matrix and the symbolic factorization stays valid.

Does nothing when the caller supplied no branch data, since there is then nothing to rebuild from — a tap loop cannot be configured in that case either, so this is unreachable rather than lossy.