transport¶
A network: generators sit on buses, lines connect buses, and power balances at every bus.
✔ Agrees with hand-written linopy 0.9.0 — objective 4400, matched to
rtol=1e-09.
The problem¶
Each sum is over the lines or generators a coordinate map sends to bus \(b\) — \(\mathrm{bus}\), \(\mathrm{to}\) and \(\mathrm{from}\) are the coordinates the dimensions declare, not sets in their own right. Load is \(d\) here, because \(\ell\) is already the line index.
The model¶
The same model, as math
Sets¶
| Symbol | Meaning |
|---|---|
| \(\mathcal{S}\) | index \(s\) --- snapshot --- dispatch periods |
| \(\mathcal{G}\) | index \(g\) --- generator with \(\mathrm{bus}: \mathcal{G} \to \mathcal{B}\) --- generating units |
| \(\mathcal{B}\) | index \(b\) --- bus --- network nodes |
| \(\mathcal{L}\) | index \(\ell\) --- line with \(\mathrm{from}: \mathcal{L} \to \mathcal{B},\enspace \mathrm{to}: \mathcal{L} \to \mathcal{B}\) --- transmission lines, each joining two buses |
Parameters¶
| Symbol | Meaning |
|---|---|
| \(\bar p\) | p_max over \(\mathcal{G}\) --- installed capacity |
| \(c\) | cost over \(\mathcal{G}\) --- marginal cost |
| \(\bar f\) | cap over \(\mathcal{L}\) --- forward transmission limit |
| \(\underline{f}\) | neg_cap over \(\mathcal{L}\) --- reverse transmission limit |
| \(d\) | load over \(\mathcal{S} \times \mathcal{B}\) --- demand at each bus |
Variables¶
| Symbol | Meaning |
|---|---|
| \(p\) | p over \(\mathcal{S} \times \mathcal{G}\) --- output of generator \(g\) in snapshot \(s\) |
| \(f\) | f over \(\mathcal{S} \times \mathcal{L}\) --- flow on line \(\ell\), signed towards its to bus |
Objective¶
total_cost
Subject to¶
balance
Variable domains¶
p
f
The tabs start from the instance’s tables — one frame per parameter.
dimensions:
snapshot:
dtype: int
generator:
dtype: str
coords: [bus] # every generator sits on a bus
bus:
dtype: str
line:
dtype: str
coords: {from: bus, to: bus} # both endpoints are buses
parameters:
p_max:
dims: [generator]
cost:
dims: [generator]
cap:
dims: [line]
neg_cap:
dims: [line]
load:
dims: [snapshot, bus]
variables:
p:
foreach: [snapshot, generator]
bounds:
lower: 0
upper: p_max
f:
foreach: [snapshot, line]
bounds:
lower: neg_cap
upper: cap
expressions:
gen_at_bus: sum(p, over=generator, group_by=bus)
net_inflow: sum(f, over=line, group_by=to) - sum(f, over=line, group_by=from)
constraints:
balance:
foreach: [snapshot, bus]
expression: gen_at_bus + net_inflow == load
objectives:
total_cost:
sense: minimize
expression: p * cost
The model-building half of examples/ports/references/linopy/transport.py:
def build(tables: dict[str, pd.DataFrame]) -> linopy.Model:
"""The instance's tables as a linopy model, row for row.
``tables`` is the same mapping the lpspec call binds as ``sources``.
"""
p_max: pd.Series = tables['p_max'].set_index('generator')['value']
cost: pd.Series = tables['cost'].set_index('generator')['value']
cap: pd.Series = tables['cap'].set_index('line')['value']
neg_cap: pd.Series = tables['neg_cap'].set_index('line')['value']
load = xr.DataArray(tables['load'].pivot(index='snapshot', columns='bus', values='value'))
snapshots, buses = load.indexes['snapshot'], load.indexes['bus']
gen_at = pd.DataFrame(0.0, index=buses, columns=p_max.index)
for gen, bus in zip(tables['generator']['generator'], tables['generator']['bus'], strict=True):
gen_at.loc[bus, gen] = 1.0
flow_in = pd.DataFrame(0.0, index=buses, columns=cap.index)
for line, src, dst in zip(tables['line']['line'], tables['line']['from'], tables['line']['to'], strict=True):
flow_in.loc[dst, line] += 1.0
flow_in.loc[src, line] -= 1.0
m = linopy.Model()
p = m.add_variables(lower=0, upper=p_max, coords=[snapshots, p_max.index], name='p')
f = m.add_variables(lower=neg_cap, upper=cap, coords=[snapshots, cap.index], name='f')
m.add_constraints(
(p * xr.DataArray(gen_at)).sum('generator') + (f * xr.DataArray(flow_in)).sum('line') == load,
name='balance',
)
m.add_objective((p * cost).sum())
return m
What it exercises¶
Three sum(group_by=) calls, and they are what a network is in this language.
A dimension can carry coordinates — generator carries bus, line
carries from and to — and sum(f, over=line, group_by=to) sums along a
line's to coordinate, landing the result on bus. The same f is summed
twice through two different coordinates, once as an inflow and once as an
outflow.
No adjacency matrix, and no join written by the modeller: the topology is data on the dimension.
The two halves of the balance are named expressions — pure substitution before either backend sees the model, so naming them costs nothing at build or solve; what it buys is a constraint that reads as the sentence it is.
examples/transport.yaml · back to all models