The utility rate forecast class only calls init_energy_rates once, when the load forecast isn't complete yet. This class requires dc_flat_peak to be filled out in order to establish tiers for kWh/kW rates. The battery dispatch code needs to calculate peaks (they were unused in 2020.11.29) in order to properly estimate tiers for these rates. Steps to fix:
- Restore peak calculation to dispatch_automatic_behind_the_meter_t::setup_rate_forecast
- Add peak vector as argument to UtilityRateForecast again
- Add a function to UtilityRateForecast that calls rate.init_energy_rates
- Call this during the setup function in the dispatch class
- Additional calls might be required yearly to properly handle demand escalation
This is a pretty niche issue (one dispatch option with unusual rates), so I'm not tagging this for a specific patch or release just yet.
The utility rate forecast class only calls init_energy_rates once, when the load forecast isn't complete yet. This class requires dc_flat_peak to be filled out in order to establish tiers for kWh/kW rates. The battery dispatch code needs to calculate peaks (they were unused in 2020.11.29) in order to properly estimate tiers for these rates. Steps to fix:
This is a pretty niche issue (one dispatch option with unusual rates), so I'm not tagging this for a specific patch or release just yet.