-
Notifications
You must be signed in to change notification settings - Fork 27
Removed hard-coded logic for electrolyzer replacement schedule #555
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
elenya-grant
wants to merge
9
commits into
NatLabRockies:develop
Choose a base branch
from
elenya-grant:all_tech_refurb
base: develop
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
9 commits
Select commit
Hold shift + click to select a range
36d7e8f
draft
elenya-grant ade3810
updated finances to take in replacement schedules for all techs
elenya-grant caa4131
updated feedstock and added logic to prevent connecting replacement s…
elenya-grant 26a9ddc
merged in develop
elenya-grant 08a7889
added doc page about naming convention
elenya-grant ed8f9bd
removed unnecessary elif statement in connect_technologies
elenya-grant 9be6844
added test for new error message
elenya-grant 6cc09d1
updated inline comments for finance models
elenya-grant 7889135
Merge branch 'develop' into all_tech_refurb
johnjasa File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,35 @@ | ||
| # Expected Technology Naming Convention in H2I | ||
|
|
||
| Some logic within H2I is relies on some expected naming convention of technologies in the technology configuration file. The following details the naming convention required for H2I to run properly. | ||
|
|
||
| ```yaml | ||
| technologies: | ||
| tech_name_A: #these are the keys with specific required naming convention | ||
| performance_model: | ||
| model: | ||
| cost_model: | ||
| model: | ||
| model_inputs: | ||
| performance_parameters: | ||
| ``` | ||
|
|
||
| - if using the `GenericCombinerPerformanceModel` as the technology performance model, the technology name must include the name `combiner`. Some examples of valid technology names are: | ||
| + 'combiner' | ||
| + 'combiner_1' | ||
| + 'electricity_combiner' | ||
| + 'hydrogen_combiner_2' | ||
| - if using the `GenericSplitterPerformanceModel` as the technology performance model, the technology name must include the name `splitter`. Some examples of valid technology names are: | ||
| + 'splitter' | ||
| + 'splitter_1' | ||
| + 'electricity_splitter' | ||
| + 'hydrogen_splitter_2' | ||
| - if using the `FeedstockPerformanceModel` as the technology performance model and the `FeedstockCostModel` as the technology cost model, the technology name must include the name `feedstock`. Some examples of valid technology names are: | ||
| + 'feedstock' | ||
| + 'water_feedstock' | ||
| + 'feedstock_iron_ore' | ||
| + 'natural_gas_feedstock_tank' | ||
| - If a transport component is defined in the technology configuration file (most likely to transport commodities that cannot be transported by 'pipe' or 'cable'), the technology name must include the name `transport`. Some examples of valid technology names are: | ||
| + 'transport' | ||
| + 'lime_transport' | ||
| + 'transport_iron_ore' | ||
| + 'reformer_catalyst_transport_tube' |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.