Penalties and deficit cost
Penalties are costs on slack variables that enter each stage's objective function. They keep the problem always feasible, even in extreme scenarios, and signal how severe each violation is. The deficit, the cost of unserved load, is the best-known penalty.
Why it matters
Seção intitulada “Why it matters”Droughts and equipment failures can make some constraints impossible to meet. Slacks with graded costs keep the problem feasible while signalling how severe the violations are. This is what gives SDDP its relatively complete recourse: every subproblem is feasible, whatever the scenario.
Recourse slacks guarantee feasibility (deficit, excess, inflow non-negativity). Constraint-violation penalties shape the policy. Regularization costs steer the solution where the problem would otherwise be indifferent; they are not real costs and must be orders of magnitude smaller than any economic cost.
Costs follow a priority order in which the deficit outranks the operational constraint slacks. The model checks the configured values when the case loads and emits a warning, without stopping the run, when the order is not respected. That check compares the values as given, so a case can pass it and still invert the energy-equivalent ordering. Two rules reject the case outright: a negative turbining cost on a hydro plant that uses FPHA, and a filling schedule that cannot reach the dead volume (see the ordering validation, under Go deeper).
The priority ladder
Seção intitulada “The priority ladder”The deficit, charged by depth segments with rising costs, is detailed on the Deficit page. Above it sits the violation of the minimum storage of a plant being filled: keeping the reservoir above its dead volume is more critical than serving the load, because operating below it endangers the dam. The filling target sits on a separate rung, below the deficit. Its position relative to the operational constraints is left to the study’s calibration.
The costs have different units ($/MWh, $/hm³, $/(m³/s·h)). The ordering is expressed in energy-equivalent costs, in $/MWh. The load-time check compares the values as given, without that conversion, so a case can pass it and still invert the energy-equivalent ordering.
What the model decides
Seção intitulada “What the model decides”- Load deficit, by segment MW
- Violation of each flexible constraint, when it occurs unit of each constraint
Each violation is charged at the cost of its penalty. The per-stage cost breakdown reports most components in a column of their own, such as deficit, excess, spillage and flow violations. The minimum-storage and filling-target violations of a plant in its filling phase are the exception: their columns always read zero, and their costs count only in the immediate cost.
What you provide
Seção intitulada “What you provide”- The global default for each cost, in
penalties.json, with four required sections: buses, lines, hydro plants and non-controllable sources. Required costs must be positive, except the turbining cost and the curtailment cost, which may be zero. - Optionally, sparse per-stage overrides, in separate files for buses, lines, hydro plants and non-controllable sources. Rows exist only for the entity-stage pairs where the value differs from the default.
- The deficit segments: in each bus’s registry or, when the bus declares none, in the case default.
How each cost value is resolved
Seção intitulada “How each cost value is resolved”The cascade has three levels of specificity. The per-stage override, defined for an entity at a stage, is the most specific. The per-entity override comes next, and the case-wide global default is the last resort. The most specific value present wins.