Rung 34: maintenance of committable units — a fixed, an extendable and a modular committable generator, link and process, each taken off for one event¶
One rung of the PyPSA corpus: the file pypsa.yaml projected onto what this network builds, attached to that network, and held to what PyPSA solves it to.
✔ Verified against pypsa master at 3625c816 — objective 6420.048611 on both sides; structure ✔ 101 constraints · 30 variables, name for name; size ✔ 503 rows · ✔ 277 columns · ✔ 1153 nonzeros; duals — integer model, no duals; model for model: 131 blocks equal, 0 documented splits, 1 recorded deviations.
Rows and columns, PyPSA against specsolve, name for name
| row | PyPSA | specsolve |
|---|---|---|
Bus-nodal_balance |
12 | 12 |
Generator-com-ext-p-lower |
4 | 4 |
Generator-com-ext-p-lower-nonneg |
4 | 4 |
Generator-com-ext-p-upper-bigM |
4 | 4 |
Generator-com-ext-p-upper-cap |
4 | 4 |
Generator-com-mod-p-lower |
4 | 4 |
Generator-com-mod-p-upper |
4 | 4 |
Generator-com-p-lower |
4 | 4 |
Generator-com-p-upper |
4 | 4 |
Generator-com-transition-shut-down |
12 | 12 |
Generator-com-transition-start-up |
12 | 12 |
Generator-ext-p_nom-lower |
2 | 2 |
Generator-ext-p_nom-upper |
2 | 2 |
Generator-fix-p-lower |
12 | 12 |
Generator-fix-p-upper |
12 | 12 |
Generator-maint-event-count |
3 | 3 |
Generator-maint-modstatus-lb |
4 | 4 |
Generator-maint-modstatus-le-maint |
4 | 4 |
Generator-maint-modstatus-le-status |
4 | 4 |
Generator-maint-start-horizon |
1 | 1 |
Generator-maint-status-lb |
4 | 4 |
Generator-maint-status-le-maint |
4 | 4 |
Generator-maint-status-le-status |
4 | 4 |
Generator-maint-window |
12 | 12 |
Generator-maintcap_lower_nommax |
4 | 4 |
Generator-maintcap_lower_nommin |
4 | 4 |
Generator-maintcap_upper |
4 | 4 |
Generator-maintcap_upper_nommax |
4 | 4 |
Generator-p_nom_modularity |
1 | 1 |
Generator-shut_down-p-fixed-upper |
8 | 8 |
Generator-shut_down-p_nom-variable-upper |
4 | 4 |
Generator-start_up-p-fixed-upper |
8 | 8 |
Generator-start_up-p_nom-variable-upper |
4 | 4 |
Generator-status-p-fixed-upper |
8 | 8 |
Generator-status-p_nom-variable-upper |
4 | 4 |
Link-com-ext-p-lower |
4 | 4 |
Link-com-ext-p-lower-nonneg |
4 | 4 |
Link-com-ext-p-upper-bigM |
4 | 4 |
Link-com-ext-p-upper-cap |
4 | 4 |
Link-com-mod-p-lower |
4 | 4 |
Link-com-mod-p-upper |
4 | 4 |
Link-com-p-lower |
4 | 4 |
Link-com-p-upper |
4 | 4 |
Link-com-transition-shut-down |
12 | 12 |
Link-com-transition-start-up |
12 | 12 |
Link-ext-p_nom-lower |
2 | 2 |
Link-ext-p_nom-upper |
2 | 2 |
Link-fix-p-lower |
4 | 4 |
Link-fix-p-upper |
4 | 4 |
Link-maint-event-count |
3 | 3 |
Link-maint-modstatus-lb |
4 | 4 |
Link-maint-modstatus-le-maint |
4 | 4 |
Link-maint-modstatus-le-status |
4 | 4 |
Link-maint-start-horizon |
1 | 1 |
Link-maint-status-lb |
4 | 4 |
Link-maint-status-le-maint |
4 | 4 |
Link-maint-status-le-status |
4 | 4 |
Link-maint-window |
12 | 12 |
Link-maintcap_lower_nommax |
4 | 4 |
Link-maintcap_lower_nommin |
4 | 4 |
Link-maintcap_upper |
4 | 4 |
Link-maintcap_upper_nommax |
4 | 4 |
Link-p_nom_modularity |
1 | 1 |
Link-shut_down-p-fixed-upper |
8 | 8 |
Link-shut_down-p_nom-variable-upper |
4 | 4 |
Link-start_up-p-fixed-upper |
8 | 8 |
Link-start_up-p_nom-variable-upper |
4 | 4 |
Link-status-p-fixed-upper |
8 | 8 |
Link-status-p_nom-variable-upper |
4 | 4 |
Process-com-ext-p-lower |
4 | 4 |
Process-com-ext-p-lower-nonneg |
4 | 4 |
Process-com-ext-p-upper-bigM |
4 | 4 |
Process-com-ext-p-upper-cap |
4 | 4 |
Process-com-mod-p-lower |
4 | 4 |
Process-com-mod-p-upper |
4 | 4 |
Process-com-p-lower |
4 | 4 |
Process-com-p-upper |
4 | 4 |
Process-com-transition-shut-down |
12 | 12 |
Process-com-transition-start-up |
12 | 12 |
Process-ext-p_nom-lower |
2 | 2 |
Process-ext-p_nom-upper |
2 | 2 |
Process-maint-event-count |
3 | 3 |
Process-maint-modstatus-lb |
4 | 4 |
Process-maint-modstatus-le-maint |
4 | 4 |
Process-maint-modstatus-le-status |
4 | 4 |
Process-maint-start-horizon |
1 | 1 |
Process-maint-status-lb |
4 | 4 |
Process-maint-status-le-maint |
4 | 4 |
Process-maint-status-le-status |
4 | 4 |
Process-maint-window |
12 | 12 |
Process-maintcap_lower_nommax |
4 | 4 |
Process-maintcap_lower_nommin |
4 | 4 |
Process-maintcap_upper |
4 | 4 |
Process-maintcap_upper_nommax |
4 | 4 |
Process-p_nom_modularity |
1 | 1 |
Process-shut_down-p-fixed-upper |
8 | 8 |
Process-shut_down-p_nom-variable-upper |
4 | 4 |
Process-start_up-p-fixed-upper |
8 | 8 |
Process-start_up-p_nom-variable-upper |
4 | 4 |
Process-status-p-fixed-upper |
8 | 8 |
Process-status-p_nom-variable-upper |
4 | 4 |
| column | PyPSA | specsolve |
|---|---|---|
Generator-maintenance |
12 | 12 |
Generator-maintenance_capacity |
4 | 4 |
Generator-maintenance_start |
12 | 12 |
Generator-maintenance_status |
8 | 8 |
Generator-n_mod |
1 | 1 |
Generator-p |
24 | 24 |
Generator-p_nom |
2 | 2 |
Generator-shut_down |
12 | 12 |
Generator-start_up |
12 | 12 |
Generator-status |
12 | 12 |
Link-maintenance |
12 | 12 |
Link-maintenance_capacity |
4 | 4 |
Link-maintenance_start |
12 | 12 |
Link-maintenance_status |
8 | 8 |
Link-n_mod |
1 | 1 |
Link-p |
16 | 16 |
Link-p_nom |
2 | 2 |
Link-shut_down |
12 | 12 |
Link-start_up |
12 | 12 |
Link-status |
12 | 12 |
Process-maintenance |
12 | 12 |
Process-maintenance_capacity |
4 | 4 |
Process-maintenance_start |
12 | 12 |
Process-maintenance_status |
8 | 8 |
Process-n_mod |
1 | 1 |
Process-p |
12 | 12 |
Process-p_nom |
2 | 2 |
Process-shut_down |
12 | 12 |
Process-start_up |
12 | 12 |
Process-status |
12 | 12 |
The model¶
The same model, as math
The file states a plain n.optimize(), its multi-period class under the multi_investment_periods keyword, and its stochastic class, which n.set_scenarios(...) sets. Every quantity chosen once the future is known (second-stage) spans the futures dispatch is chosen in (scenario). Capacity is chosen once, before the future is known, and paid at its expected cost in each investment period its build year and lifetime span. Operation is the expectation over the scenarios' weights, with a share priced at the worst-outcome mean cost (CVaR) only where a risk preference is set. A plain run's data has one scenario, one period, unit weights, no outage and every active flag true, so the problem is the standard one. On a security-constrained run, PyPSA copies each branch flow limit once per outage, and the outage factors, active flags and scenario weights come from data prep.
Sets¶
| Symbol | Meaning |
|---|---|
| \(\mathcal{B}\) | index \(b\) — breakpoint — the corners of a piecewise-linear curve, in order. A curve runs over the breakpoints its data has rows for, so curves may differ in length |
| \(\mathcal{N}\) | index \(n\) — bus with \(\mathrm{Generator\_bus}: \mathcal{G} \to \mathcal{N},\ \mathrm{Link\_bus0}: \mathcal{L} \to \mathcal{N},\ \mathrm{Link\_output\_bus}: \mathcal{O} \to \mathcal{N},\ \mathrm{Load\_bus}: \mathcal{D} \to \mathcal{N},\ \mathrm{Process\_output\_bus}: \mathcal{R} \to \mathcal{N}\) — network nodes |
| \(\mathcal{G}\) | index \(g\) — generator with \(\mathrm{Generator\_bus}: \mathcal{G} \to \mathcal{N},\ \mathrm{Generator\_maintenance\_cover} \subseteq \mathcal{T} \times \mathcal{G} \times \Xi \times \mathcal{T}\), Generator_maintenance_cover is absent where the data has no row — generating units, each on one bus |
| \(\mathcal{L}\) | index \(l\) — link with \(\mathrm{Link\_bus0}: \mathcal{L} \to \mathcal{N},\ \mathrm{Link\_maintenance\_cover} \subseteq \mathcal{T} \times \mathcal{L} \times \Xi \times \mathcal{T},\ \mathrm{Link\_output\_link}: \mathcal{O} \to \mathcal{L}\), Link_maintenance_cover is absent where the data has no row — controllable connections, each from one bus to the buses it delivers to |
| \(\mathcal{O}\) | index \(o\) — link_output with \(\mathrm{Link\_output\_bus}: \mathcal{O} \to \mathcal{N},\ \mathrm{Link\_output\_link}: \mathcal{O} \to \mathcal{L}\) — a link's output ports, one label per port a link declares. The labels are PyPSA's bus1, bus2, … columns read long, data prep. A link of any number of output ports is then one term in the balance |
| \(\mathcal{D}\) | index \(d\) — load with \(\mathrm{Load\_bus}: \mathcal{D} \to \mathcal{N}\) — demands, each on one bus |
| \(\mathcal{Y}\) | index \(y\) — period with \(\mathrm{snapshot\_period}: \mathcal{T} \to \mathcal{Y}\) — investment periods. It is PyPSA's investment_periods |
| \(\mathcal{J}\) | index \(j\) — process with \(\mathrm{Process\_maintenance\_cover} \subseteq \mathcal{T} \times \mathcal{J} \times \Xi \times \mathcal{T},\ \mathrm{Process\_output\_process}: \mathcal{R} \to \mathcal{J}\), Process_maintenance_cover is absent where the data has no row — generalised multi-port converters, each with an internal power that every port draws or delivers at its own rate |
| \(\mathcal{R}\) | index \(r\) — process_output with \(\mathrm{Process\_output\_bus}: \mathcal{R} \to \mathcal{N},\ \mathrm{Process\_output\_process}: \mathcal{R} \to \mathcal{J}\) — a process's ports, one label per port a process declares. The labels are PyPSA's bus0, bus1, …, each with a signed rate, data prep. A process of any number of ports is then one term in the balance |
| \(\Xi\) | index \(\xi\) — scenario with \(\mathrm{Generator\_maintenance\_cover} \subseteq \mathcal{T} \times \mathcal{G} \times \Xi \times \mathcal{T},\ \mathrm{Link\_maintenance\_cover} \subseteq \mathcal{T} \times \mathcal{L} \times \Xi \times \mathcal{T},\ \mathrm{Process\_maintenance\_cover} \subseteq \mathcal{T} \times \mathcal{J} \times \Xi \times \mathcal{T}\), Generator_maintenance_cover is absent where the data has no row, Link_maintenance_cover is absent where the data has no row, Process_maintenance_cover is absent where the data has no row — the futures dispatch is chosen in, each with a weight |
| \(\mathcal{T}\) | index \(t\) — snapshot with \(\mathrm{Generator\_maintenance\_cover} \subseteq \mathcal{T} \times \mathcal{G} \times \Xi \times \mathcal{T},\ \mathrm{Link\_maintenance\_cover} \subseteq \mathcal{T} \times \mathcal{L} \times \Xi \times \mathcal{T},\ \mathrm{Process\_maintenance\_cover} \subseteq \mathcal{T} \times \mathcal{J} \times \Xi \times \mathcal{T},\ \mathrm{snapshot\_period}: \mathcal{T} \to \mathcal{Y}\), Generator_maintenance_cover is absent where the data has no row, Link_maintenance_cover is absent where the data has no row, Process_maintenance_cover is absent where the data has no row — dispatch periods |
Parameters¶
| Symbol | Meaning |
|---|---|
| \(\mathrm{Bus\_attached}\) | Bus_attached over \(\mathcal{N} \times \mathcal{T}\) — whether a load, a unit, a port or a branch that is active in the snapshot's period is attached to the bus, data prep. A bus nothing is attached to has no balance row |
| \(\mathrm{on}\) | Generator_active over \(\mathcal{G} \times \mathcal{T}\) — whether a generator is active in a snapshot's period. It is PyPSA's active, from build year and lifetime, data prep |
| \(\mathrm{act}\) | Generator_active_asset over \(\mathcal{G}\) — whether a generator is one of PyPSA's active_assets, by its active flag alone, without build year and lifetime. A unit that is active in no snapshot of the horizon still counts. PyPSA refuses one that differs by scenario (constants.py:54) |
| \(\mathrm{M}\) | Generator_big_m over \(\mathcal{G} \times \Xi\), absent where the data has no row — the bound a committed extendable generator's big-M rows release it by, data prep. It is the build cap p_nom_max times the highest p_max_pu, where the cap is finite and positive. Elsewhere it is committable_big_m times the highest p_max_pu (components.py:1082-1152). Without that keyword, it is ten times the largest of the peak total load and the component's largest finite p_nom and p_nom_max. Where there is none of them, it is 1e6. Below the output a solve wants, it caps that output |
| \(\mathrm{c}^{\mathrm{cap}}\) | Generator_capital_cost over \(\mathcal{G} \times \Xi\) — cost of one unit of nominal power for the modelled horizon (PyPSA's periodized_cost), data prep. It is overnight_cost as an annuity over lifetime at discount_rate, times nyears, where overnight_cost is given, and capital_cost where it is not. Both add fom_cost (components.py:1157-1178, costs.py:102-203) |
| \(\mathrm{W}\) | Generator_capital_weight over \(\mathcal{G}\) — the sum of period weights a generator is active in. It is PyPSA's active * period_weighting, summed, data prep |
| \(\mathrm{com}\) | Generator_committable over \(\mathcal{G}\) — whether output is gated by an on/off status decision |
| \(\mathrm{mnt}\) | Generator_maintainable over \(\mathcal{G}\) — whether a generator must be taken off for maintenance within the horizon: in any scenario, as PyPSA takes the union over them (components.py:1000-1003) |
| \(\mathrm{n}^{\mathrm{mnt}}\) | Generator_maintenance_events over \(\mathcal{G} \times \Xi\) — how many maintenance events occur within the horizon |
| \(\gamma\) | Generator_maintenance_pu over \(\mathcal{G} \times \Xi\) — the share of the build a maintenance event takes off |
| \(\mathrm{blk}\) | Generator_maintenance_start_blocked over \(\mathcal{G} \times \Xi \times \mathcal{T}\) — true where no maintenance event may start, data prep. The snapshots it would cover there run past the end of the horizon or into one the generator is not active in. It is PyPSA's active & ~valid, from maintenance_duration and the generator weightings |
| \(\mathrm{c}\) | Generator_marginal_cost over \(\mathcal{G} \times \Xi \times \mathcal{T}\) — cost of one unit of output |
| \(\mathrm{p}^{\mathrm{curve}}\) | Generator_marginal_cost_curve_p over \(\mathcal{B} \times \mathcal{G}\), absent where the data has no row — the output at each breakpoint of a generator's piecewise marginal_cost curve: PyPSA's p_pu breakpoints times p_nom, data prep. A generator with no curve has no rows |
| \(\mathrm{c}^{(2)}\) | Generator_marginal_cost_quadratic over \(\mathcal{G} \times \Xi \times \mathcal{T}\) — cost of the square of one unit of output |
| \(\mathrm{N}^{\mathrm{fix}}\) | Generator_modules_installed over \(\mathcal{G} \times \Xi\) — how many whole modules a committable build has in place, data prep. It is Generator_p_nom / Generator_p_nom_mod where a fixed build is modular, and one where it is not. PyPSA refuses a fixed modular build whose nominal power is not a whole number of modules |
| \(\overline{\mathrm{p}}\) | Generator_p_max_pu over \(\mathcal{G} \times \Xi \times \mathcal{T}\) — most output, per unit of nominal power: an availability profile |
| \(\underline{\mathrm{p}}\) | Generator_p_min_pu over \(\mathcal{G} \times \Xi \times \mathcal{T}\) — least output, per unit of nominal power |
| \(\mathrm{nonneg}\) | Generator_p_min_pu_nonneg over \(\mathcal{G}\) — true where none of the generator's own minimums-per-unit is negative. It is PyPSA's per-unit (p_min_pu >= 0).all() over every snapshot and scenario, data prep |
| \(\mathrm{p}^{\mathrm{nom}}\) | Generator_p_nom over \(\mathcal{G} \times \Xi\) — nominal power |
| \(\mathrm{ext}\) | Generator_p_nom_extendable over \(\mathcal{G}\) — whether the nominal power is a decision |
| \(\overline{\mathrm{p}}^{\mathrm{nom}}\) | Generator_p_nom_max over \(\mathcal{G} \times \Xi\) — most nominal power an extendable generator may be built at |
| \(\underline{\mathrm{p}}^{\mathrm{nom}}\) | Generator_p_nom_min over \(\mathcal{G} \times \Xi\) — least nominal power an extendable generator may be built at |
| \(\mathrm{p}^{\mathrm{mod}}\) | Generator_p_nom_mod over \(\mathcal{G}\), absent where the data has no row — the module size a build comes in whole numbers of. No value means the build is continuous |
| \(\mathrm{c}^{\mathrm{dn}}\) | Generator_shut_down_cost over \(\mathcal{G} \times \Xi \times \mathcal{T}\) — cost of one stop in this snapshot |
| \(\mathrm{sgn}\) | Generator_sign over \(\mathcal{G}\) — the sign output enters its bus's balance with. It is PyPSA's sign, 1 unless given, -1 for a unit that draws power. PyPSA refuses one that differs by scenario (constants.py:46) |
| \(\mathrm{c}^{\mathrm{on}}\) | Generator_stand_by_cost over \(\mathcal{G} \times \Xi \times \mathcal{T}\) — cost of one snapshot spent on |
| \(\mathrm{c}^{\mathrm{up}}\) | Generator_start_up_cost over \(\mathcal{G} \times \Xi \times \mathcal{T}\) — cost of one start in this snapshot |
| \(\mathrm{u}^{0}\) | Generator_status_initial over \(\mathcal{G} \times \Xi\) — one where the unit was on before the first snapshot, zero where off. It is PyPSA's up_time_before > 0 for a committable unit, and one for a unit that is not, whose ramp rows PyPSA starts from on (constraints.py:323), data prep. Under a rolling horizon, it is the status the previous window solved, a fraction where unit commitment is linearised |
| \(\mathrm{on}^{f}\) | Link_active over \(\mathcal{L} \times \mathcal{T}\) — whether a link is active in a snapshot's period. It is PyPSA's active, data prep |
| \(\mathrm{act}^{f}\) | Link_active_asset over \(\mathcal{L}\) — whether a link is one of PyPSA's active_assets, by its active flag alone, without build year and lifetime. A unit that is active in no snapshot of the horizon still counts. PyPSA refuses one that differs by scenario (constants.py:54) |
| \(\mathrm{M}^{f}\) | Link_big_m over \(\mathcal{L} \times \Xi\), absent where the data has no row — the bound a committed extendable link's big-M rows release it by, data prep. It is the build cap p_nom_max times the highest p_max_pu, where the cap is finite and positive. Elsewhere it is committable_big_m times the highest p_max_pu (components.py:1082-1152). Without that keyword, it is ten times the largest of the peak total load and the component's largest finite p_nom and p_nom_max. Where there is none of them, it is 1e6. Below the flow a solve wants, it caps that flow |
| \(\mathrm{c}^{\mathrm{cap},f}\) | Link_capital_cost over \(\mathcal{L} \times \Xi\) — cost of one unit of nominal power for the modelled horizon (PyPSA's periodized_cost), data prep. It is overnight_cost as an annuity over lifetime at discount_rate, times nyears, where overnight_cost is given, and capital_cost where it is not. Both add fom_cost (components.py:1157-1178, costs.py:102-203) |
| \(\mathrm{W}^{f}\) | Link_capital_weight over \(\mathcal{L}\) — the sum of period weights a link is active in. It is PyPSA's active * period_weighting, summed, data prep |
| \(\mathrm{com}^{f}\) | Link_committable over \(\mathcal{L}\) — whether flow is gated by an on/off status decision |
| \(\eta\) | Link_efficiency over \(\mathcal{O} \times \Xi \times \mathcal{T}\) — share of the flow that arrives at an output port, PyPSA's efficiency, efficiency2, … read long: negative where that port consumes rather than delivers. Read at the snapshot the flow arrives, so a delayed port delivers at its arrival snapshot's efficiency (constraints.py:1575) |
| \(\mathrm{mnt}^{f}\) | Link_maintainable over \(\mathcal{L}\) — whether a link must be taken off for maintenance within the horizon: in any scenario, as PyPSA takes the union over them (components.py:1000-1003) |
| \(\mathrm{n}^{f,\mathrm{mnt}}\) | Link_maintenance_events over \(\mathcal{L} \times \Xi\) — how many maintenance events occur within the horizon |
| \(\gamma^{f}\) | Link_maintenance_pu over \(\mathcal{L} \times \Xi\) — the share of the build a maintenance event takes off |
| \(\mathrm{blk}^{f}\) | Link_maintenance_start_blocked over \(\mathcal{L} \times \Xi \times \mathcal{T}\) — true where no maintenance event may start, data prep. The snapshots it would cover there run past the end of the horizon or into one the link is not active in. It is PyPSA's active & ~valid, from maintenance_duration and the generator weightings |
| \(\mathrm{c}^{f}\) | Link_marginal_cost over \(\mathcal{L} \times \Xi \times \mathcal{T}\) — cost of one unit of flow |
| \(\mathrm{c}^{f,(2)}\) | Link_marginal_cost_quadratic over \(\mathcal{L} \times \Xi \times \mathcal{T}\) — cost of the square of one unit of flow |
| \(\mathrm{N}^{f,\mathrm{fix}}\) | Link_modules_installed over \(\mathcal{L} \times \Xi\) — how many whole modules a committable build has in place, data prep. It is Link_p_nom / Link_p_nom_mod where a fixed build is modular, and one where it is not. PyPSA refuses a fixed modular build whose nominal power is not a whole number of modules |
| \(\mathrm{cyc}^{f}\) | Link_output_cyclic_delay over \(\mathcal{O}\) — whether a delayed port's flow wraps from the end of its investment period (PyPSA's cyclic_delay, cyclic_delay2, …). Where it does not, the flow still in transit at each period's first snapshots is lost. The flag is the same in every scenario, as the delay is |
| \(\mathrm{d}^{f}\) | Link_output_delay over \(\mathcal{O}\) — snapshots a port's delivery lags its link's flow (PyPSA's delay, delay2, … read long). In data prep you divide it by the snapshot_weightings.generators value and round it up. It is zero for a port that delivers at once. A port has the same delay in every scenario, because PyPSA refuses a delay that differs by scenario (constants.py:55) |
| \(\overline{\mathrm{f}}\) | Link_p_max_pu over \(\mathcal{L} \times \Xi \times \mathcal{T}\) — most flow, per unit of nominal power |
| \(\underline{\mathrm{f}}\) | Link_p_min_pu over \(\mathcal{L} \times \Xi \times \mathcal{T}\) — least flow, per unit of nominal power: negative for a link that carries both ways |
| \(\mathrm{nonneg}^{f}\) | Link_p_min_pu_nonneg over \(\mathcal{L}\) — true where none of the link's own minimums-per-unit is negative. It is PyPSA's per-unit (p_min_pu >= 0).all() over every snapshot and scenario, data prep |
| \(\mathrm{f}^{\mathrm{nom}}\) | Link_p_nom over \(\mathcal{L} \times \Xi\) — nominal power |
| \(\mathrm{ext}^{f}\) | Link_p_nom_extendable over \(\mathcal{L}\) — whether the nominal power is a decision |
| \(\overline{\mathrm{f}}^{\mathrm{nom}}\) | Link_p_nom_max over \(\mathcal{L} \times \Xi\) — most nominal power an extendable link may be built at |
| \(\underline{\mathrm{f}}^{\mathrm{nom}}\) | Link_p_nom_min over \(\mathcal{L} \times \Xi\) — least nominal power an extendable link may be built at |
| \(\mathrm{f}^{\mathrm{mod}}\) | Link_p_nom_mod over \(\mathcal{L}\), absent where the data has no row — the module size a build comes in whole numbers of. No value means the build is continuous |
| \(\mathrm{c}^{f,\mathrm{dn}}\) | Link_shut_down_cost over \(\mathcal{L} \times \Xi \times \mathcal{T}\) — cost of one stop in this snapshot |
| \(\mathrm{c}^{f,\mathrm{on}}\) | Link_stand_by_cost over \(\mathcal{L} \times \Xi \times \mathcal{T}\) — cost of one snapshot spent on |
| \(\mathrm{c}^{f,\mathrm{up}}\) | Link_start_up_cost over \(\mathcal{L} \times \Xi \times \mathcal{T}\) — cost of one start in this snapshot |
| \(\mathrm{u}^{f,0}\) | Link_status_initial over \(\mathcal{L} \times \Xi\) — one where the link was on before the first snapshot, zero where off. It is PyPSA's up_time_before > 0 for a committable link, and one for a link that is not, whose ramp rows PyPSA starts from on (constraints.py:323), data prep. Under a rolling horizon, it is the status the previous window solved, a fraction where unit commitment is linearised |
| \(\mathrm{on}^{\mathrm{load}}\) | Load_active over \(\mathcal{D}\) — whether a load is active in the network, PyPSA's active. A load has no build year and no lifetime, so the flag is the same in every snapshot. PyPSA refuses one that differs by scenario (constants.py:54) |
| \(\mathrm{load}\) | Load_p_set over \(\mathcal{D} \times \Xi \times \mathcal{T}\) — demand |
| \(\mathrm{sgn}^{\mathrm{load}}\) | Load_sign over \(\mathcal{D}\) — the sign a load's demand enters its bus's balance with. It is PyPSA's sign, -1 unless given, 1 for a load that feeds its bus. PyPSA refuses one that differs by scenario (constants.py:46) |
| \(\mathrm{on}^{z}\) | Process_active over \(\mathcal{J} \times \mathcal{T}\) — whether a process is active in a snapshot's period. It is PyPSA's active, data prep |
| \(\mathrm{act}^{z}\) | Process_active_asset over \(\mathcal{J}\) — whether a process is one of PyPSA's active_assets, by its active flag alone, without build year and lifetime. A unit that is active in no snapshot of the horizon still counts. PyPSA refuses one that differs by scenario (constants.py:54) |
| \(\mathrm{M}^{z}\) | Process_big_m over \(\mathcal{J} \times \Xi\), absent where the data has no row — the bound a committed extendable process's big-M rows release it by, data prep. It is the build cap p_nom_max times the highest p_max_pu, where the cap is finite and positive. Elsewhere it is committable_big_m times the highest p_max_pu (components.py:1082-1152). Without that keyword, it is ten times the largest of the peak total load and the component's largest finite p_nom and p_nom_max. Where there is none of them, it is 1e6. Below the internal power a solve wants, it caps that internal power |
| \(\mathrm{c}^{\mathrm{cap},z}\) | Process_capital_cost over \(\mathcal{J} \times \Xi\) — cost of one unit of nominal power for the modelled horizon (PyPSA's periodized_cost), data prep. It is overnight_cost as an annuity over lifetime at discount_rate, times nyears, where overnight_cost is given, and capital_cost where it is not. Both add fom_cost (components.py:1157-1178, costs.py:102-203) |
| \(\mathrm{W}^{z}\) | Process_capital_weight over \(\mathcal{J}\) — the sum of period weights a process is active in. It is PyPSA's active * period_weighting, summed, data prep |
| \(\mathrm{com}^{z}\) | Process_committable over \(\mathcal{J}\) — whether internal power is gated by an on/off status decision |
| \(\mathrm{mnt}^{z}\) | Process_maintainable over \(\mathcal{J}\) — whether a process must be taken off for maintenance within the horizon: in any scenario, as PyPSA takes the union over them (components.py:1000-1003) |
| \(\mathrm{n}^{z,\mathrm{mnt}}\) | Process_maintenance_events over \(\mathcal{J} \times \Xi\) — how many maintenance events occur within the horizon |
| \(\gamma^{z}\) | Process_maintenance_pu over \(\mathcal{J} \times \Xi\) — the share of the build a maintenance event takes off |
| \(\mathrm{blk}^{z}\) | Process_maintenance_start_blocked over \(\mathcal{J} \times \Xi \times \mathcal{T}\) — true where no maintenance event may start, data prep. The snapshots it would cover there run past the end of the horizon or into one the process is not active in. It is PyPSA's active & ~valid, from maintenance_duration and the generator weightings |
| \(\mathrm{c}^{z}\) | Process_marginal_cost over \(\mathcal{J} \times \Xi \times \mathcal{T}\) — cost of one unit of internal power |
| \(\mathrm{c}^{z,(2)}\) | Process_marginal_cost_quadratic over \(\mathcal{J} \times \Xi \times \mathcal{T}\) — cost of the square of one unit of internal power |
| \(\mathrm{N}^{z,\mathrm{fix}}\) | Process_modules_installed over \(\mathcal{J} \times \Xi\) — how many whole modules a committable build has in place, data prep. It is Process_p_nom / Process_p_nom_mod where a fixed build is modular, and one where it is not. PyPSA refuses a fixed modular build whose nominal power is not a whole number of modules |
| \(\mathrm{cyc}^{z}\) | Process_output_cyclic_delay over \(\mathcal{R}\) — whether a delayed port's transfer wraps from the end of its investment period (PyPSA's cyclic_delay0, cyclic_delay1, …). Where it does not, the energy still in transit at each period's first snapshots is lost. The flag is the same in every scenario, as the delay is |
| \(\mathrm{d}^{z}\) | Process_output_delay over \(\mathcal{R}\) — snapshots a port's transfer lags its process's internal power (PyPSA's delay0, delay1, … read long). In data prep you divide it by the snapshot_weightings.generators value and round it up. It is zero for a port that transfers at once. A port has the same delay in every scenario, as a link's port has |
| \(\overline{\mathrm{z}}\) | Process_p_max_pu over \(\mathcal{J} \times \Xi \times \mathcal{T}\) — most internal power, per unit of nominal power |
| \(\underline{\mathrm{z}}\) | Process_p_min_pu over \(\mathcal{J} \times \Xi \times \mathcal{T}\) — least internal power, per unit of nominal power: negative for a process that runs both ways |
| \(\mathrm{nonneg}^{z}\) | Process_p_min_pu_nonneg over \(\mathcal{J}\) — true where none of the process's own minimums-per-unit is negative. It is PyPSA's per-unit (p_min_pu >= 0).all() over every snapshot and scenario, data prep |
| \(\mathrm{z}^{\mathrm{nom}}\) | Process_p_nom over \(\mathcal{J} \times \Xi\) — nominal internal power |
| \(\mathrm{ext}^{z}\) | Process_p_nom_extendable over \(\mathcal{J}\) — whether the nominal internal power is a decision |
| \(\overline{\mathrm{z}}^{\mathrm{nom}}\) | Process_p_nom_max over \(\mathcal{J} \times \Xi\) — most nominal power an extendable process may be built at |
| \(\underline{\mathrm{z}}^{\mathrm{nom}}\) | Process_p_nom_min over \(\mathcal{J} \times \Xi\) — least nominal power an extendable process may be built at |
| \(\mathrm{z}^{\mathrm{mod}}\) | Process_p_nom_mod over \(\mathcal{J}\), absent where the data has no row — the module size a build comes in whole numbers of. No value means the build is continuous |
| \(\alpha\) | Process_rate over \(\mathcal{R} \times \Xi \times \mathcal{T}\) — the energy a port draws or delivers per unit of internal power (PyPSA's rate0, rate1, … read long). It is negative where the port withdraws and positive where it injects. A link is a process whose bus0 rate is minus one and whose output rates are its efficiencies. The rate at the snapshot the transfer arrives applies, so a delayed port transfers at its arrival snapshot's rate (constraints.py:1575) |
| \(\mathrm{c}^{z,\mathrm{dn}}\) | Process_shut_down_cost over \(\mathcal{J} \times \Xi \times \mathcal{T}\) — cost of one stop in this snapshot |
| \(\mathrm{c}^{z,\mathrm{on}}\) | Process_stand_by_cost over \(\mathcal{J} \times \Xi \times \mathcal{T}\) — cost of one snapshot spent on |
| \(\mathrm{c}^{z,\mathrm{up}}\) | Process_start_up_cost over \(\mathcal{J} \times \Xi \times \mathcal{T}\) — cost of one start in this snapshot |
| \(\mathrm{u}^{z,0}\) | Process_status_initial over \(\mathcal{J} \times \Xi\) — one where the process was on before the first snapshot, zero where off. It is PyPSA's up_time_before > 0 for a committable process, and one for a process that is not, whose ramp rows PyPSA starts from on (constraints.py:323), data prep. Under a rolling horizon, it is the status the previous window solved, a fraction where unit commitment is linearised |
| \(\mathrm{w}^{y}\) | period_weight_objective over \(\mathcal{Y}\) — PyPSA's investment_period_weightings.objective — what a period's cost weighs. PyPSA reads it only under multi_investment_periods. Otherwise you feed one in data prep, whatever the column contains (optimize.py:231-233, :293-297) |
| \(\pi\) | scenario_weight over \(\Xi\) — PyPSA's scenario_weightings.weight — the probability of a future |
| \(\mathrm{w}\) | snapshot_weightings_objective over \(\mathcal{T}\) — PyPSA's snapshot_weightings.objective — hours a snapshot weighs in the cost |
Conditions¶
| Symbol | Meaning |
|---|---|
| \(\mathrm{Generator\_com\_ext}\) | Generator_com_ext over \(\mathcal{G} \times \mathcal{T}\) — a committable generator with an extendable, non-modular build that is active in the snapshot's period. These are PyPSA's com-ext rows, whose status is relaxed against the chosen build |
| \(\mathrm{Generator\_committed}\) | Generator_committed over \(\mathcal{G} \times \mathcal{T}\) — a committable generator that is active in the snapshot's period: every unit-commitment row's set |
| \(\mathrm{Generator\_maint\_ext}\) | Generator_maint_ext over \(\mathcal{G} \times \mathcal{T}\) — a maintainable generator with an extendable build that is active in the snapshot's period, unless it is committable and modular. These are the maintenance rows against the chosen build |
| \(\mathrm{Generator\_marginal\_cost\_curve}\) | Generator_marginal_cost_curve over \(\mathcal{G}\) — a generator that pays along a piecewise marginal_cost curve: one of PyPSA's active_assets with curve data (optimize.py:307, piecewise.py:230-257) |
| \(\mathrm{Link\_com\_ext}\) | Link_com_ext over \(\mathcal{L} \times \mathcal{T}\) — a committable link with an extendable, non-modular build that is active in the snapshot's period. These are PyPSA's com-ext rows, whose status is relaxed against the chosen build |
| \(\mathrm{Link\_committed}\) | Link_committed over \(\mathcal{L} \times \mathcal{T}\) — a committable link that is active in the snapshot's period: every unit-commitment row's set |
| \(\mathrm{Link\_maint\_ext}\) | Link_maint_ext over \(\mathcal{L} \times \mathcal{T}\) — a maintainable link with an extendable build that is active in the snapshot's period, unless it is committable and modular. These are the maintenance rows against the chosen build |
| \(\mathrm{Process\_com\_ext}\) | Process_com_ext over \(\mathcal{J} \times \mathcal{T}\) — a committable process with an extendable, non-modular build that is active in the snapshot's period. These are PyPSA's com-ext rows, whose status is relaxed against the chosen build |
| \(\mathrm{Process\_committed}\) | Process_committed over \(\mathcal{J} \times \mathcal{T}\) — a committable process that is active in the snapshot's period: every unit-commitment row's set |
| \(\mathrm{Process\_maint\_ext}\) | Process_maint_ext over \(\mathcal{J} \times \mathcal{T}\) — a maintainable process with an extendable build that is active in the snapshot's period, unless it is committable and modular. These are the maintenance rows against the chosen build |
Variables¶
| Symbol | Meaning |
|---|---|
| \(\mu\) | Generator_maintenance over \(\mathcal{G} \times \Xi \times \mathcal{T}\), \(0\) where the mask leaves it out — Generator-maintenance — whether a maintainable generator is in maintenance: continuous, and one exactly where an event covers the snapshot |
| \(\mu^{\mathrm{nom}}\) | Generator_maintenance_capacity over \(\mathcal{G} \times \Xi \times \mathcal{T}\), \(0\) where the mask leaves it out — Generator-maintenance_capacity — the chosen build while in maintenance, zero otherwise: the product the maintcap rows linearise |
| \(\mu^{\mathrm{up}}\) | Generator_maintenance_start over \(\mathcal{G} \times \Xi \times \mathcal{T}\), \(0\) where the mask leaves it out — Generator-maintenance_start — whether a maintenance event starts in this snapshot |
| \(\mu^{u}\) | Generator_maintenance_status over \(\mathcal{G} \times \Xi \times \mathcal{T}\), \(0\) where the mask leaves it out — Generator-maintenance_status — the status while in maintenance, zero otherwise: the product the maint-status rows linearise, so a unit in maintenance may also be off |
| \(C^{\mathrm{curve}}\) | Generator_marginal_cost_piecewise over \(\mathcal{G} \times \Xi \times \mathcal{T}\) — Generator-marginal_cost_piecewise — the running cost of a generator that pays along a curve, held above the curve |
| \(N\) | Generator_n_mod over \(\mathcal{G}\) — Generator-n_mod — how many modules of an extendable modular build. A unit that is not active has none |
| \(p\) | Generator_p over \(\mathcal{G} \times \Xi \times \mathcal{T}\) — Generator-p — output of a generator in a snapshot |
| \(P\) | Generator_p_nom_ext over \(\mathcal{G}\) — Generator-p_nom — nominal power where it is a decision, for a generator that is active. A fixed build is the parameter of the same PyPSA name |
| \(\mathit{dn}\) | Generator_shut_down over \(\mathcal{G} \times \Xi \times \mathcal{T}\) — Generator-shut_down — how much of a committable unit turns off this snapshot, capped as the status is |
| \(\mathit{up}\) | Generator_start_up over \(\mathcal{G} \times \Xi \times \mathcal{T}\) — Generator-start_up — how much of a committable unit turns on this snapshot, capped as the status is |
| \(u\) | Generator_status over \(\mathcal{G} \times \Xi \times \mathcal{T}\) — Generator-status — how much of a committable unit is on. It is an integer the rows below cap at one, or at the module count where the build is modular |
| \(\mu^{f}\) | Link_maintenance over \(\mathcal{L} \times \Xi \times \mathcal{T}\), \(0\) where the mask leaves it out — Link-maintenance — whether a maintainable link is in maintenance: continuous, and one exactly where an event covers the snapshot |
| \(\mu^{f,\mathrm{nom}}\) | Link_maintenance_capacity over \(\mathcal{L} \times \Xi \times \mathcal{T}\), \(0\) where the mask leaves it out — Link-maintenance_capacity — the chosen build while in maintenance, zero otherwise: the product the maintcap rows linearise |
| \(\mu^{f,\mathrm{up}}\) | Link_maintenance_start over \(\mathcal{L} \times \Xi \times \mathcal{T}\), \(0\) where the mask leaves it out — Link-maintenance_start — whether a maintenance event starts in this snapshot |
| \(\mu^{f,u}\) | Link_maintenance_status over \(\mathcal{L} \times \Xi \times \mathcal{T}\), \(0\) where the mask leaves it out — Link-maintenance_status — the status while in maintenance, zero otherwise: the product the maint-status rows linearise, so a unit in maintenance may also be off |
| \(N^{f}\) | Link_n_mod over \(\mathcal{L}\) — Link-n_mod — how many modules of an extendable modular build. A unit that is not active has none |
| \(f\) | Link_p over \(\mathcal{L} \times \Xi \times \mathcal{T}\) — Link-p — PyPSA's p0, the flow measured at the Link_bus0 end. A positive value withdraws there and injects at every bus the link's output ports deliver to |
| \(F\) | Link_p_nom_ext over \(\mathcal{L}\) — Link-p_nom — nominal power where it is a decision, for a link that is active. A fixed build is the parameter of the same PyPSA name |
| \(\mathit{dn}^{f}\) | Link_shut_down over \(\mathcal{L} \times \Xi \times \mathcal{T}\) — Link-shut_down — how much of a committable link turns off this snapshot, capped as the status is |
| \(\mathit{up}^{f}\) | Link_start_up over \(\mathcal{L} \times \Xi \times \mathcal{T}\) — Link-start_up — how much of a committable link turns on this snapshot, capped as the status is |
| \(u^{f}\) | Link_status over \(\mathcal{L} \times \Xi \times \mathcal{T}\) — Link-status — how much of a committable link is on. It is an integer the rows below cap at one, or at the module count where the build is modular |
| \(\mu^{z}\) | Process_maintenance over \(\mathcal{J} \times \Xi \times \mathcal{T}\), \(0\) where the mask leaves it out — Process-maintenance — whether a maintainable process is in maintenance: continuous, and one exactly where an event covers the snapshot |
| \(\mu^{z,\mathrm{nom}}\) | Process_maintenance_capacity over \(\mathcal{J} \times \Xi \times \mathcal{T}\), \(0\) where the mask leaves it out — Process-maintenance_capacity — the chosen build while in maintenance, zero otherwise: the product the maintcap rows linearise |
| \(\mu^{z,\mathrm{up}}\) | Process_maintenance_start over \(\mathcal{J} \times \Xi \times \mathcal{T}\), \(0\) where the mask leaves it out — Process-maintenance_start — whether a maintenance event starts in this snapshot |
| \(\mu^{z,u}\) | Process_maintenance_status over \(\mathcal{J} \times \Xi \times \mathcal{T}\), \(0\) where the mask leaves it out — Process-maintenance_status — the status while in maintenance, zero otherwise: the product the maint-status rows linearise, so a unit in maintenance may also be off |
| \(N^{z}\) | Process_n_mod over \(\mathcal{J}\) — Process-n_mod — how many modules of an extendable modular build. A unit that is not active has none |
| \(z\) | Process_p over \(\mathcal{J} \times \Xi \times \mathcal{T}\) — Process-p — PyPSA's internal power p. A positive value drives every port at its own rate, withdrawing where the rate is negative and injecting where it is positive |
| \(Z\) | Process_p_nom_ext over \(\mathcal{J}\) — Process-p_nom — nominal internal power where it is a decision, for a process that is active. A fixed build is the parameter of the same PyPSA name |
| \(\mathit{dn}^{z}\) | Process_shut_down over \(\mathcal{J} \times \Xi \times \mathcal{T}\) — Process-shut_down — how much of a committable process turns off this snapshot, capped as the status is |
| \(\mathit{up}^{z}\) | Process_start_up over \(\mathcal{J} \times \Xi \times \mathcal{T}\) — Process-start_up — how much of a committable process turns on this snapshot, capped as the status is |
| \(u^{z}\) | Process_status over \(\mathcal{J} \times \Xi \times \mathcal{T}\) — Process-status — how much of a committable process is on. It is an integer the rows below cap at one, or at the module count where the build is modular |
Definitions¶
| Symbol | Meaning |
|---|---|
| \(\mathit{Bus\_injection}\) | Bus_injection over \(\mathcal{N} \times \Xi \times \mathcal{T}\) — what every component puts into a bus, less what it takes out of it. PyPSA writes each term into the balance, and a load on its right-hand side |
| \(\mathit{Generator\_capex}\) | Generator_capex (scalar) |
| \(\mathit{Generator\_commitment\_opex}\) | Generator_commitment_opex over \(\Xi\) |
| \(\mathit{Generator\_injection}\) | Generator_injection over \(\mathcal{N} \times \Xi \times \mathcal{T}\) |
| \(\mathrm{Generator\_maintenance\_modules}\) | Generator_maintenance_modules over \(\mathcal{G} \times \Xi\) — how many modules of a modular committable generator can be on in maintenance: its build cap in modules where the build is extendable, and the modules installed where it is fixed (constraints.py:588-594) |
| \(\mathit{Generator\_opex}\) | Generator_opex over \(\Xi\) |
| \(\mathit{Generator\_previous\_status}\) | Generator_previous_status over \(\mathcal{G} \times \Xi \times \mathcal{T}\) — the commitment state a generator carries into a snapshot. It is off at the first snapshot it is active in past the first of the horizon. PyPSA reads a status it did not build as off there (constraints.py:391). It is the state carried over otherwise |
| \(\mathit{Generator\_running\_cost}\) | Generator_running_cost over \(\mathcal{G} \times \Xi \times \mathcal{T}\) — what a generator's output costs in a snapshot: the value read off its piecewise curve where it has one, and its linear marginal_cost otherwise. A curve replaces the linear cost, as PyPSA drops the unit from that term (optimize.py:333-348) |
| \(\mathit{Generator\_status\_carried\_over}\) | Generator_status_carried_over over \(\mathcal{G} \times \Xi \times \mathcal{T}\) — the state a generator carries over into a snapshot: the state it brought into the horizon at the first, the previous snapshot's after that |
| \(\mathit{Link\_capex}\) | Link_capex (scalar) |
| \(\mathit{Link\_commitment\_opex}\) | Link_commitment_opex over \(\Xi\) |
| \(\mathit{Link\_injection}\) | Link_injection over \(\mathcal{N} \times \Xi \times \mathcal{T}\) |
| \(\mathrm{Link\_maintenance\_modules}\) | Link_maintenance_modules over \(\mathcal{L} \times \Xi\) — how many modules of a modular committable link can be on in maintenance: its build cap in modules where the build is extendable, and the modules installed where it is fixed (constraints.py:588-594) |
| \(\mathit{Link\_opex}\) | Link_opex over \(\Xi\) |
| \(\mathit{Link\_output\_arrival}\) | Link_output_arrival over \(\mathcal{O} \times \Xi \times \mathcal{T}\) — what a link delivers to an output port at a snapshot. It is its flow delayed by the port's delay within its investment period. It is multiplied by the port's efficiency at the snapshot the flow arrives. Where the port is cyclic_delay, the delayed flow wraps from the period's end. Where it is not, the flow still in transit at the period's first snapshots is lost. A port that does not delay (delay zero) delivers its flow unshifted, cyclic or not |
| \(\mathit{Link\_previous\_status}\) | Link_previous_status over \(\mathcal{L} \times \Xi \times \mathcal{T}\) — the commitment state a link carries into a snapshot. It is off at the first snapshot it is active in past the first of the horizon. PyPSA reads a status it did not build as off there (constraints.py:391). It is the state carried over otherwise |
| \(\mathit{Link\_status\_carried\_over}\) | Link_status_carried_over over \(\mathcal{L} \times \Xi \times \mathcal{T}\) — the state a link carries over into a snapshot: the state it brought into the horizon at the first, the previous snapshot's after that |
| \(\mathrm{Load\_demand}\) | Load_demand over \(\mathcal{D} \times \Xi \times \mathcal{T}\) — what a load draws from its bus's balance. It is its demand times its sign where it is active, and nothing where it is not. PyPSA drops an inactive load from the balance (constraints.py:1591-1592) |
| \(\mathrm{Load\_injection}\) | Load_injection over \(\mathcal{N} \times \Xi \times \mathcal{T}\) |
| \(\mathit{Process\_capex}\) | Process_capex (scalar) |
| \(\mathit{Process\_commitment\_opex}\) | Process_commitment_opex over \(\Xi\) |
| \(\mathit{Process\_injection}\) | Process_injection over \(\mathcal{N} \times \Xi \times \mathcal{T}\) |
| \(\mathrm{Process\_maintenance\_modules}\) | Process_maintenance_modules over \(\mathcal{J} \times \Xi\) — how many modules of a modular committable process can be on in maintenance: its build cap in modules where the build is extendable, and the modules installed where it is fixed (constraints.py:588-594) |
| \(\mathit{Process\_opex}\) | Process_opex over \(\Xi\) |
| \(\mathit{Process\_output\_arrival}\) | Process_output_arrival over \(\mathcal{R} \times \Xi \times \mathcal{T}\) — what a process transfers at a port at a snapshot. It is its internal power delayed by the port's delay within its investment period. It is multiplied by the port's rate at the snapshot the transfer arrives. Where the port is cyclic_delay, the delayed transfer wraps from the period's end. Where it is not, the energy still in transit at the period's first snapshots is lost. A port that does not delay (delay zero) transfers at once, cyclic or not |
| \(\mathit{Process\_previous\_status}\) | Process_previous_status over \(\mathcal{J} \times \Xi \times \mathcal{T}\) — the commitment state a process carries into a snapshot. It is off at the first snapshot it is active in past the first of the horizon. PyPSA reads a status it did not build as off there (constraints.py:391). It is the state carried over otherwise |
| \(\mathit{Process\_status\_carried\_over}\) | Process_status_carried_over over \(\mathcal{J} \times \Xi \times \mathcal{T}\) — the state a process carries over into a snapshot: the state it brought into the horizon at the first, the previous snapshot's after that |
| \(\mathit{risk\_weighted\_opex}\) | risk_weighted_opex (scalar) |
| \(\mathit{scenario\_opex}\) | scenario_opex over \(\Xi\) — what a future costs to run: every operating term, weighted by the snapshot's hours and its period, before the scenario's own weight. A start and a stop cost what they cost, unweighted, as PyPSA adds them (optimize.py:448-468) |
| \(\mathit{total\_cost}\) | total_cost (scalar) — what the system costs. Capacity counts once per active period at its expected cost over the scenarios. Operation counts in expectation over the scenarios, and a share of it at the tail |
Notation¶
| Symbol | Meaning |
|---|---|
| \(t \ominus k\) | edge='wrap' — \(t-k\), cyclic |
| \(t \boxminus_{v} k\) | edge=v — \(t-k\), and \(v\) past the edge |
| \(t \ominus^{\mathrm{relation}(t)} k\) | within=relation[...] — \(t-k\) inside the group of \(t\) |
| \(\mathrm{pos}(t)\) | position() — the position of \(t\), counted from \(0\); \(t\) is the label |
Conditions¶
Generator_com_ext
Generator_committed
Generator_maint_ext
Generator_marginal_cost_curve
Link_com_ext
Link_committed
Link_maint_ext
Process_com_ext
Process_committed
Process_maint_ext
Variable domains¶
Generator_maintenance
Generator_maintenance_capacity
Generator_maintenance_start
Generator_maintenance_status
Generator_marginal_cost_piecewise
Generator_n_mod
Generator_p
Generator_p_nom_ext
Generator_shut_down
Generator_start_up
Generator_status
Link_maintenance
Link_maintenance_capacity
Link_maintenance_start
Link_maintenance_status
Link_n_mod
Link_p
Link_p_nom_ext
Link_shut_down
Link_start_up
Link_status
Process_maintenance
Process_maintenance_capacity
Process_maintenance_start
Process_maintenance_status
Process_n_mod
Process_p
Process_p_nom_ext
Process_shut_down
Process_start_up
Process_status
Definitions¶
Bus_injection
Generator_capex
Generator_commitment_opex
Generator_injection
Generator_maintenance_modules
Generator_opex
Generator_previous_status
Generator_running_cost
Generator_status_carried_over
Link_capex
Link_commitment_opex
Link_injection
Link_maintenance_modules
Link_opex
Link_output_arrival
Link_previous_status
Link_status_carried_over
Load_demand
Load_injection
Process_capex
Process_commitment_opex
Process_injection
Process_maintenance_modules
Process_opex
Process_output_arrival
Process_previous_status
Process_status_carried_over
risk_weighted_opex
scenario_opex
total_cost
Objective¶
Subject to¶
Bus_nodal_balance
Generator_com_ext_p_lower
Generator_com_ext_p_lower_nonneg
Generator_com_ext_p_upper_big_m
Generator_com_ext_p_upper_cap
Generator_com_mod_p_lower
Generator_com_mod_p_upper
Generator_com_p_lower
Generator_com_p_upper
Generator_com_transition_shut_down
Generator_com_transition_start_up
Generator_ext_p_nom_lower
Generator_ext_p_nom_upper
Generator_fix_p_lower
Generator_fix_p_upper
Generator_maint_event_count
Generator_maint_modstatus_lb
Generator_maint_modstatus_le_maint
Generator_maint_modstatus_le_status
Generator_maint_start_horizon
Generator_maint_status_lb
Generator_maint_status_le_maint
Generator_maint_status_le_status
Generator_maint_window
Generator_maintcap_lower_nommax
Generator_maintcap_lower_nommin
Generator_maintcap_upper
Generator_maintcap_upper_nommax
Generator_p_nom_modularity
Generator_shut_down_p_fixed_upper
Generator_shut_down_p_nom_variable_upper
Generator_start_up_p_fixed_upper
Generator_start_up_p_nom_variable_upper
Generator_status_p_fixed_upper
Generator_status_p_nom_variable_upper
Link_com_ext_p_lower
Link_com_ext_p_lower_nonneg
Link_com_ext_p_upper_big_m
Link_com_ext_p_upper_cap
Link_com_mod_p_lower
Link_com_mod_p_upper
Link_com_p_lower
Link_com_p_upper
Link_com_transition_shut_down
Link_com_transition_start_up
Link_ext_p_nom_lower
Link_ext_p_nom_upper
Link_fix_p_lower
Link_fix_p_upper
Link_maint_event_count
Link_maint_modstatus_lb
Link_maint_modstatus_le_maint
Link_maint_modstatus_le_status
Link_maint_start_horizon
Link_maint_status_lb
Link_maint_status_le_maint
Link_maint_status_le_status
Link_maint_window
Link_maintcap_lower_nommax
Link_maintcap_lower_nommin
Link_maintcap_upper
Link_maintcap_upper_nommax
Link_p_nom_modularity
Link_shut_down_p_fixed_upper
Link_shut_down_p_nom_variable_upper
Link_start_up_p_fixed_upper
Link_start_up_p_nom_variable_upper
Link_status_p_fixed_upper
Link_status_p_nom_variable_upper
Process_com_ext_p_lower
Process_com_ext_p_lower_nonneg
Process_com_ext_p_upper_big_m
Process_com_ext_p_upper_cap
Process_com_mod_p_lower
Process_com_mod_p_upper
Process_com_p_lower
Process_com_p_upper
Process_com_transition_shut_down
Process_com_transition_start_up
Process_ext_p_nom_lower
Process_ext_p_nom_upper
Process_maint_event_count
Process_maint_modstatus_lb
Process_maint_modstatus_le_maint
Process_maint_modstatus_le_status
Process_maint_start_horizon
Process_maint_status_lb
Process_maint_status_le_maint
Process_maint_status_le_status
Process_maint_window
Process_maintcap_lower_nommax
Process_maintcap_lower_nommin
Process_maintcap_upper
Process_maintcap_upper_nommax
Process_p_nom_modularity
Process_shut_down_p_fixed_upper
Process_shut_down_p_nom_variable_upper
Process_start_up_p_fixed_upper
Process_start_up_p_nom_variable_upper
Process_status_p_fixed_upper
Process_status_p_nom_variable_upper
The spec, differential/pypsa/rungs/rung_34_committable_maintenance.yaml — the file projected onto what this rung builds:
version: 0
description: The file states a plain `n.optimize()`, its multi-period class under the `multi_investment_periods`
keyword, and its stochastic class, which `n.set_scenarios(...)` sets. Every quantity chosen once the
future is known (second-stage) spans the futures dispatch is chosen in (`scenario`). Capacity is chosen
once, before the future is known, and paid at its expected cost in each investment `period` its build
year and lifetime span. Operation is the expectation over the scenarios' weights, with a share priced
at the worst-outcome mean cost (CVaR) only where a risk preference is set. A plain run's data has one
scenario, one period, unit weights, no outage and every `active` flag true, so the problem is the standard
one. On a security-constrained run, PyPSA copies each branch flow limit once per `outage`, and the outage
factors, `active` flags and scenario weights come from data prep.
dimensions:
breakpoint: {dtype: int, ordered: true, description: 'the corners of a piecewise-linear curve, in order.
A curve runs over the breakpoints its data has rows for, so curves may differ in length'}
bus: {description: network nodes}
generator: {description: 'generating units, each on one bus'}
link: {description: 'controllable connections, each from one bus to the buses it delivers to'}
link_output: {description: 'a link''s output ports, one label per port a link declares. The labels are
PyPSA''s `bus1`, `bus2`, … columns read long, data prep. A link of any number of output ports is
then one term in the balance'}
load: {description: 'demands, each on one bus'}
period: {dtype: int, ordered: true, description: investment periods. It is PyPSA's `investment_periods`}
process: {description: 'generalised multi-port converters, each with an internal power that every port
draws or delivers at its own rate'}
process_output: {description: 'a process''s ports, one label per port a process declares. The labels
are PyPSA''s `bus0`, `bus1`, …, each with a signed `rate`, data prep. A process of any number of
ports is then one term in the balance'}
scenario: {description: 'the futures dispatch is chosen in, each with a weight'}
snapshot: {dtype: datetime, ordered: true, description: dispatch periods}
relations:
Generator_bus: {key: generator, values: bus, description: the bus a generator sits on}
Generator_maintenance_cover:
key:
covered: snapshot
generator: generator
scenario: scenario
start: snapshot
missing: absent
description: the snapshots a maintenance event covers, by the snapshot it starts in, data prep. In
a scenario, they are the start and the snapshots after it, until their generator weightings reach
that scenario's `maintenance_duration`. A generator that is not maintainable has no rows
Link_bus0: {key: link, values: bus, description: the bus a link leaves}
Link_maintenance_cover:
key:
covered: snapshot
link: link
scenario: scenario
start: snapshot
missing: absent
description: the snapshots a maintenance event covers, by the snapshot it starts in, data prep. In
a scenario, they are the start and the snapshots after it, until their generator weightings reach
that scenario's `maintenance_duration`. A link that is not maintainable has no rows
Link_output_bus: {key: link_output, values: bus, description: 'the bus an output port delivers to. It
is PyPSA''s `bus1`, `bus2`, … columns. A link of three output ports is three labels here rather
than a third relation, so the file states any number of them'}
Link_output_link: {key: link_output, values: link, description: the link an output port belongs to}
Load_bus: {key: load, values: bus, description: the bus a load sits on}
Process_maintenance_cover:
key:
covered: snapshot
process: process
scenario: scenario
start: snapshot
missing: absent
description: the snapshots a maintenance event covers, by the snapshot it starts in, data prep. In
a scenario, they are the start and the snapshots after it, until their generator weightings reach
that scenario's `maintenance_duration`. A process that is not maintainable has no rows
Process_output_bus: {key: process_output, values: bus, description: 'the bus a port draws from or delivers
to. It is PyPSA''s `bus0`, `bus1`, … columns. A process of three ports is three labels here rather
than a third relation, so the file states any number of them'}
Process_output_process: {key: process_output, values: process, description: the process a port belongs
to}
snapshot_period: {key: snapshot, values: period, description: the investment period a snapshot falls
in}
parameters:
Bus_attached:
dims: [bus, snapshot]
dtype: bool
description: whether a load, a unit, a port or a branch that is active in the snapshot's period is
attached to the bus, data prep. A bus nothing is attached to has no balance row
Generator_active:
dims: [generator, snapshot]
dtype: bool
description: whether a generator is active in a snapshot's period. It is PyPSA's `active`, from build
year and lifetime, data prep
Generator_active_asset:
dims: [generator]
dtype: bool
description: whether a generator is one of PyPSA's `active_assets`, by its `active` flag alone, without
build year and lifetime. A unit that is active in no snapshot of the horizon still counts. PyPSA
refuses one that differs by scenario (`constants.py:54`)
Generator_big_m:
dims: [generator, scenario]
missing: absent
description: the bound a committed extendable generator's big-M rows release it by, data prep. It
is the build cap `p_nom_max` times the highest `p_max_pu`, where the cap is finite and positive.
Elsewhere it is `committable_big_m` times the highest `p_max_pu` (`components.py:1082-1152`). Without
that keyword, it is ten times the largest of the peak total load and the component's largest finite
`p_nom` and `p_nom_max`. Where there is none of them, it is 1e6. Below the output a solve wants,
it caps that output
Generator_capital_cost:
dims: [generator, scenario]
description: cost of one unit of nominal power for the modelled horizon (PyPSA's `periodized_cost`),
data prep. It is `overnight_cost` as an annuity over `lifetime` at `discount_rate`, times `nyears`,
where `overnight_cost` is given, and `capital_cost` where it is not. Both add `fom_cost` (`components.py:1157-1178`,
`costs.py:102-203`)
Generator_capital_weight:
dims: [generator]
description: the sum of period weights a generator is active in. It is PyPSA's `active * period_weighting`,
summed, data prep
Generator_committable:
dims: [generator]
dtype: bool
description: whether output is gated by an on/off status decision
Generator_maintainable:
dims: [generator]
dtype: bool
description: 'whether a generator must be taken off for maintenance within the horizon: in any scenario,
as PyPSA takes the union over them (`components.py:1000-1003`)'
Generator_maintenance_events:
dims: [generator, scenario]
dtype: int
description: how many maintenance events occur within the horizon
Generator_maintenance_pu:
dims: [generator, scenario]
description: the share of the build a maintenance event takes off
Generator_maintenance_start_blocked:
dims: [generator, scenario, snapshot]
dtype: bool
description: true where no maintenance event may start, data prep. The snapshots it would cover there
run past the end of the horizon or into one the generator is not active in. It is PyPSA's `active
& ~valid`, from `maintenance_duration` and the generator weightings
Generator_marginal_cost:
dims: [generator, scenario, snapshot]
description: cost of one unit of output
Generator_marginal_cost_curve_p:
dims: [breakpoint, generator]
missing: absent
description: 'the output at each breakpoint of a generator''s piecewise `marginal_cost` curve: PyPSA''s
`p_pu` breakpoints times `p_nom`, data prep. A generator with no curve has no rows'
Generator_marginal_cost_quadratic:
dims: [generator, scenario, snapshot]
description: cost of the square of one unit of output
Generator_modules_installed:
dims: [generator, scenario]
description: how many whole modules a committable build has in place, data prep. It is `Generator_p_nom
/ Generator_p_nom_mod` where a fixed build is modular, and one where it is not. PyPSA refuses a
fixed modular build whose nominal power is not a whole number of modules
Generator_p_max_pu:
dims: [generator, scenario, snapshot]
description: 'most output, per unit of nominal power: an availability profile'
Generator_p_min_pu:
dims: [generator, scenario, snapshot]
description: least output, per unit of nominal power
Generator_p_min_pu_nonneg:
dims: [generator]
dtype: bool
description: true where none of the generator's own minimums-per-unit is negative. It is PyPSA's per-unit
`(p_min_pu >= 0).all()` over every snapshot and scenario, data prep
Generator_p_nom:
dims: [generator, scenario]
description: nominal power
Generator_p_nom_extendable:
dims: [generator]
dtype: bool
description: whether the nominal power is a decision
Generator_p_nom_max:
dims: [generator, scenario]
description: most nominal power an extendable generator may be built at
Generator_p_nom_min:
dims: [generator, scenario]
description: least nominal power an extendable generator may be built at
Generator_p_nom_mod:
dims: [generator]
missing: absent
description: the module size a build comes in whole numbers of. No value means the build is continuous
Generator_shut_down_cost:
dims: [generator, scenario, snapshot]
description: cost of one stop in this snapshot
Generator_sign:
dims: [generator]
description: the sign output enters its bus's balance with. It is PyPSA's `sign`, `1` unless given,
`-1` for a unit that draws power. PyPSA refuses one that differs by scenario (`constants.py:46`)
Generator_stand_by_cost:
dims: [generator, scenario, snapshot]
description: cost of one snapshot spent on
Generator_start_up_cost:
dims: [generator, scenario, snapshot]
description: cost of one start in this snapshot
Generator_status_initial:
dims: [generator, scenario]
description: one where the unit was on before the first snapshot, zero where off. It is PyPSA's `up_time_before
> 0` for a committable unit, and one for a unit that is not, whose ramp rows PyPSA starts from on
(`constraints.py:323`), data prep. Under a rolling horizon, it is the status the previous window
solved, a fraction where unit commitment is linearised
Link_active:
dims: [link, snapshot]
dtype: bool
description: whether a link is active in a snapshot's period. It is PyPSA's `active`, data prep
Link_active_asset:
dims: [link]
dtype: bool
description: whether a link is one of PyPSA's `active_assets`, by its `active` flag alone, without
build year and lifetime. A unit that is active in no snapshot of the horizon still counts. PyPSA
refuses one that differs by scenario (`constants.py:54`)
Link_big_m:
dims: [link, scenario]
missing: absent
description: the bound a committed extendable link's big-M rows release it by, data prep. It is the
build cap `p_nom_max` times the highest `p_max_pu`, where the cap is finite and positive. Elsewhere
it is `committable_big_m` times the highest `p_max_pu` (`components.py:1082-1152`). Without that
keyword, it is ten times the largest of the peak total load and the component's largest finite `p_nom`
and `p_nom_max`. Where there is none of them, it is 1e6. Below the flow a solve wants, it caps that
flow
Link_capital_cost:
dims: [link, scenario]
description: cost of one unit of nominal power for the modelled horizon (PyPSA's `periodized_cost`),
data prep. It is `overnight_cost` as an annuity over `lifetime` at `discount_rate`, times `nyears`,
where `overnight_cost` is given, and `capital_cost` where it is not. Both add `fom_cost` (`components.py:1157-1178`,
`costs.py:102-203`)
Link_capital_weight:
dims: [link]
description: the sum of period weights a link is active in. It is PyPSA's `active * period_weighting`,
summed, data prep
Link_committable:
dims: [link]
dtype: bool
description: whether flow is gated by an on/off status decision
Link_efficiency:
dims: [link_output, scenario, snapshot]
description: 'share of the flow that arrives at an output port, PyPSA''s `efficiency`, `efficiency2`,
… read long: negative where that port consumes rather than delivers. Read at the snapshot the flow
arrives, so a delayed port delivers at its arrival snapshot''s efficiency (`constraints.py:1575`)'
Link_maintainable:
dims: [link]
dtype: bool
description: 'whether a link must be taken off for maintenance within the horizon: in any scenario,
as PyPSA takes the union over them (`components.py:1000-1003`)'
Link_maintenance_events:
dims: [link, scenario]
dtype: int
description: how many maintenance events occur within the horizon
Link_maintenance_pu:
dims: [link, scenario]
description: the share of the build a maintenance event takes off
Link_maintenance_start_blocked:
dims: [link, scenario, snapshot]
dtype: bool
description: true where no maintenance event may start, data prep. The snapshots it would cover there
run past the end of the horizon or into one the link is not active in. It is PyPSA's `active & ~valid`,
from `maintenance_duration` and the generator weightings
Link_marginal_cost:
dims: [link, scenario, snapshot]
description: cost of one unit of flow
Link_marginal_cost_quadratic:
dims: [link, scenario, snapshot]
description: cost of the square of one unit of flow
Link_modules_installed:
dims: [link, scenario]
description: how many whole modules a committable build has in place, data prep. It is `Link_p_nom
/ Link_p_nom_mod` where a fixed build is modular, and one where it is not. PyPSA refuses a fixed
modular build whose nominal power is not a whole number of modules
Link_output_cyclic_delay:
dims: [link_output]
dtype: bool
description: whether a delayed port's flow wraps from the end of its investment period (PyPSA's `cyclic_delay`,
`cyclic_delay2`, …). Where it does not, the flow still in transit at each period's first snapshots
is lost. The flag is the same in every scenario, as the delay is
Link_output_delay:
dims: [link_output]
dtype: int
description: snapshots a port's delivery lags its link's flow (PyPSA's `delay`, `delay2`, … read long).
In data prep you divide it by the `snapshot_weightings.generators` value and round it up. It is
zero for a port that delivers at once. A port has the same delay in every scenario, because PyPSA
refuses a delay that differs by scenario (`constants.py:55`)
Link_p_max_pu:
dims: [link, scenario, snapshot]
description: most flow, per unit of nominal power
Link_p_min_pu:
dims: [link, scenario, snapshot]
description: 'least flow, per unit of nominal power: negative for a link that carries both ways'
Link_p_min_pu_nonneg:
dims: [link]
dtype: bool
description: true where none of the link's own minimums-per-unit is negative. It is PyPSA's per-unit
`(p_min_pu >= 0).all()` over every snapshot and scenario, data prep
Link_p_nom:
dims: [link, scenario]
description: nominal power
Link_p_nom_extendable:
dims: [link]
dtype: bool
description: whether the nominal power is a decision
Link_p_nom_max:
dims: [link, scenario]
description: most nominal power an extendable link may be built at
Link_p_nom_min:
dims: [link, scenario]
description: least nominal power an extendable link may be built at
Link_p_nom_mod:
dims: [link]
missing: absent
description: the module size a build comes in whole numbers of. No value means the build is continuous
Link_shut_down_cost:
dims: [link, scenario, snapshot]
description: cost of one stop in this snapshot
Link_stand_by_cost:
dims: [link, scenario, snapshot]
description: cost of one snapshot spent on
Link_start_up_cost:
dims: [link, scenario, snapshot]
description: cost of one start in this snapshot
Link_status_initial:
dims: [link, scenario]
description: one where the link was on before the first snapshot, zero where off. It is PyPSA's `up_time_before
> 0` for a committable link, and one for a link that is not, whose ramp rows PyPSA starts from on
(`constraints.py:323`), data prep. Under a rolling horizon, it is the status the previous window
solved, a fraction where unit commitment is linearised
Load_active:
dims: [load]
dtype: bool
description: whether a load is active in the network, PyPSA's `active`. A load has no build year and
no lifetime, so the flag is the same in every snapshot. PyPSA refuses one that differs by scenario
(`constants.py:54`)
Load_p_set:
dims: [load, scenario, snapshot]
description: demand
Load_sign:
dims: [load]
description: the sign a load's demand enters its bus's balance with. It is PyPSA's `sign`, `-1` unless
given, `1` for a load that feeds its bus. PyPSA refuses one that differs by scenario (`constants.py:46`)
Process_active:
dims: [process, snapshot]
dtype: bool
description: whether a process is active in a snapshot's period. It is PyPSA's `active`, data prep
Process_active_asset:
dims: [process]
dtype: bool
description: whether a process is one of PyPSA's `active_assets`, by its `active` flag alone, without
build year and lifetime. A unit that is active in no snapshot of the horizon still counts. PyPSA
refuses one that differs by scenario (`constants.py:54`)
Process_big_m:
dims: [process, scenario]
missing: absent
description: the bound a committed extendable process's big-M rows release it by, data prep. It is
the build cap `p_nom_max` times the highest `p_max_pu`, where the cap is finite and positive. Elsewhere
it is `committable_big_m` times the highest `p_max_pu` (`components.py:1082-1152`). Without that
keyword, it is ten times the largest of the peak total load and the component's largest finite `p_nom`
and `p_nom_max`. Where there is none of them, it is 1e6. Below the internal power a solve wants,
it caps that internal power
Process_capital_cost:
dims: [process, scenario]
description: cost of one unit of nominal power for the modelled horizon (PyPSA's `periodized_cost`),
data prep. It is `overnight_cost` as an annuity over `lifetime` at `discount_rate`, times `nyears`,
where `overnight_cost` is given, and `capital_cost` where it is not. Both add `fom_cost` (`components.py:1157-1178`,
`costs.py:102-203`)
Process_capital_weight:
dims: [process]
description: the sum of period weights a process is active in. It is PyPSA's `active * period_weighting`,
summed, data prep
Process_committable:
dims: [process]
dtype: bool
description: whether internal power is gated by an on/off status decision
Process_maintainable:
dims: [process]
dtype: bool
description: 'whether a process must be taken off for maintenance within the horizon: in any scenario,
as PyPSA takes the union over them (`components.py:1000-1003`)'
Process_maintenance_events:
dims: [process, scenario]
dtype: int
description: how many maintenance events occur within the horizon
Process_maintenance_pu:
dims: [process, scenario]
description: the share of the build a maintenance event takes off
Process_maintenance_start_blocked:
dims: [process, scenario, snapshot]
dtype: bool
description: true where no maintenance event may start, data prep. The snapshots it would cover there
run past the end of the horizon or into one the process is not active in. It is PyPSA's `active
& ~valid`, from `maintenance_duration` and the generator weightings
Process_marginal_cost:
dims: [process, scenario, snapshot]
description: cost of one unit of internal power
Process_marginal_cost_quadratic:
dims: [process, scenario, snapshot]
description: cost of the square of one unit of internal power
Process_modules_installed:
dims: [process, scenario]
description: how many whole modules a committable build has in place, data prep. It is `Process_p_nom
/ Process_p_nom_mod` where a fixed build is modular, and one where it is not. PyPSA refuses a fixed
modular build whose nominal power is not a whole number of modules
Process_output_cyclic_delay:
dims: [process_output]
dtype: bool
description: whether a delayed port's transfer wraps from the end of its investment period (PyPSA's
`cyclic_delay0`, `cyclic_delay1`, …). Where it does not, the energy still in transit at each period's
first snapshots is lost. The flag is the same in every scenario, as the delay is
Process_output_delay:
dims: [process_output]
dtype: int
description: snapshots a port's transfer lags its process's internal power (PyPSA's `delay0`, `delay1`,
… read long). In data prep you divide it by the `snapshot_weightings.generators` value and round
it up. It is zero for a port that transfers at once. A port has the same delay in every scenario,
as a link's port has
Process_p_max_pu:
dims: [process, scenario, snapshot]
description: most internal power, per unit of nominal power
Process_p_min_pu:
dims: [process, scenario, snapshot]
description: 'least internal power, per unit of nominal power: negative for a process that runs both
ways'
Process_p_min_pu_nonneg:
dims: [process]
dtype: bool
description: true where none of the process's own minimums-per-unit is negative. It is PyPSA's per-unit
`(p_min_pu >= 0).all()` over every snapshot and scenario, data prep
Process_p_nom:
dims: [process, scenario]
description: nominal internal power
Process_p_nom_extendable:
dims: [process]
dtype: bool
description: whether the nominal internal power is a decision
Process_p_nom_max:
dims: [process, scenario]
description: most nominal power an extendable process may be built at
Process_p_nom_min:
dims: [process, scenario]
description: least nominal power an extendable process may be built at
Process_p_nom_mod:
dims: [process]
missing: absent
description: the module size a build comes in whole numbers of. No value means the build is continuous
Process_rate:
dims: [process_output, scenario, snapshot]
description: the energy a port draws or delivers per unit of internal power (PyPSA's `rate0`, `rate1`,
… read long). It is negative where the port withdraws and positive where it injects. A link is a
process whose `bus0` rate is minus one and whose output rates are its efficiencies. The rate at
the snapshot the transfer arrives applies, so a delayed port transfers at its arrival snapshot's
rate (`constraints.py:1575`)
Process_shut_down_cost:
dims: [process, scenario, snapshot]
description: cost of one stop in this snapshot
Process_stand_by_cost:
dims: [process, scenario, snapshot]
description: cost of one snapshot spent on
Process_start_up_cost:
dims: [process, scenario, snapshot]
description: cost of one start in this snapshot
Process_status_initial:
dims: [process, scenario]
description: one where the process was on before the first snapshot, zero where off. It is PyPSA's
`up_time_before > 0` for a committable process, and one for a process that is not, whose ramp rows
PyPSA starts from on (`constraints.py:323`), data prep. Under a rolling horizon, it is the status
the previous window solved, a fraction where unit commitment is linearised
period_weight_objective:
dims: [period]
description: PyPSA's `investment_period_weightings.objective` — what a period's cost weighs. PyPSA
reads it only under `multi_investment_periods`. Otherwise you feed one in data prep, whatever the
column contains (`optimize.py:231-233`, `:293-297`)
scenario_weight:
dims: [scenario]
description: PyPSA's `scenario_weightings.weight` — the probability of a future
snapshot_weightings_objective:
dims: [snapshot]
description: PyPSA's `snapshot_weightings.objective` — hours a snapshot weighs in the cost
variables:
Generator_maintenance:
dims: [generator, scenario, snapshot]
where: Generator_maintainable AND Generator_active
bounds: {lower: 0.0, upper: 1.0}
missing: 0.0
description: '`Generator-maintenance` — whether a maintainable generator is in maintenance: continuous,
and one exactly where an event covers the snapshot'
Generator_maintenance_capacity:
dims: [generator, scenario, snapshot]
where: Generator_maint_ext
bounds: {lower: 0.0}
missing: 0.0
description: '`Generator-maintenance_capacity` — the chosen build while in maintenance, zero otherwise:
the product the `maintcap` rows linearise'
Generator_maintenance_start:
dims: [generator, scenario, snapshot]
where: Generator_maintainable AND Generator_active
domain: binary
missing: 0.0
description: '`Generator-maintenance_start` — whether a maintenance event starts in this snapshot'
Generator_maintenance_status:
dims: [generator, scenario, snapshot]
where: Generator_maintainable AND Generator_committed AND NOT (Generator_p_nom_extendable AND NOT
(Generator_p_nom_mod > 0))
bounds: {lower: 0.0}
missing: 0.0
description: '`Generator-maintenance_status` — the status while in maintenance, zero otherwise: the
product the `maint-status` rows linearise, so a unit in maintenance may also be off'
Generator_n_mod:
dims: [generator]
where: Generator_p_nom_extendable AND Generator_p_nom_mod > 0 AND Generator_active_asset
bounds: {lower: 0.0}
domain: integer
description: '`Generator-n_mod` — how many modules of an extendable modular build. A unit that is
not active has none'
Generator_p:
dims: [generator, scenario, snapshot]
where: Generator_active
description: '`Generator-p` — output of a generator in a snapshot'
Generator_p_nom_ext:
dims: [generator]
where: Generator_p_nom_extendable AND Generator_active_asset
description: '`Generator-p_nom` — nominal power where it is a decision, for a generator that is active.
A fixed build is the parameter of the same PyPSA name'
Generator_shut_down:
dims: [generator, scenario, snapshot]
where: Generator_committed
bounds: {lower: 0.0}
domain: integer
description: '`Generator-shut_down` — how much of a committable unit turns off this snapshot, capped
as the status is'
Generator_start_up:
dims: [generator, scenario, snapshot]
where: Generator_committed
bounds: {lower: 0.0}
domain: integer
description: '`Generator-start_up` — how much of a committable unit turns on this snapshot, capped
as the status is'
Generator_status:
dims: [generator, scenario, snapshot]
where: Generator_committed
bounds: {lower: 0.0}
domain: integer
description: '`Generator-status` — how much of a committable unit is on. It is an integer the rows
below cap at one, or at the module count where the build is modular'
Link_maintenance:
dims: [link, scenario, snapshot]
where: Link_maintainable AND Link_active
bounds: {lower: 0.0, upper: 1.0}
missing: 0.0
description: '`Link-maintenance` — whether a maintainable link is in maintenance: continuous, and
one exactly where an event covers the snapshot'
Link_maintenance_capacity:
dims: [link, scenario, snapshot]
where: Link_maint_ext
bounds: {lower: 0.0}
missing: 0.0
description: '`Link-maintenance_capacity` — the chosen build while in maintenance, zero otherwise:
the product the `maintcap` rows linearise'
Link_maintenance_start:
dims: [link, scenario, snapshot]
where: Link_maintainable AND Link_active
domain: binary
missing: 0.0
description: '`Link-maintenance_start` — whether a maintenance event starts in this snapshot'
Link_maintenance_status:
dims: [link, scenario, snapshot]
where: Link_maintainable AND Link_committed AND NOT (Link_p_nom_extendable AND NOT (Link_p_nom_mod
> 0))
bounds: {lower: 0.0}
missing: 0.0
description: '`Link-maintenance_status` — the status while in maintenance, zero otherwise: the product
the `maint-status` rows linearise, so a unit in maintenance may also be off'
Link_n_mod:
dims: [link]
where: Link_p_nom_extendable AND Link_p_nom_mod > 0 AND Link_active_asset
bounds: {lower: 0.0}
domain: integer
description: '`Link-n_mod` — how many modules of an extendable modular build. A unit that is not active
has none'
Link_p:
dims: [link, scenario, snapshot]
where: Link_active
description: '`Link-p` — PyPSA''s `p0`, the flow measured at the `Link_bus0` end. A positive value
withdraws there and injects at every bus the link''s output ports deliver to'
Link_p_nom_ext:
dims: [link]
where: Link_p_nom_extendable AND Link_active_asset
description: '`Link-p_nom` — nominal power where it is a decision, for a link that is active. A fixed
build is the parameter of the same PyPSA name'
Link_shut_down:
dims: [link, scenario, snapshot]
where: Link_committed
bounds: {lower: 0.0}
domain: integer
description: '`Link-shut_down` — how much of a committable link turns off this snapshot, capped as
the status is'
Link_start_up:
dims: [link, scenario, snapshot]
where: Link_committed
bounds: {lower: 0.0}
domain: integer
description: '`Link-start_up` — how much of a committable link turns on this snapshot, capped as the
status is'
Link_status:
dims: [link, scenario, snapshot]
where: Link_committed
bounds: {lower: 0.0}
domain: integer
description: '`Link-status` — how much of a committable link is on. It is an integer the rows below
cap at one, or at the module count where the build is modular'
Process_maintenance:
dims: [process, scenario, snapshot]
where: Process_maintainable AND Process_active
bounds: {lower: 0.0, upper: 1.0}
missing: 0.0
description: '`Process-maintenance` — whether a maintainable process is in maintenance: continuous,
and one exactly where an event covers the snapshot'
Process_maintenance_capacity:
dims: [process, scenario, snapshot]
where: Process_maint_ext
bounds: {lower: 0.0}
missing: 0.0
description: '`Process-maintenance_capacity` — the chosen build while in maintenance, zero otherwise:
the product the `maintcap` rows linearise'
Process_maintenance_start:
dims: [process, scenario, snapshot]
where: Process_maintainable AND Process_active
domain: binary
missing: 0.0
description: '`Process-maintenance_start` — whether a maintenance event starts in this snapshot'
Process_maintenance_status:
dims: [process, scenario, snapshot]
where: Process_maintainable AND Process_committed AND NOT (Process_p_nom_extendable AND NOT (Process_p_nom_mod
> 0))
bounds: {lower: 0.0}
missing: 0.0
description: '`Process-maintenance_status` — the status while in maintenance, zero otherwise: the
product the `maint-status` rows linearise, so a unit in maintenance may also be off'
Process_n_mod:
dims: [process]
where: Process_p_nom_extendable AND Process_p_nom_mod > 0 AND Process_active_asset
bounds: {lower: 0.0}
domain: integer
description: '`Process-n_mod` — how many modules of an extendable modular build. A unit that is not
active has none'
Process_p:
dims: [process, scenario, snapshot]
where: Process_active
description: '`Process-p` — PyPSA''s internal power `p`. A positive value drives every port at its
own rate, withdrawing where the rate is negative and injecting where it is positive'
Process_p_nom_ext:
dims: [process]
where: Process_p_nom_extendable AND Process_active_asset
description: '`Process-p_nom` — nominal internal power where it is a decision, for a process that
is active. A fixed build is the parameter of the same PyPSA name'
Process_shut_down:
dims: [process, scenario, snapshot]
where: Process_committed
bounds: {lower: 0.0}
domain: integer
description: '`Process-shut_down` — how much of a committable process turns off this snapshot, capped
as the status is'
Process_start_up:
dims: [process, scenario, snapshot]
where: Process_committed
bounds: {lower: 0.0}
domain: integer
description: '`Process-start_up` — how much of a committable process turns on this snapshot, capped
as the status is'
Process_status:
dims: [process, scenario, snapshot]
where: Process_committed
bounds: {lower: 0.0}
domain: integer
description: '`Process-status` — how much of a committable process is on. It is an integer the rows
below cap at one, or at the module count where the build is modular'
Generator_marginal_cost_piecewise:
dims: [generator, scenario, snapshot]
where: Generator_marginal_cost_curve AND Generator_active
description: '`Generator-marginal_cost_piecewise` — the running cost of a generator that pays along
a curve, held above the curve'
constraints:
Bus_nodal_balance:
dims: [bus, scenario, snapshot]
where: Bus_attached
expression: Bus_injection == 0
description: '`Bus-nodal_balance` — what is generated at a bus meets the load there, less half of
every incident line''s and transformer''s loss. What is generated includes storage dispatch and
stores. It is net of what the links take away, plus what arrives over them after losses and any
delay at every port they deliver to. Each process port draws or delivers at its own rate, and each
passive branch carries its flow. PyPSA dissipates a branch''s loss half at either end. Each generator,
storage unit, store and load term enters with its component''s `sign` (`constraints.py:1480-1481`,
`:1592`), and an inactive load not at all. A bus nothing is attached to has no row. PyPSA refuses
one that carries load. The file states no assumption for it.'
Generator_com_ext_p_lower:
dims: [generator, scenario, snapshot]
where: Generator_com_ext
expression: Generator_p >= Generator_p_min_pu * (Generator_p_nom_ext - Generator_maintenance_pu *
Generator_maintenance_capacity) + Generator_big_m * Generator_status - Generator_big_m
description: '`Generator-com-ext-p-lower` — a committed extendable unit outputs at least its minimum
of the chosen build. Off, the big M releases the row'
Generator_com_ext_p_lower_nonneg:
dims: [generator, scenario, snapshot]
where: Generator_com_ext AND Generator_p_min_pu_nonneg
expression: Generator_p >= 0
description: '`Generator-com-ext-p-lower-nonneg` — where no minimum-per-unit is negative, output is
also plainly non-negative, a row the big-M lower cannot assert while the unit is off'
Generator_com_ext_p_upper_big_m:
dims: [generator, scenario, snapshot]
where: Generator_com_ext
expression: Generator_p <= Generator_big_m * Generator_status
description: '`Generator-com-ext-p-upper-bigM` — off, a unit outputs nothing. On, the big M is no
bound'
Generator_com_ext_p_upper_cap:
dims: [generator, scenario, snapshot]
where: Generator_com_ext
expression: Generator_p <= Generator_p_max_pu * (Generator_p_nom_ext - Generator_maintenance_pu *
Generator_maintenance_capacity)
description: '`Generator-com-ext-p-upper-cap` — a committed extendable unit outputs at most what is
available of the chosen build, whatever its status'
Generator_com_mod_p_lower:
dims: [generator, scenario, snapshot]
where: Generator_committed AND Generator_p_nom_mod > 0
expression: Generator_p >= Generator_p_min_pu * Generator_p_nom_mod * (Generator_status - Generator_maintenance_pu
* Generator_maintenance_status)
description: '`Generator-com-mod-p-lower` — a committed modular unit outputs at least its minimum
of one module, whether the build is fixed or a decision'
Generator_com_mod_p_upper:
dims: [generator, scenario, snapshot]
where: Generator_committed AND Generator_p_nom_mod > 0
expression: Generator_p <= Generator_p_max_pu * Generator_p_nom_mod * (Generator_status - Generator_maintenance_pu
* Generator_maintenance_status)
description: '`Generator-com-mod-p-upper` — a committed modular unit outputs at most one module''s
share, whether the build is fixed or a decision'
Generator_com_p_lower:
dims: [generator, scenario, snapshot]
where: Generator_committed AND NOT Generator_p_nom_extendable AND NOT (Generator_p_nom_mod > 0)
expression: Generator_p >= Generator_p_min_pu * Generator_p_nom * (Generator_status - Generator_maintenance_pu
* Generator_maintenance_status)
description: '`Generator-com-p-lower` — a committed unit outputs at least its minimum. Off, it outputs
at least nothing'
Generator_com_p_upper:
dims: [generator, scenario, snapshot]
where: Generator_committed AND NOT Generator_p_nom_extendable AND NOT (Generator_p_nom_mod > 0)
expression: Generator_p <= Generator_p_max_pu * Generator_p_nom * (Generator_status - Generator_maintenance_pu
* Generator_maintenance_status)
description: '`Generator-com-p-upper` — a committed unit outputs at most what is available. Off, it
outputs at most nothing'
Generator_com_transition_shut_down:
dims: [generator, scenario, snapshot]
where: Generator_committed
expression: Generator_shut_down >= Generator_previous_status - Generator_status
description: '`Generator-com-transition-shut-down` — turning off is a stop, counted against the state
the unit carried into the snapshot'
Generator_com_transition_start_up:
dims: [generator, scenario, snapshot]
where: Generator_committed
expression: Generator_start_up >= Generator_status - Generator_previous_status
description: '`Generator-com-transition-start-up` — turning on is a start, counted against the state
the unit carried into the snapshot'
Generator_ext_p_nom_lower:
dims: [generator, scenario]
where: Generator_p_nom_extendable AND Generator_active_asset
expression: Generator_p_nom_ext >= Generator_p_nom_min
description: '`Generator-ext-p_nom-lower` — the chosen build is at least its floor in every scenario'
Generator_ext_p_nom_upper:
dims: [generator, scenario]
where: Generator_p_nom_extendable AND Generator_active_asset AND Generator_p_nom_max
expression: Generator_p_nom_ext <= Generator_p_nom_max
description: '`Generator-ext-p_nom-upper` — the chosen build is at most its cap in every scenario.
A cap of infinity is no row'
Generator_fix_p_lower:
dims: [generator, scenario, snapshot]
where: not Generator_p_nom_extendable AND not Generator_committable AND Generator_active
expression: Generator_p >= Generator_p_min_pu * Generator_p_nom * (1 - Generator_maintenance_pu *
Generator_maintenance)
description: '`Generator-fix-p-lower` — a fixed generator outputs at least its minimum'
Generator_fix_p_upper:
dims: [generator, scenario, snapshot]
where: not Generator_p_nom_extendable AND not Generator_committable AND Generator_active
expression: Generator_p <= Generator_p_max_pu * Generator_p_nom * (1 - Generator_maintenance_pu *
Generator_maintenance)
description: '`Generator-fix-p-upper` — a fixed generator outputs at most what is available'
Generator_maint_event_count:
dims: [generator, scenario]
where: Generator_maintainable
expression: sum(Generator_maintenance_start, over=snapshot) == Generator_maintenance_events
description: '`Generator-maint-event-count` — a maintainable generator holds its number of maintenance
events over the horizon'
Generator_maint_modstatus_lb:
dims: [generator, scenario, snapshot]
where: Generator_maintainable AND Generator_committed AND Generator_p_nom_mod > 0
expression: Generator_maintenance_status >= Generator_status - Generator_maintenance_modules * (1
- Generator_maintenance)
description: '`Generator-maint-modstatus-lb` — in maintenance, every module on is on in maintenance'
Generator_maint_modstatus_le_maint:
dims: [generator, scenario, snapshot]
where: Generator_maintainable AND Generator_committed AND Generator_p_nom_mod > 0
expression: Generator_maintenance_status <= Generator_maintenance_modules * Generator_maintenance
description: '`Generator-maint-modstatus-le-maint` — out of maintenance, no module is on in maintenance.
In it, at most its modules in maintenance'
Generator_maint_modstatus_le_status:
dims: [generator, scenario, snapshot]
where: Generator_maintainable AND Generator_committed AND Generator_p_nom_mod > 0
expression: Generator_maintenance_status <= Generator_status
description: '`Generator-maint-modstatus-le-status` — the modules on in maintenance are at most the
modules on'
Generator_maint_start_horizon:
dims: [generator, scenario, snapshot]
where: Generator_maintainable AND Generator_active AND Generator_maintenance_start_blocked
expression: Generator_maintenance_start == 0
description: '`Generator-maint-start-horizon` — no event starts where it could not run its whole duration'
Generator_maint_status_lb:
dims: [generator, scenario, snapshot]
where: Generator_maintainable AND Generator_committed AND NOT Generator_p_nom_extendable AND NOT (Generator_p_nom_mod
> 0)
expression: Generator_maintenance_status >= Generator_status + Generator_maintenance - 1
description: '`Generator-maint-status-lb` — on and in maintenance, the status in maintenance is one'
Generator_maint_status_le_maint:
dims: [generator, scenario, snapshot]
where: Generator_maintainable AND Generator_committed AND NOT Generator_p_nom_extendable AND NOT (Generator_p_nom_mod
> 0)
expression: Generator_maintenance_status <= Generator_maintenance
description: '`Generator-maint-status-le-maint` — out of maintenance, the status in maintenance is
zero'
Generator_maint_status_le_status:
dims: [generator, scenario, snapshot]
where: Generator_maintainable AND Generator_committed AND NOT Generator_p_nom_extendable AND NOT (Generator_p_nom_mod
> 0)
expression: Generator_maintenance_status <= Generator_status
description: '`Generator-maint-status-le-status` — the status in maintenance is at most the status'
Generator_maint_window:
dims: [generator, scenario, snapshot]
where: Generator_maintainable AND Generator_active
expression: Generator_maintenance == sum(Generator_maintenance_start, over=start, by=Generator_maintenance_cover[covered])
description: '`Generator-maint-window` — a generator is in maintenance exactly where an event it started
covers the snapshot. Two events do not overlap, since the maintenance status is at most one'
Generator_maintcap_lower_nommax:
dims: [generator, scenario, snapshot]
where: Generator_maint_ext
expression: Generator_maintenance_capacity >= Generator_p_nom_ext - Generator_p_nom_max * (1 - Generator_maintenance)
description: '`Generator-maintcap_lower_nommax` — in maintenance, the whole chosen build is taken
off'
Generator_maintcap_lower_nommin:
dims: [generator, scenario, snapshot]
where: Generator_maint_ext AND Generator_p_nom_min > 0
expression: Generator_maintenance_capacity >= Generator_p_nom_min * Generator_maintenance
description: '`Generator-maintcap_lower_nommin` — in maintenance, at least the floor of the build
is taken off'
Generator_maintcap_upper:
dims: [generator, scenario, snapshot]
where: Generator_maint_ext
expression: Generator_maintenance_capacity <= Generator_p_nom_ext - Generator_p_nom_min * (1 - Generator_maintenance)
description: '`Generator-maintcap_upper` — the build taken off is at most the chosen build in maintenance,
and at most the build less its floor out of it'
Generator_maintcap_upper_nommax:
dims: [generator, scenario, snapshot]
where: Generator_maint_ext
expression: Generator_maintenance_capacity <= Generator_p_nom_max * Generator_maintenance
description: '`Generator-maintcap_upper_nommax` — out of maintenance, no build is taken off'
Generator_p_nom_modularity:
dims: [generator]
where: Generator_p_nom_extendable AND Generator_p_nom_mod > 0 AND Generator_active_asset
expression: Generator_p_nom_ext == Generator_p_nom_mod * Generator_n_mod
description: '`Generator-p_nom_modularity` — the chosen build is a whole number of modules'
Generator_shut_down_p_fixed_upper:
dims: [generator, scenario, snapshot]
where: Generator_committed AND NOT (Generator_p_nom_extendable AND Generator_p_nom_mod > 0)
expression: Generator_shut_down <= Generator_modules_installed
description: '`Generator-shut_down-p-fixed-upper` — a stop is at most the modules in place, an explicit
row as PyPSA writes it. The bound is one where the build is not modular, and the fixed build''s
whole count of modules where it is'
Generator_shut_down_p_nom_variable_upper:
dims: [generator, scenario, snapshot]
where: Generator_committed AND Generator_p_nom_extendable AND Generator_p_nom_mod > 0
expression: Generator_shut_down <= Generator_n_mod
description: '`Generator-shut_down-p_nom-variable-upper` — a modular unit stops only where a module
is built'
Generator_start_up_p_fixed_upper:
dims: [generator, scenario, snapshot]
where: Generator_committed AND NOT (Generator_p_nom_extendable AND Generator_p_nom_mod > 0)
expression: Generator_start_up <= Generator_modules_installed
description: '`Generator-start_up-p-fixed-upper` — a start is at most the modules in place, an explicit
row as PyPSA writes it. The bound is one where the build is not modular, and the fixed build''s
whole count of modules where it is'
Generator_start_up_p_nom_variable_upper:
dims: [generator, scenario, snapshot]
where: Generator_committed AND Generator_p_nom_extendable AND Generator_p_nom_mod > 0
expression: Generator_start_up <= Generator_n_mod
description: '`Generator-start_up-p_nom-variable-upper` — a modular unit starts only where a module
is built'
Generator_status_p_fixed_upper:
dims: [generator, scenario, snapshot]
where: Generator_committed AND NOT (Generator_p_nom_extendable AND Generator_p_nom_mod > 0)
expression: Generator_status <= Generator_modules_installed
description: '`Generator-status-p-fixed-upper` — a status is at most the modules in place, an explicit
row as PyPSA writes it. The bound is one where the build is not modular, and the fixed build''s
whole count of modules where it is'
Generator_status_p_nom_variable_upper:
dims: [generator, scenario, snapshot]
where: Generator_committed AND Generator_p_nom_extendable AND Generator_p_nom_mod > 0
expression: Generator_status <= Generator_n_mod
description: '`Generator-status-p_nom-variable-upper` — a modular unit is on only where a module is
built'
Link_com_ext_p_lower:
dims: [link, scenario, snapshot]
where: Link_com_ext
expression: Link_p >= Link_p_min_pu * (Link_p_nom_ext - Link_maintenance_pu * Link_maintenance_capacity)
+ Link_big_m * Link_status - Link_big_m
description: '`Link-com-ext-p-lower` — a committed extendable link flows at least its minimum of the
chosen build. Off, the big M releases the row'
Link_com_ext_p_lower_nonneg:
dims: [link, scenario, snapshot]
where: Link_com_ext AND Link_p_min_pu_nonneg
expression: Link_p >= 0
description: '`Link-com-ext-p-lower-nonneg` — where no minimum-per-unit is negative, flow is also
plainly non-negative, a row the big-M lower cannot assert while the link is off'
Link_com_ext_p_upper_big_m:
dims: [link, scenario, snapshot]
where: Link_com_ext
expression: Link_p <= Link_big_m * Link_status
description: '`Link-com-ext-p-upper-bigM` — off, a link flows nothing. On, the big M is no bound'
Link_com_ext_p_upper_cap:
dims: [link, scenario, snapshot]
where: Link_com_ext
expression: Link_p <= Link_p_max_pu * (Link_p_nom_ext - Link_maintenance_pu * Link_maintenance_capacity)
description: '`Link-com-ext-p-upper-cap` — a committed extendable link flows at most what is available
of the chosen build, whatever its status'
Link_com_mod_p_lower:
dims: [link, scenario, snapshot]
where: Link_committed AND Link_p_nom_mod > 0
expression: Link_p >= Link_p_min_pu * Link_p_nom_mod * (Link_status - Link_maintenance_pu * Link_maintenance_status)
description: '`Link-com-mod-p-lower` — a committed modular link flows at least its minimum of one
module, whether the build is fixed or a decision'
Link_com_mod_p_upper:
dims: [link, scenario, snapshot]
where: Link_committed AND Link_p_nom_mod > 0
expression: Link_p <= Link_p_max_pu * Link_p_nom_mod * (Link_status - Link_maintenance_pu * Link_maintenance_status)
description: '`Link-com-mod-p-upper` — a committed modular link flows at most one module''s share,
whether the build is fixed or a decision'
Link_com_p_lower:
dims: [link, scenario, snapshot]
where: Link_committed AND NOT Link_p_nom_extendable AND NOT (Link_p_nom_mod > 0)
expression: Link_p >= Link_p_min_pu * Link_p_nom * (Link_status - Link_maintenance_pu * Link_maintenance_status)
description: '`Link-com-p-lower` — a committed link flows at least its minimum. Off, it flows at least
nothing'
Link_com_p_upper:
dims: [link, scenario, snapshot]
where: Link_committed AND NOT Link_p_nom_extendable AND NOT (Link_p_nom_mod > 0)
expression: Link_p <= Link_p_max_pu * Link_p_nom * (Link_status - Link_maintenance_pu * Link_maintenance_status)
description: '`Link-com-p-upper` — a committed link flows at most what is available. Off, it flows
at most nothing'
Link_com_transition_shut_down:
dims: [link, scenario, snapshot]
where: Link_committed
expression: Link_shut_down >= Link_previous_status - Link_status
description: '`Link-com-transition-shut-down` — turning off is a stop, counted against the state the
link carried into the snapshot'
Link_com_transition_start_up:
dims: [link, scenario, snapshot]
where: Link_committed
expression: Link_start_up >= Link_status - Link_previous_status
description: '`Link-com-transition-start-up` — turning on is a start, counted against the state the
link carried into the snapshot'
Link_ext_p_nom_lower:
dims: [link, scenario]
where: Link_p_nom_extendable AND Link_active_asset
expression: Link_p_nom_ext >= Link_p_nom_min
description: '`Link-ext-p_nom-lower` — the chosen build is at least its floor in every scenario'
Link_ext_p_nom_upper:
dims: [link, scenario]
where: Link_p_nom_extendable AND Link_active_asset AND Link_p_nom_max
expression: Link_p_nom_ext <= Link_p_nom_max
description: '`Link-ext-p_nom-upper` — the chosen build is at most its cap in every scenario. A cap
of infinity is no row'
Link_fix_p_lower:
dims: [link, scenario, snapshot]
where: not Link_p_nom_extendable AND not Link_committable AND Link_active
expression: Link_p >= Link_p_min_pu * Link_p_nom * (1 - Link_maintenance_pu * Link_maintenance)
description: '`Link-fix-p-lower` — a fixed link carries at least its minimum, negative for the other
way'
Link_fix_p_upper:
dims: [link, scenario, snapshot]
where: not Link_p_nom_extendable AND not Link_committable AND Link_active
expression: Link_p <= Link_p_max_pu * Link_p_nom * (1 - Link_maintenance_pu * Link_maintenance)
description: '`Link-fix-p-upper` — a fixed link carries at most its nominal power'
Link_maint_event_count:
dims: [link, scenario]
where: Link_maintainable
expression: sum(Link_maintenance_start, over=snapshot) == Link_maintenance_events
description: '`Link-maint-event-count` — a maintainable link holds its number of maintenance events
over the horizon'
Link_maint_modstatus_lb:
dims: [link, scenario, snapshot]
where: Link_maintainable AND Link_committed AND Link_p_nom_mod > 0
expression: Link_maintenance_status >= Link_status - Link_maintenance_modules * (1 - Link_maintenance)
description: '`Link-maint-modstatus-lb` — in maintenance, every module on is on in maintenance'
Link_maint_modstatus_le_maint:
dims: [link, scenario, snapshot]
where: Link_maintainable AND Link_committed AND Link_p_nom_mod > 0
expression: Link_maintenance_status <= Link_maintenance_modules * Link_maintenance
description: '`Link-maint-modstatus-le-maint` — out of maintenance, no module is on in maintenance.
In it, at most its modules in maintenance'
Link_maint_modstatus_le_status:
dims: [link, scenario, snapshot]
where: Link_maintainable AND Link_committed AND Link_p_nom_mod > 0
expression: Link_maintenance_status <= Link_status
description: '`Link-maint-modstatus-le-status` — the modules on in maintenance are at most the modules
on'
Link_maint_start_horizon:
dims: [link, scenario, snapshot]
where: Link_maintainable AND Link_active AND Link_maintenance_start_blocked
expression: Link_maintenance_start == 0
description: '`Link-maint-start-horizon` — no event starts where it could not run its whole duration'
Link_maint_status_lb:
dims: [link, scenario, snapshot]
where: Link_maintainable AND Link_committed AND NOT Link_p_nom_extendable AND NOT (Link_p_nom_mod
> 0)
expression: Link_maintenance_status >= Link_status + Link_maintenance - 1
description: '`Link-maint-status-lb` — on and in maintenance, the status in maintenance is one'
Link_maint_status_le_maint:
dims: [link, scenario, snapshot]
where: Link_maintainable AND Link_committed AND NOT Link_p_nom_extendable AND NOT (Link_p_nom_mod
> 0)
expression: Link_maintenance_status <= Link_maintenance
description: '`Link-maint-status-le-maint` — out of maintenance, the status in maintenance is zero'
Link_maint_status_le_status:
dims: [link, scenario, snapshot]
where: Link_maintainable AND Link_committed AND NOT Link_p_nom_extendable AND NOT (Link_p_nom_mod
> 0)
expression: Link_maintenance_status <= Link_status
description: '`Link-maint-status-le-status` — the status in maintenance is at most the status'
Link_maint_window:
dims: [link, scenario, snapshot]
where: Link_maintainable AND Link_active
expression: Link_maintenance == sum(Link_maintenance_start, over=start, by=Link_maintenance_cover[covered])
description: '`Link-maint-window` — a link is in maintenance exactly where an event it started covers
the snapshot. Two events do not overlap, since the maintenance status is at most one'
Link_maintcap_lower_nommax:
dims: [link, scenario, snapshot]
where: Link_maint_ext
expression: Link_maintenance_capacity >= Link_p_nom_ext - Link_p_nom_max * (1 - Link_maintenance)
description: '`Link-maintcap_lower_nommax` — in maintenance, the whole chosen build is taken off'
Link_maintcap_lower_nommin:
dims: [link, scenario, snapshot]
where: Link_maint_ext AND Link_p_nom_min > 0
expression: Link_maintenance_capacity >= Link_p_nom_min * Link_maintenance
description: '`Link-maintcap_lower_nommin` — in maintenance, at least the floor of the build is taken
off'
Link_maintcap_upper:
dims: [link, scenario, snapshot]
where: Link_maint_ext
expression: Link_maintenance_capacity <= Link_p_nom_ext - Link_p_nom_min * (1 - Link_maintenance)
description: '`Link-maintcap_upper` — the build taken off is at most the chosen build in maintenance,
and at most the build less its floor out of it'
Link_maintcap_upper_nommax:
dims: [link, scenario, snapshot]
where: Link_maint_ext
expression: Link_maintenance_capacity <= Link_p_nom_max * Link_maintenance
description: '`Link-maintcap_upper_nommax` — out of maintenance, no build is taken off'
Link_p_nom_modularity:
dims: [link]
where: Link_p_nom_extendable AND Link_p_nom_mod > 0 AND Link_active_asset
expression: Link_p_nom_ext == Link_p_nom_mod * Link_n_mod
description: '`Link-p_nom_modularity` — the chosen build is a whole number of modules'
Link_shut_down_p_fixed_upper:
dims: [link, scenario, snapshot]
where: Link_committed AND NOT (Link_p_nom_extendable AND Link_p_nom_mod > 0)
expression: Link_shut_down <= Link_modules_installed
description: '`Link-shut_down-p-fixed-upper` — a stop is at most the modules in place, an explicit
row as PyPSA writes it. The bound is one where the build is not modular, and the fixed build''s
whole count of modules where it is'
Link_shut_down_p_nom_variable_upper:
dims: [link, scenario, snapshot]
where: Link_committed AND Link_p_nom_extendable AND Link_p_nom_mod > 0
expression: Link_shut_down <= Link_n_mod
description: '`Link-shut_down-p_nom-variable-upper` — a modular link stops only where a module is
built'
Link_start_up_p_fixed_upper:
dims: [link, scenario, snapshot]
where: Link_committed AND NOT (Link_p_nom_extendable AND Link_p_nom_mod > 0)
expression: Link_start_up <= Link_modules_installed
description: '`Link-start_up-p-fixed-upper` — a start is at most the modules in place, an explicit
row as PyPSA writes it. The bound is one where the build is not modular, and the fixed build''s
whole count of modules where it is'
Link_start_up_p_nom_variable_upper:
dims: [link, scenario, snapshot]
where: Link_committed AND Link_p_nom_extendable AND Link_p_nom_mod > 0
expression: Link_start_up <= Link_n_mod
description: '`Link-start_up-p_nom-variable-upper` — a modular link starts only where a module is
built'
Link_status_p_fixed_upper:
dims: [link, scenario, snapshot]
where: Link_committed AND NOT (Link_p_nom_extendable AND Link_p_nom_mod > 0)
expression: Link_status <= Link_modules_installed
description: '`Link-status-p-fixed-upper` — a status is at most the modules in place, an explicit
row as PyPSA writes it. The bound is one where the build is not modular, and the fixed build''s
whole count of modules where it is'
Link_status_p_nom_variable_upper:
dims: [link, scenario, snapshot]
where: Link_committed AND Link_p_nom_extendable AND Link_p_nom_mod > 0
expression: Link_status <= Link_n_mod
description: '`Link-status-p_nom-variable-upper` — a modular link is on only where a module is built'
Process_com_ext_p_lower:
dims: [process, scenario, snapshot]
where: Process_com_ext
expression: Process_p >= Process_p_min_pu * (Process_p_nom_ext - Process_maintenance_pu * Process_maintenance_capacity)
+ Process_big_m * Process_status - Process_big_m
description: '`Process-com-ext-p-lower` — a committed extendable process runs at least its minimum
of the chosen build. Off, the big M releases the row'
Process_com_ext_p_lower_nonneg:
dims: [process, scenario, snapshot]
where: Process_com_ext AND Process_p_min_pu_nonneg
expression: Process_p >= 0
description: '`Process-com-ext-p-lower-nonneg` — where no minimum-per-unit is negative, internal power
is also plainly non-negative, a row the big-M lower cannot assert while the process is off'
Process_com_ext_p_upper_big_m:
dims: [process, scenario, snapshot]
where: Process_com_ext
expression: Process_p <= Process_big_m * Process_status
description: '`Process-com-ext-p-upper-bigM` — off, a process does not run. On, the big M is no bound'
Process_com_ext_p_upper_cap:
dims: [process, scenario, snapshot]
where: Process_com_ext
expression: Process_p <= Process_p_max_pu * (Process_p_nom_ext - Process_maintenance_pu * Process_maintenance_capacity)
description: '`Process-com-ext-p-upper-cap` — a committed extendable process runs at most what is
available of the chosen build, whatever its status'
Process_com_mod_p_lower:
dims: [process, scenario, snapshot]
where: Process_committed AND Process_p_nom_mod > 0
expression: Process_p >= Process_p_min_pu * Process_p_nom_mod * (Process_status - Process_maintenance_pu
* Process_maintenance_status)
description: '`Process-com-mod-p-lower` — a committed modular process runs at least its minimum of
one module, whether the build is fixed or a decision'
Process_com_mod_p_upper:
dims: [process, scenario, snapshot]
where: Process_committed AND Process_p_nom_mod > 0
expression: Process_p <= Process_p_max_pu * Process_p_nom_mod * (Process_status - Process_maintenance_pu
* Process_maintenance_status)
description: '`Process-com-mod-p-upper` — a committed modular process runs at most one module''s share,
whether the build is fixed or a decision'
Process_com_p_lower:
dims: [process, scenario, snapshot]
where: Process_committed AND NOT Process_p_nom_extendable AND NOT (Process_p_nom_mod > 0)
expression: Process_p >= Process_p_min_pu * Process_p_nom * (Process_status - Process_maintenance_pu
* Process_maintenance_status)
description: '`Process-com-p-lower` — a committed process runs at least its minimum. Off, it runs
at least nothing'
Process_com_p_upper:
dims: [process, scenario, snapshot]
where: Process_committed AND NOT Process_p_nom_extendable AND NOT (Process_p_nom_mod > 0)
expression: Process_p <= Process_p_max_pu * Process_p_nom * (Process_status - Process_maintenance_pu
* Process_maintenance_status)
description: '`Process-com-p-upper` — a committed process runs at most what is available. Off, it
runs at most nothing'
Process_com_transition_shut_down:
dims: [process, scenario, snapshot]
where: Process_committed
expression: Process_shut_down >= Process_previous_status - Process_status
description: '`Process-com-transition-shut-down` — turning off is a stop, counted against the state
the process carried into the snapshot'
Process_com_transition_start_up:
dims: [process, scenario, snapshot]
where: Process_committed
expression: Process_start_up >= Process_status - Process_previous_status
description: '`Process-com-transition-start-up` — turning on is a start, counted against the state
the process carried into the snapshot'
Process_ext_p_nom_lower:
dims: [process, scenario]
where: Process_p_nom_extendable AND Process_active_asset
expression: Process_p_nom_ext >= Process_p_nom_min
description: '`Process-ext-p_nom-lower` — the chosen build is at least its floor in every scenario'
Process_ext_p_nom_upper:
dims: [process, scenario]
where: Process_p_nom_extendable AND Process_active_asset AND Process_p_nom_max
expression: Process_p_nom_ext <= Process_p_nom_max
description: '`Process-ext-p_nom-upper` — the chosen build is at most its cap in every scenario. A
cap of infinity is no row'
Process_maint_event_count:
dims: [process, scenario]
where: Process_maintainable
expression: sum(Process_maintenance_start, over=snapshot) == Process_maintenance_events
description: '`Process-maint-event-count` — a maintainable process holds its number of maintenance
events over the horizon'
Process_maint_modstatus_lb:
dims: [process, scenario, snapshot]
where: Process_maintainable AND Process_committed AND Process_p_nom_mod > 0
expression: Process_maintenance_status >= Process_status - Process_maintenance_modules * (1 - Process_maintenance)
description: '`Process-maint-modstatus-lb` — in maintenance, every module on is on in maintenance'
Process_maint_modstatus_le_maint:
dims: [process, scenario, snapshot]
where: Process_maintainable AND Process_committed AND Process_p_nom_mod > 0
expression: Process_maintenance_status <= Process_maintenance_modules * Process_maintenance
description: '`Process-maint-modstatus-le-maint` — out of maintenance, no module is on in maintenance.
In it, at most its modules in maintenance'
Process_maint_modstatus_le_status:
dims: [process, scenario, snapshot]
where: Process_maintainable AND Process_committed AND Process_p_nom_mod > 0
expression: Process_maintenance_status <= Process_status
description: '`Process-maint-modstatus-le-status` — the modules on in maintenance are at most the
modules on'
Process_maint_start_horizon:
dims: [process, scenario, snapshot]
where: Process_maintainable AND Process_active AND Process_maintenance_start_blocked
expression: Process_maintenance_start == 0
description: '`Process-maint-start-horizon` — no event starts where it could not run its whole duration'
Process_maint_status_lb:
dims: [process, scenario, snapshot]
where: Process_maintainable AND Process_committed AND NOT Process_p_nom_extendable AND NOT (Process_p_nom_mod
> 0)
expression: Process_maintenance_status >= Process_status + Process_maintenance - 1
description: '`Process-maint-status-lb` — on and in maintenance, the status in maintenance is one'
Process_maint_status_le_maint:
dims: [process, scenario, snapshot]
where: Process_maintainable AND Process_committed AND NOT Process_p_nom_extendable AND NOT (Process_p_nom_mod
> 0)
expression: Process_maintenance_status <= Process_maintenance
description: '`Process-maint-status-le-maint` — out of maintenance, the status in maintenance is zero'
Process_maint_status_le_status:
dims: [process, scenario, snapshot]
where: Process_maintainable AND Process_committed AND NOT Process_p_nom_extendable AND NOT (Process_p_nom_mod
> 0)
expression: Process_maintenance_status <= Process_status
description: '`Process-maint-status-le-status` — the status in maintenance is at most the status'
Process_maint_window:
dims: [process, scenario, snapshot]
where: Process_maintainable AND Process_active
expression: Process_maintenance == sum(Process_maintenance_start, over=start, by=Process_maintenance_cover[covered])
description: '`Process-maint-window` — a process is in maintenance exactly where an event it started
covers the snapshot. Two events do not overlap, since the maintenance status is at most one'
Process_maintcap_lower_nommax:
dims: [process, scenario, snapshot]
where: Process_maint_ext
expression: Process_maintenance_capacity >= Process_p_nom_ext - Process_p_nom_max * (1 - Process_maintenance)
description: '`Process-maintcap_lower_nommax` — in maintenance, the whole chosen build is taken off'
Process_maintcap_lower_nommin:
dims: [process, scenario, snapshot]
where: Process_maint_ext AND Process_p_nom_min > 0
expression: Process_maintenance_capacity >= Process_p_nom_min * Process_maintenance
description: '`Process-maintcap_lower_nommin` — in maintenance, at least the floor of the build is
taken off'
Process_maintcap_upper:
dims: [process, scenario, snapshot]
where: Process_maint_ext
expression: Process_maintenance_capacity <= Process_p_nom_ext - Process_p_nom_min * (1 - Process_maintenance)
description: '`Process-maintcap_upper` — the build taken off is at most the chosen build in maintenance,
and at most the build less its floor out of it'
Process_maintcap_upper_nommax:
dims: [process, scenario, snapshot]
where: Process_maint_ext
expression: Process_maintenance_capacity <= Process_p_nom_max * Process_maintenance
description: '`Process-maintcap_upper_nommax` — out of maintenance, no build is taken off'
Process_p_nom_modularity:
dims: [process]
where: Process_p_nom_extendable AND Process_p_nom_mod > 0 AND Process_active_asset
expression: Process_p_nom_ext == Process_p_nom_mod * Process_n_mod
description: '`Process-p_nom_modularity` — the chosen build is a whole number of modules'
Process_shut_down_p_fixed_upper:
dims: [process, scenario, snapshot]
where: Process_committed AND NOT (Process_p_nom_extendable AND Process_p_nom_mod > 0)
expression: Process_shut_down <= Process_modules_installed
description: '`Process-shut_down-p-fixed-upper` — a stop is at most the modules in place, an explicit
row as PyPSA writes it. The bound is one where the build is not modular, and the fixed build''s
whole count of modules where it is'
Process_shut_down_p_nom_variable_upper:
dims: [process, scenario, snapshot]
where: Process_committed AND Process_p_nom_extendable AND Process_p_nom_mod > 0
expression: Process_shut_down <= Process_n_mod
description: '`Process-shut_down-p_nom-variable-upper` — a modular process stops only where a module
is built'
Process_start_up_p_fixed_upper:
dims: [process, scenario, snapshot]
where: Process_committed AND NOT (Process_p_nom_extendable AND Process_p_nom_mod > 0)
expression: Process_start_up <= Process_modules_installed
description: '`Process-start_up-p-fixed-upper` — a start is at most the modules in place, an explicit
row as PyPSA writes it. The bound is one where the build is not modular, and the fixed build''s
whole count of modules where it is'
Process_start_up_p_nom_variable_upper:
dims: [process, scenario, snapshot]
where: Process_committed AND Process_p_nom_extendable AND Process_p_nom_mod > 0
expression: Process_start_up <= Process_n_mod
description: '`Process-start_up-p_nom-variable-upper` — a modular process starts only where a module
is built'
Process_status_p_fixed_upper:
dims: [process, scenario, snapshot]
where: Process_committed AND NOT (Process_p_nom_extendable AND Process_p_nom_mod > 0)
expression: Process_status <= Process_modules_installed
description: '`Process-status-p-fixed-upper` — a status is at most the modules in place, an explicit
row as PyPSA writes it. The bound is one where the build is not modular, and the fixed build''s
whole count of modules where it is'
Process_status_p_nom_variable_upper:
dims: [process, scenario, snapshot]
where: Process_committed AND Process_p_nom_extendable AND Process_p_nom_mod > 0
expression: Process_status <= Process_n_mod
description: '`Process-status-p_nom-variable-upper` — a modular process is on only where a module
is built'
expressions:
Bus_injection:
dims: [bus, scenario, snapshot]
expression: ((Generator_injection + Link_injection) + Load_injection) + Process_injection
description: what every component puts into a bus, less what it takes out of it. PyPSA writes each
term into the balance, and a load on its right-hand side
Generator_capex: {expression: sum(scenario_weight * Generator_p_nom_ext * Generator_capital_cost * Generator_capital_weight)}
Generator_commitment_opex: {expression: 'sum(sum(((Generator_status * Generator_stand_by_cost) * snapshot_weightings_objective)
* at(period_weight_objective, by=snapshot_period[period]), over=generator), over=snapshot) + sum(sum((Generator_start_up
* Generator_start_up_cost) * at(period_weight_objective, by=snapshot_period[period]), over=generator),
over=snapshot) + sum(sum((Generator_shut_down * Generator_shut_down_cost) * at(period_weight_objective,
by=snapshot_period[period]), over=generator), over=snapshot)'}
Generator_injection: {expression: 'sum(Generator_sign * Generator_p, over=generator, by=Generator_bus[bus])'}
Generator_maintenance_modules:
dims: [generator, scenario]
description: 'how many modules of a modular committable generator can be on in maintenance: its build
cap in modules where the build is extendable, and the modules installed where it is fixed (`constraints.py:588-594`)'
cases:
extendable: {when: Generator_p_nom_extendable, expression: Generator_p_nom_max / Generator_p_nom_mod}
otherwise: Generator_modules_installed
Generator_opex: {expression: 'sum(sum((Generator_running_cost * snapshot_weightings_objective) * at(period_weight_objective,
by=snapshot_period[period]), over=generator), over=snapshot) + sum(sum((((Generator_p * Generator_p)
* Generator_marginal_cost_quadratic) * snapshot_weightings_objective) * at(period_weight_objective,
by=snapshot_period[period]), over=generator), over=snapshot)'}
Generator_previous_status:
dims: [generator, scenario, snapshot]
description: the commitment state a generator carries into a snapshot. It is off at the first snapshot
it is active in past the first of the horizon. PyPSA reads a status it did not build as off there
(`constraints.py:391`). It is the state carried over otherwise
cases:
opening_late: {when: 'position(snapshot) > 0 AND NOT shift(Generator_active, along=snapshot, offset=1)',
expression: '0'}
otherwise: Generator_status_carried_over
Generator_running_cost:
dims: [generator, scenario, snapshot]
description: 'what a generator''s output costs in a snapshot: the value read off its piecewise curve
where it has one, and its linear `marginal_cost` otherwise. A curve replaces the linear cost, as
PyPSA drops the unit from that term (`optimize.py:333-348`)'
cases:
curve: {when: Generator_marginal_cost_curve, expression: Generator_marginal_cost_piecewise}
otherwise: Generator_p * Generator_marginal_cost
Generator_status_carried_over:
dims: [generator, scenario, snapshot]
description: 'the state a generator carries over into a snapshot: the state it brought into the horizon
at the first, the previous snapshot''s after that'
cases:
opening: {when: position(snapshot) == 0, expression: Generator_status_initial}
otherwise: shift(Generator_status, along=snapshot, offset=1)
Link_capex: {expression: sum(scenario_weight * Link_p_nom_ext * Link_capital_cost * Link_capital_weight)}
Link_commitment_opex: {expression: 'sum(sum(((Link_status * Link_stand_by_cost) * snapshot_weightings_objective)
* at(period_weight_objective, by=snapshot_period[period]), over=link), over=snapshot) + sum(sum((Link_start_up
* Link_start_up_cost) * at(period_weight_objective, by=snapshot_period[period]), over=link), over=snapshot)
+ sum(sum((Link_shut_down * Link_shut_down_cost) * at(period_weight_objective, by=snapshot_period[period]),
over=link), over=snapshot)'}
Link_injection: {expression: '-sum(Link_p, over=link, by=Link_bus0[bus]) + sum(Link_output_arrival,
over=link_output, by=Link_output_bus[bus])'}
Link_maintenance_modules:
dims: [link, scenario]
description: 'how many modules of a modular committable link can be on in maintenance: its build cap
in modules where the build is extendable, and the modules installed where it is fixed (`constraints.py:588-594`)'
cases:
extendable: {when: Link_p_nom_extendable, expression: Link_p_nom_max / Link_p_nom_mod}
otherwise: Link_modules_installed
Link_opex: {expression: 'sum(sum(((Link_p * Link_marginal_cost) * snapshot_weightings_objective) * at(period_weight_objective,
by=snapshot_period[period]), over=link), over=snapshot) + sum(sum((((Link_p * Link_p) * Link_marginal_cost_quadratic)
* snapshot_weightings_objective) * at(period_weight_objective, by=snapshot_period[period]), over=link),
over=snapshot)'}
Link_output_arrival:
dims: [link_output, scenario, snapshot]
description: what a link delivers to an output port at a snapshot. It is its flow delayed by the port's
`delay` within its investment period. It is multiplied by the port's efficiency at the snapshot
the flow arrives. Where the port is `cyclic_delay`, the delayed flow wraps from the period's end.
Where it is not, the flow still in transit at the period's first snapshots is lost. A port that
does not delay (`delay` zero) delivers its flow unshifted, cyclic or not
cases:
wrapping: {when: Link_output_cyclic_delay, expression: 'shift(at(Link_p, by=Link_output_link[link]),
along=snapshot, offset=Link_output_delay, edge=''wrap'', within=snapshot_period[period]) * Link_efficiency'}
otherwise: shift(at(Link_p, by=Link_output_link[link]), along=snapshot, offset=Link_output_delay,
edge=0, within=snapshot_period[period]) * Link_efficiency
Link_previous_status:
dims: [link, scenario, snapshot]
description: the commitment state a link carries into a snapshot. It is off at the first snapshot
it is active in past the first of the horizon. PyPSA reads a status it did not build as off there
(`constraints.py:391`). It is the state carried over otherwise
cases:
opening_late: {when: 'position(snapshot) > 0 AND NOT shift(Link_active, along=snapshot, offset=1)',
expression: '0'}
otherwise: Link_status_carried_over
Link_status_carried_over:
dims: [link, scenario, snapshot]
description: 'the state a link carries over into a snapshot: the state it brought into the horizon
at the first, the previous snapshot''s after that'
cases:
opening: {when: position(snapshot) == 0, expression: Link_status_initial}
otherwise: shift(Link_status, along=snapshot, offset=1)
Load_demand:
dims: [load, scenario, snapshot]
description: what a load draws from its bus's balance. It is its demand times its sign where it is
active, and nothing where it is not. PyPSA drops an inactive load from the balance (`constraints.py:1591-1592`)
cases:
active: {when: Load_active, expression: Load_sign * Load_p_set}
otherwise: '0'
Load_injection: {expression: 'sum(Load_demand, over=load, by=Load_bus[bus])'}
Process_capex: {expression: sum(scenario_weight * Process_p_nom_ext * Process_capital_cost * Process_capital_weight)}
Process_commitment_opex: {expression: 'sum(sum(((Process_status * Process_stand_by_cost) * snapshot_weightings_objective)
* at(period_weight_objective, by=snapshot_period[period]), over=process), over=snapshot) + sum(sum((Process_start_up
* Process_start_up_cost) * at(period_weight_objective, by=snapshot_period[period]), over=process),
over=snapshot) + sum(sum((Process_shut_down * Process_shut_down_cost) * at(period_weight_objective,
by=snapshot_period[period]), over=process), over=snapshot)'}
Process_injection: {expression: 'sum(Process_output_arrival, over=process_output, by=Process_output_bus[bus])'}
Process_maintenance_modules:
dims: [process, scenario]
description: 'how many modules of a modular committable process can be on in maintenance: its build
cap in modules where the build is extendable, and the modules installed where it is fixed (`constraints.py:588-594`)'
cases:
extendable: {when: Process_p_nom_extendable, expression: Process_p_nom_max / Process_p_nom_mod}
otherwise: Process_modules_installed
Process_opex: {expression: 'sum(sum(((Process_p * Process_marginal_cost) * snapshot_weightings_objective)
* at(period_weight_objective, by=snapshot_period[period]), over=process), over=snapshot) + sum(sum((((Process_p
* Process_p) * Process_marginal_cost_quadratic) * snapshot_weightings_objective) * at(period_weight_objective,
by=snapshot_period[period]), over=process), over=snapshot)'}
Process_output_arrival:
dims: [process_output, scenario, snapshot]
description: what a process transfers at a port at a snapshot. It is its internal power delayed by
the port's `delay` within its investment period. It is multiplied by the port's rate at the snapshot
the transfer arrives. Where the port is `cyclic_delay`, the delayed transfer wraps from the period's
end. Where it is not, the energy still in transit at the period's first snapshots is lost. A port
that does not delay (`delay` zero) transfers at once, cyclic or not
cases:
wrapping: {when: Process_output_cyclic_delay, expression: 'shift(at(Process_p, by=Process_output_process[process]),
along=snapshot, offset=Process_output_delay, edge=''wrap'', within=snapshot_period[period])
* Process_rate'}
otherwise: shift(at(Process_p, by=Process_output_process[process]), along=snapshot, offset=Process_output_delay,
edge=0, within=snapshot_period[period]) * Process_rate
Process_previous_status:
dims: [process, scenario, snapshot]
description: the commitment state a process carries into a snapshot. It is off at the first snapshot
it is active in past the first of the horizon. PyPSA reads a status it did not build as off there
(`constraints.py:391`). It is the state carried over otherwise
cases:
opening_late: {when: 'position(snapshot) > 0 AND NOT shift(Process_active, along=snapshot, offset=1)',
expression: '0'}
otherwise: Process_status_carried_over
Process_status_carried_over:
dims: [process, scenario, snapshot]
description: 'the state a process carries over into a snapshot: the state it brought into the horizon
at the first, the previous snapshot''s after that'
cases:
opening: {when: position(snapshot) == 0, expression: Process_status_initial}
otherwise: shift(Process_status, along=snapshot, offset=1)
risk_weighted_opex: {expression: 'sum(scenario_weight * scenario_opex, over=scenario)'}
scenario_opex:
dims: [scenario]
expression: ((((Generator_opex + Generator_commitment_opex) + Link_opex) + Link_commitment_opex) +
Process_opex) + Process_commitment_opex
description: 'what a future costs to run: every operating term, weighted by the snapshot''s hours
and its period, before the scenario''s own weight. A start and a stop cost what they cost, unweighted,
as PyPSA adds them (`optimize.py:448-468`)'
total_cost:
dims: []
expression: ((Generator_capex + Link_capex) + Process_capex) + risk_weighted_opex
description: what the system costs. Capacity counts once per active period at its expected cost over
the scenarios. Operation counts in expectation over the scenarios, and a share of it at the tail
conditions:
Generator_com_ext: {condition: Generator_committable AND Generator_p_nom_extendable AND NOT (Generator_p_nom_mod
> 0) AND Generator_active, description: 'a committable generator with an extendable, non-modular
build that is active in the snapshot''s period. These are PyPSA''s `com-ext` rows, whose status
is relaxed against the chosen build'}
Generator_committed: {condition: Generator_committable AND Generator_active, description: 'a committable
generator that is active in the snapshot''s period: every unit-commitment row''s set'}
Generator_maint_ext: {condition: Generator_maintainable AND Generator_p_nom_extendable AND NOT (Generator_committable
AND Generator_p_nom_mod > 0) AND Generator_active, description: 'a maintainable generator with an
extendable build that is active in the snapshot''s period, unless it is committable and modular.
These are the maintenance rows against the chosen build'}
Generator_marginal_cost_curve: {condition: 'count(Generator_marginal_cost_curve_p, over=breakpoint)
> 0 AND Generator_active_asset', description: 'a generator that pays along a piecewise `marginal_cost`
curve: one of PyPSA''s `active_assets` with curve data (`optimize.py:307`, `piecewise.py:230-257`)'}
Link_com_ext: {condition: Link_committable AND Link_p_nom_extendable AND NOT (Link_p_nom_mod > 0) AND
Link_active, description: 'a committable link with an extendable, non-modular build that is active
in the snapshot''s period. These are PyPSA''s `com-ext` rows, whose status is relaxed against the
chosen build'}
Link_committed: {condition: Link_committable AND Link_active, description: 'a committable link that
is active in the snapshot''s period: every unit-commitment row''s set'}
Link_maint_ext: {condition: Link_maintainable AND Link_p_nom_extendable AND NOT (Link_committable AND
Link_p_nom_mod > 0) AND Link_active, description: 'a maintainable link with an extendable build
that is active in the snapshot''s period, unless it is committable and modular. These are the maintenance
rows against the chosen build'}
Process_com_ext: {condition: Process_committable AND Process_p_nom_extendable AND NOT (Process_p_nom_mod
> 0) AND Process_active, description: 'a committable process with an extendable, non-modular build
that is active in the snapshot''s period. These are PyPSA''s `com-ext` rows, whose status is relaxed
against the chosen build'}
Process_committed: {condition: Process_committable AND Process_active, description: 'a committable process
that is active in the snapshot''s period: every unit-commitment row''s set'}
Process_maint_ext: {condition: Process_maintainable AND Process_p_nom_extendable AND NOT (Process_committable
AND Process_p_nom_mod > 0) AND Process_active, description: 'a maintainable process with an extendable
build that is active in the snapshot''s period, unless it is committable and modular. These are
the maintenance rows against the chosen build'}
objective: {sense: minimize, expression: total_cost}
The prep — every table the spec declares, from the network — and the solve:
from differential.pypsa.prep import relation, static, varying, weighting
n = build() # the network from the PyPSA tab
sources = {
'bus': pl.Series('bus', list(names(n.buses.index).astype(str)), dtype=pl.String),
**{
dim: pl.Series(dim, list(names(n.static(component).index).astype(str)), dtype=pl.String)
for component, dim in DIM.items()
},
**scenarios(n),
**periods(n, multi),
**carriers(n, multi),
'snapshot': pl.Series('snapshot', list(timesteps(n)), dtype=pl.Datetime('us')),
'Generator_bus': relation(n, 'Generator', 'bus'),
'Link_bus0': relation(n, 'Link', 'bus0'),
'Load_bus': relation(n, 'Load', 'bus'),
'Bus_attached': attached(n),
'Generator_sign': per_component('Generator', first_scenario(n.generators['sign'])),
'Load_active': per_component('Load', first_scenario(loads['active']), bool),
'Load_p_set': varying(n, 'Load', 'p_set'),
'Load_sign': per_component('Load', first_scenario(loads['sign'])),
'snapshot_weightings_objective': weighting(n, 'objective'),
}
with sps.solve('differential/pypsa/rungs/rung_34_committable_maintenance.yaml', sources) as solution:
solution.objective # 6420.048611
The network, rung_34_committable_maintenance.py in the corpus — the spine plus what this rung adds:
# SPDX-FileCopyrightText: mathspec Contributors
#
# SPDX-License-Identifier: MIT
"""Rung 34: maintenance of committable units — a fixed, an extendable and a modular committable generator, link and process, each taken off for one event."""
from __future__ import annotations
import spine
def build():
"""The spine plus an east bus and nine maintainable committable components, with a dear peaker to cover them."""
n = spine.build()
n.add('Bus', 'east')
committable = {'committable': True, 'maintainable': True}
n.add(
'Generator',
'unit',
bus='north',
p_nom=60,
p_min_pu=0.3,
marginal_cost=5,
start_up_cost=10,
maintenance_duration=2,
**committable,
)
n.add(
'Generator',
'unit_ext',
bus='south',
p_nom_extendable=True,
p_nom_min=5,
p_nom_max=50,
capital_cost=10,
p_min_pu=0.2,
marginal_cost=4,
maintenance_duration=3,
maintenance_pu=0.5,
**committable,
)
n.add(
'Generator',
'unit_mod',
bus='south',
p_nom_extendable=True,
p_nom_mod=10,
p_nom_max=30,
capital_cost=8,
p_min_pu=0.5,
marginal_cost=3,
maintenance_duration=1,
**committable,
)
for component, ports in (('Link', {}), ('Process', {'rate0': -1.25})):
n.add(
component,
f'{component.lower()}_unit',
bus0='north',
bus1='east',
p_nom=40,
p_min_pu=0.2,
marginal_cost=1,
maintenance_duration=2,
**ports,
**committable,
)
n.add(
component,
f'{component.lower()}_ext',
bus0='south',
bus1='east',
p_nom_extendable=True,
p_nom_min=5,
p_nom_max=30,
capital_cost=5,
p_min_pu=0.2,
maintenance_duration=3,
maintenance_pu=0.5,
**ports,
**committable,
)
n.add(
component,
f'{component.lower()}_mod',
bus0='north',
bus1='east',
p_nom_extendable=True,
p_nom_mod=10,
p_nom_max=20,
capital_cost=3,
p_min_pu=0.5,
maintenance_duration=1,
**ports,
**committable,
)
n.add('Generator', 'east_peak', bus='east', p_nom=100, marginal_cost=60)
n.add('Load', 'east_load', bus='east', p_set=[50, 60, 40, 55])
return n
The data¶
Every table this spec declares was first declared by a lower rung; its values here are in the prep above.