Rung 64: commitment edges — a committable generator, link and process built in the later period start up when they open, and a committable unit without a build cap is released by an inferred big M¶
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 9140.0 on both sides; structure ✔ 29 constraints · 13 variables, name for name; size ✔ 205 rows · ✔ 97 columns · ✔ 361 nonzeros; duals — integer model, no duals; model for model: 33 blocks equal, 0 documented splits, 10 recorded deviations.
Rows and columns, PyPSA against specsolve, name for name
| row | PyPSA | specsolve |
|---|---|---|
Bus-nodal_balance |
16 | 16 |
Generator-com-ext-p-lower |
8 | 8 |
Generator-com-ext-p-lower-nonneg |
8 | 8 |
Generator-com-ext-p-upper-bigM |
8 | 8 |
Generator-com-ext-p-upper-cap |
8 | 8 |
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 |
1 | 1 |
Generator-fix-p-lower |
16 | 16 |
Generator-fix-p-upper |
16 | 16 |
Generator-shut_down-p-fixed-upper |
12 | 12 |
Generator-start_up-p-fixed-upper |
12 | 12 |
Generator-status-p-fixed-upper |
12 | 12 |
Link-com-p-lower |
4 | 4 |
Link-com-p-upper |
4 | 4 |
Link-com-transition-shut-down |
4 | 4 |
Link-com-transition-start-up |
4 | 4 |
Link-shut_down-p-fixed-upper |
4 | 4 |
Link-start_up-p-fixed-upper |
4 | 4 |
Link-status-p-fixed-upper |
4 | 4 |
Process-com-p-lower |
4 | 4 |
Process-com-p-upper |
4 | 4 |
Process-com-transition-shut-down |
4 | 4 |
Process-com-transition-start-up |
4 | 4 |
Process-shut_down-p-fixed-upper |
4 | 4 |
Process-start_up-p-fixed-upper |
4 | 4 |
Process-status-p-fixed-upper |
4 | 4 |
| column | PyPSA | specsolve |
|---|---|---|
Generator-p |
28 | 28 |
Generator-p_nom |
1 | 1 |
Generator-shut_down |
12 | 12 |
Generator-start_up |
12 | 12 |
Generator-status |
12 | 12 |
Link-p |
4 | 4 |
Link-shut_down |
4 | 4 |
Link-start_up |
4 | 4 |
Link-status |
4 | 4 |
Process-p |
4 | 4 |
Process-shut_down |
4 | 4 |
Process-start_up |
4 | 4 |
Process-status |
4 | 4 |
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}\) — generating units, each on one bus |
| \(\mathcal{L}\) | index \(l\) — link with \(\mathrm{Link\_bus0}: \mathcal{L} \to \mathcal{N},\ \mathrm{Link\_output\_link}: \mathcal{O} \to \mathcal{L}\) — 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\_output\_process}: \mathcal{R} \to \mathcal{J}\) — 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 — the futures dispatch is chosen in, each with a weight |
| \(\mathcal{T}\) | index \(t\) — snapshot with \(\mathrm{snapshot\_period}: \mathcal{T} \to \mathcal{Y}\) — 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{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 |
| \(\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{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{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{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 |
| \(\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{com}^{z}\) | Process_committable over \(\mathcal{J}\) — whether internal power is gated by an on/off status decision |
| \(\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{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 |
| \(\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\_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\_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{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 |
Variables¶
| Symbol | Meaning |
|---|---|
| \(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 |
| \(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 |
| \(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 |
| \(\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 |
| \(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 |
| \(\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}\) |
| \(\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\_commitment\_opex}\) | Link_commitment_opex over \(\Xi\) |
| \(\mathit{Link\_injection}\) | Link_injection over \(\mathcal{N} \times \Xi \times \mathcal{T}\) |
| \(\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\_commitment\_opex}\) | Process_commitment_opex over \(\Xi\) |
| \(\mathit{Process\_injection}\) | Process_injection over \(\mathcal{N} \times \Xi \times \mathcal{T}\) |
| \(\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_marginal_cost_curve
Link_committed
Process_committed
Variable domains¶
Generator_marginal_cost_piecewise
Generator_p
Generator_p_nom_ext
Generator_shut_down
Generator_start_up
Generator_status
Link_p
Link_shut_down
Link_start_up
Link_status
Process_p
Process_shut_down
Process_start_up
Process_status
Definitions¶
Bus_injection
Generator_capex
Generator_commitment_opex
Generator_injection
Generator_opex
Generator_previous_status
Generator_running_cost
Generator_status_carried_over
Link_commitment_opex
Link_injection
Link_opex
Link_output_arrival
Link_previous_status
Link_status_carried_over
Load_demand
Load_injection
Process_commitment_opex
Process_injection
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_p_lower
Generator_com_p_upper
Generator_com_transition_shut_down
Generator_com_transition_start_up
Generator_ext_p_nom_lower
Generator_fix_p_lower
Generator_fix_p_upper
Generator_shut_down_p_fixed_upper
Generator_start_up_p_fixed_upper
Generator_status_p_fixed_upper
Link_com_p_lower
Link_com_p_upper
Link_com_transition_shut_down
Link_com_transition_start_up
Link_shut_down_p_fixed_upper
Link_start_up_p_fixed_upper
Link_status_p_fixed_upper
Process_com_p_lower
Process_com_p_upper
Process_com_transition_shut_down
Process_com_transition_start_up
Process_shut_down_p_fixed_upper
Process_start_up_p_fixed_upper
Process_status_p_fixed_upper
The spec, differential/pypsa/rungs/rung_64_commitment_edges.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}
Link_bus0: {key: link, values: bus, description: the bus a link leaves}
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_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_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_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_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_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_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_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_committable:
dims: [process]
dtype: bool
description: whether internal power is gated by an on/off status decision
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_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_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_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_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_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_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_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_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
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_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
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
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_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
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
description: '`Generator-fix-p-upper` — a fixed generator outputs at most what is available'
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_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_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'
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
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
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_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_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_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'
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
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
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_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_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_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'
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_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_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_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_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_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 + 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_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_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'}
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'}
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_64_commitment_edges.yaml', sources) as solution:
solution.objective # 9140.0
The network, rung_64_commitment_edges.py in the corpus — the spine plus what this rung adds:
# SPDX-FileCopyrightText: mathspec Contributors
#
# SPDX-License-Identifier: MIT
"""Rung 64: commitment edges — a committable generator, link and process built in the later period start up when they open, and a committable unit without a build cap is released by an inferred big M."""
from __future__ import annotations
from datetime import datetime
import pandas as pd
OPTIMIZE = {'multi_investment_periods': True}
def build():
"""A whole network, not the spine: eight snapshots over two periods, three committable units built in 2030, an uncapped committable build, and a dear peaker."""
import pypsa
n = pypsa.Network()
n.snapshots = pd.MultiIndex.from_tuples(
[(2020, datetime(2020, 1, 1, t)) for t in range(4)] + [(2030, datetime(2030, 1, 1, t)) for t in range(4)]
)
n.investment_periods = [2020, 2030]
n.investment_period_weightings['objective'] = [1.0, 0.5]
n.investment_period_weightings['years'] = [10.0, 10.0]
n.snapshot_weightings['objective'] = [2.0, 1.5, 2.5, 2.0, 2.0, 1.5, 2.5, 2.0]
n.add('Bus', ['hub', 'fuel'])
n.add('Generator', 'well64', bus='fuel', p_nom=200, marginal_cost=1)
n.add('Generator', 'peak64', bus='hub', p_nom=300, marginal_cost=50)
late = {'committable': True, 'p_nom': 30, 'p_min_pu': 0.25, 'build_year': 2030, 'lifetime': 30}
n.add('Generator', 'late_gen64', bus='hub', marginal_cost=2, start_up_cost=100, **late)
n.add('Link', 'late_link64', bus0='fuel', bus1='hub', marginal_cost=1, start_up_cost=70, **late)
n.add('Process', 'late_proc64', bus0='fuel', bus1='hub', rate0=-1.25, start_up_cost=40, **late)
n.add(
'Generator',
'uncapped64',
bus='hub',
committable=True,
p_nom_extendable=True,
capital_cost=20,
marginal_cost=10,
p_min_pu=0.2,
up_time_before=0,
start_up_cost=30,
)
n.add('Load', 'hub_load64', bus='hub', p_set=[40, 60, 70, 50, 120, 140, 150, 130])
return n
The data¶
Every table this spec declares was first declared by a lower rung; its values here are in the prep above.