NatLabRockies / NatLabRockies/H2Integrate
Enable multiple converter technologies in dispatch optimization
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 26
- Forks
- 44
- Avg merge
- 3d 22h
- Merged PRs (30d)
- 16
Description
Enable multiple converter technologies in dispatch optimization
Currently, the dispatch framework only allows one converter technology and one storage technology. Multiple converter technologies can be summed with a combiner to be directed to the dispatch, but they cannot be dispatched independently. This would require adding some costs from the converter models to the dispatch model through input/output connections, perhaps, so that costs for each converter can be defined independently.
Proposed solution
Alternatives considered
Additional context
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
Start by tracing the dispatch framework's handling of converter and storage technologies, including the combiner and input/output connections described in the issue. Define how independently dispatched converters should expose their costs and verify that multiple converter technologies can be dispatched separately with independently defined costs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100