NatLabRockies / NatLabRockies/H2Integrate

Feature request: Tool to make skeleton of `model_inputs` for tech config

Open
#852 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
26
Forks
44
Avg merge
3d 22h
Merged PRs (30d)
16

Description

Feature request: Tool to make skeleton of model_inputs for tech config

This partially came up in PR #849 and in a discussion with @genevievestarke . It'd be nice to leverage some of the functionality available in check_inputs (h2integrate/core/dict_utils.py) to be able to get a draft of the model_inputs for each technology. The method would be input a tech config file containing the models to use per technology, then it would output the tech config with the model_inputs section organized as-needed.

This would be helpful especially with storage models. It takes a reasonable bit of time to update the model_inputs for a storage model if you just want to change the performance or control model - things have to be shuffled to/from control_parameters, performance_parameters, and shared_parameters when a model is changed.

Proposed solution

Alternatives considered

Additional context

Contributor guide

Open the contributing guide

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.

Research direction

Start by reading h2integrate/core/dict_utils.py and the existing check_inputs functionality, then review PR #849 for context. Define how a tech config containing models should be transformed and what the generated, organized model_inputs section must contain, especially when storage models change performance or control models.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
tooling
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.