NatLabRockies / NatLabRockies/H2Integrate
Defining system-level control objectives
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 26
- Forks
- 44
- Avg merge
- 3d 22h
- Merged PRs (30d)
- 16
Description
We need to define our generalized objectives for system-level control.
Here are some that we could consider; which ones are needed for projects in the next year?
Which ones am I missing? Do you prefer different names?
| Objective | What It Optimizes |
|---|---|
minimize_unmet_demand |
minimize $\sum_t \sum_{\text{streams}} \text{unmet}(t)$ |
minimize_cost |
minimize $\sum_t \sum_{\text{prod}} \text{marginal cost}(t) \cdot \text{dispatch}(t) + \lambda \cdot \text{unmet}(t)$ |
maximize_profit |
maximize $\sum_t [\text{revenue}(t) - \text{cost}(t)] - \lambda \cdot \text{unmet}(t)$ |
maximize_production |
maximize $\sum_t \text{production}(t)$ for a specified commodity |
minimize_curtailment |
minimize $\sum_t \sum_{\text{curtailable}} \text{curtailment}(t)$ |
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, tests, or entry points are identified in the issue. Start by reviewing the existing control-objective implementation and the projects planned for the next year; the work is complete when the required objectives, names, and optimization definitions are agreed and documented.
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
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100