SLC: allow priority order to be a user-set input

Open
  • Is something wrong?
#775 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
python
Domain
backend

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.

Description

dispatch enhancement

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.

Dominant language
Python
Stars
30
Forks
44
Avg merge
3d 12h
Merged PRs (30d)
28

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from NatLabRockies/H2Integrate

All issues in NatLabRockies/H2Integrate

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.