StorageDispatch

class popo.scenarios.StorageDispatch(kw_rated=3.0, kwh_rated=10.0, charge_start_hour=10.0, charge_end_hour=17.0, discharge_start_hour=18.0, discharge_end_hour=22.0)

Bases: object

A customer battery and the fixed daily windows it charges and discharges in.

A scheduled dispatch rather than a closed-loop controller, kept simple and legible on purpose: charging through the hours rooftop generation peaks absorbs export at the customer’s own connection, which is the mechanism the lever is meant to test. Discharging into the evening peak empties it again, so it can absorb the next day’s export; a battery that only charges is full after one day and does nothing on the second. Outside both windows it idles.

Variables:

• kw_rated – Charging and discharging power.

• kwh_rated – Energy capacity. Charging stops once it is full and discharging once it is empty, so a capacity smaller than kw_rated times a window limits how much of it the battery uses.

• charge_start_hour – Hour of day, in [0, 24), at which charging begins.

• charge_end_hour – Hour of day at which charging ends.

• discharge_start_hour – Hour of day at which discharging begins, or None for a battery that never discharges.

• discharge_end_hour – Hour of day at which discharging ends.

shape(interval_hours=0.5)

One day of dispatch multipliers: -1 charging, +1 discharging, 0 idle, at rating.

Parameters:

interval_hours (float) – Interval length in hours.

Return type:

ndarray

Returns:

One multiplier per interval of a day; OpenDSS repeats it daily.