Rename demand in converters#691
Merged
johnjasa merged 7 commits intoNatLabRockies:developfrom Apr 27, 2026
Merged
Conversation
elenya-grant
approved these changes
Apr 22, 2026
Collaborator
elenya-grant
left a comment
There was a problem hiding this comment.
Thanks for making these changes! I think this helps be more consistent with the storage performance models and controllers - thank you!
kbrunik
approved these changes
Apr 23, 2026
Collaborator
Author
|
Chatting with Elenya about this now, we could tentatively support a passthrough component that converts the demand into set_points, which opens the door for more complex control schemes. Elenya would want this to be in the |
… into rename_demand
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Rename converter
_demandinputs to_set_pointRenames the
{commodity}_demandinput on all converter performance components to{commodity}_set_point, aligning converter naming with the storage baseclass convention.Converters updated:
GridPerformanceModelelectricity_demandelectricity_set_pointNaturalGasPerformanceModelelectricity_demandelectricity_set_pointQuinnNuclearPerformanceModelelectricity_demandelectricity_set_pointSteamMethaneReformerPerformanceModelhydrogen_demandhydrogen_set_pointIronReductionPlantBasePerformanceComponentsponge_iron_demandsponge_iron_set_pointElectricArcFurnacePlantBasePerformanceComponentsteel_demandsteel_set_pointMartinIronMinePerformanceComponentiron_ore_demandiron_ore_set_pointSection 1: Type of Contribution
Section 2: Draft PR Checklist
TODO:
_demandinputs to_set_pointin all converter performance componentsType of Reviewer Feedback Requested (on Draft PR)
Structural feedback: Is the
_set_pointnaming convention the right choice, or should a different term be used?Other feedback: N/A
Section 3: General PR Checklist
docs/files are up-to-date, or added when necessaryCHANGELOG.md"A complete thought. [PR XYZ]((https://github.com/NatLabRockies/H2Integrate/pull/XYZ)", where
XYZshould be replaced with the actual number.Section 4: Related Issues
N/A
Section 5: Impacted Areas of the Software
Section 5.1: New Files
N/A
Section 5.2: Modified Files
See Files Changed
Section 6: Additional Supporting Information
This is a breaking change for any user code that references the old
_demandinput names on converter components (e.g.,prob.set_val("grid.electricity_demand", ...)). Users will need to update these references to_set_point.Section 7: Test Results, if applicable
All converter unit and regression tests pass (77 tests across grid, nuclear, natural gas, iron mine, iron DRI, steel EAF, and SMR test suites).