NatLabRockies / NatLabRockies/H2Integrate
Defining terms for system and technology control
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 26
- Forks
- 44
- Avg merge
- 3d 22h
- Merged PRs (30d)
- 16
Description
As we work towards adding system-level control capabilities to H2I (see #542), it is important that we determine clear naming conventions. After a discussion with @genevievestarke, @johnjasa, @kbrunik, and @elenya-grant, we came up with the following diagram to represent our current ideas for naming conventions in H2I.
Note: Before all the appropriate infrastructure is set up, if there is not a tech control or system control model specified, then commodity demand may need to be directly connected to set point and tech performance may accept set point rather than command.
Consider this issue as the place to discuss naming conventions related to system-level control in H2I.
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 with issue #542 and review the attached naming-convention diagram, then read the discussion in this issue. The work is complete when the project agrees on clear terminology for system-level control and records those conventions in the relevant design or project documentation.
Written by the indexing model from the issue text.
Assessment
- Domain
- backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100