NatLabRockies / NatLabRockies/H2Integrate
When is a system-level controller necessary?
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 26
- Forks
- 44
- Avg merge
- 3d 22h
- Merged PRs (30d)
- 16
Description
As we expand out H2I to include system-level control, when should we require a top-level controller?
When we just have one technology, e.g. a solar plant or tidal turbine, we don't need a system-level controller.
If we have a wind farm and a battery, do we need a system-level controller?
When we have a demand component in the system, do we always need a system-level controller?
How can we better define when we need system-level control, both from a physical modeling perspective and from a code architecture and organization perspective?
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 reviewing how H2I currently represents system-level control and compare the single-technology, wind-farm-plus-battery, and demand-component cases described in the issue. Define decision criteria from both physical modeling and code architecture perspectives, with completion marked by a documented rule for when a top-level controller is required.
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
- 30/100