Struct SeCase 

pub struct SeCase {
    pub network: SeNetwork,
    pub buses: Vec<Bus>,
    pub measurements: Vec<Measurement>,
    pub node_idx: HashMap<u64, usize>,
    pub phases: usize,
}

A network, a starting state and a measurement set, assembled together.

The three have to agree about what a bus index means, which is the whole reason they are built in one place rather than three.

Fields

network: SeNetwork

buses: Vec<Bus>

The buses, in the layout the network is indexed by. Not an estimate: a flat start, which linear_start improves on before the first iteration.

measurements: Vec<Measurement>

node_idx: HashMap<u64, usize>

Document node id to node index. In the phase domain a node owns three buses; use bus_of rather than this directly.

phases: usize

1 for the symmetric domain, 3 for the phase domain.

The one thing a caller downstream of this genuinely needs to know, and it is here so that reporting can say node 7 phase b rather than bus 22.

Implementations

impl SeCase

pub fn bus_of(&self, node: u64, phase: usize) -> Option<usize>

The bus index carrying one phase of one document node.

phase is ignored in the symmetric domain, where a node is one bus.

pub fn nodes(&self) -> Vec<(u64, usize)>

The document’s node ids, in index order — what a report iterates to name its rows.