Skip to content

Price signals dispatch misses rate escalation in forecasts near end of year transition #850

@brtietz

Description

@brtietz

Describe the bug
A function within price signals dispatch always uses the start year, whereas if the forecast day crosses the year it should be using year + 1: https://github.com/NREL/ssc/blob/1556fb6e8669ad28ac9eb2172cdfc3867552442a/shared/lib_battery_dispatch_automatic_btm.cpp#L419

To Reproduce
Steps to reproduce the behavior:

  1. Run attached SAM file with a large year over year rate escalation: rate_escalation_test.zip
  2. View battery dispatch at year 1 to year 2 transition
  3. Difference in price justifies charging on Dec 31 and discharging on Jan 1, but battery does not do that

Expected behavior
Appropriate year should be used when computing costs.

Additional context
Fix will be on branch cmod_utilityrateforecast, and merged in with the rest of that code.

Metadata

Metadata

Assignees

Type

No type
No fields configured for issues without a type.

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions