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:
- Run attached SAM file with a large year over year rate escalation: rate_escalation_test.zip
- View battery dispatch at year 1 to year 2 transition
- 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.
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:
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.