Storage operating data not applied consistently
Open
Nobody has claimed this yet.
bug
- Dominant language
- Python
- Stars
- 9
- Forks
- 1
- Avg merge
- 9m
- Merged PRs (30d)
- 9
Description
Some storage assets are used in years before their operating date. It's a little strange since other storage assets do seem to only be used after their operating date.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files or tests are named. Start by tracing how storage assets' operating dates are represented and used in the electricity dispatch model, then compare scheduling behavior for assets before and after that date. Done means no storage asset is used before its operating date while existing valid dispatch behavior remains unchanged.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100