NatLabRockies / NatLabRockies/H2Integrate
SLC: allow priority order to be a user-set input
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 26
- Forks
- 44
- Avg merge
- 3d 22h
- Merged PRs (30d)
- 16
Description
SLC: allow priority order to be a user-set input
Currently in the system-level control, the order that technologies fulfill demand is fixed.
Proposed solution
We could allow an input in the system_level_control section of the plant_config that allows users to set the order of technologies that are called to meet a given demand.
This is currently done in https://github.com/NatLabRockies/hercules so we could draw from that logic there or discuss with @genevievestarke the best path forward based on lessons learned already.
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 locating the system_level_control and plant_config handling in H2Integrate. Compare the relevant priority-order logic in Hercules and discuss the intended behavior with the referenced project contact. Done means users can configure the technology order and the system-level control follows that order when meeting demand.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100