Battery Module

Batteries are added per area through the create_battery method. You can provide an initial amount of energy stored, i.e. state_of_energy, otherwise it defaults to 0.

See ModuleBattery for an overview of required timeseries and the domain notebook for an example for how to set up a battery.

End value

In order to prevent the LP-solver from simply emptying the battery at the end of the week, we need to set a value on the energy at the end of the decision problem horizion. One can either set this as input (EXOGENOUS) or base it on the dual value of the state_of_energy variable (ENDOGENOUS).

If the end value type is ENDOGENOUS we recommend setting initial_end_value, otherwise the battery might empty by the end of the decision problem horizion. The lower the value, the higher the incentive to keep the energy, since the objective function is minimized.

If the end value is EXOGENOUS the user can supply a NDTimeSeries to set the end value at different points of time.

  • If N is the number of values at a given point, and N=1, then that will act as the value of the state of energy.

  • If N > 1, the end value will be split into N layers, each sized as (max capacity) /  N-1. The value at index i corresponds to layer i.

NOTE: due to backwards compability reasons, and potential future support for minimum requirements, the first layer is discarded, i.e. the value at index 0 is irrelevant if N > 1.