Skip to content

Conversation

@dylanjm
Copy link
Collaborator

@dylanjm dylanjm commented Sep 30, 2024


Pull Request Description

What issue does this change request address?

#386

What are the significant changes in functionality due to this change request?

Ideally, no changes in functionality but everything will be different.


For Change Control Board: Change Request Review

The following review must be completed by an authorized member of the Change Control Board.

  • 1. Review all computer code.
  • 2. If any changes occur to the input syntax, there must be an accompanying change to the user manual and xsd schema. If the input syntax change deprecates existing input files, a conversion script needs to be added (see Conversion Scripts).
  • 3. Make sure the Python code and commenting standards are respected (camelBack, etc.) - See on the wiki for details.
  • 4. Automated Tests should pass.
  • 5. If significant functionality is added, there must be tests added to check this. Tests should cover all possible options. Multiple short tests are preferred over one large tes.
  • 6. If the change modifies or adds a requirement or a requirement based test case, the Change Control Board's Chair or designee also needs to approve the change. The requirements and the requirements test shall be in sync.
  • 7. The merge request must reference an issue. If the issue is closed, the issue close checklist shall be done.
  • 8. If an analytic test is changed/added, the the analytic documentation must be updated/added.
  • 9. If any test used as a basis for documentation examples have been changed, the associated documentation must be reviewed and assured the text matches the example.

@dylanjm dylanjm marked this pull request as draft September 30, 2024 21:22
@dylanjm dylanjm force-pushed the dove-modifications branch 2 times, most recently from 531c675 to 84bc649 Compare October 2, 2024 20:57
@dylanjm dylanjm force-pushed the dove-modifications branch from 8e89003 to 860876c Compare October 15, 2024 23:12
@dylanjm dylanjm force-pushed the dove-modifications branch from 1552aaa to 731c206 Compare December 9, 2024 18:05
@dylanjm dylanjm force-pushed the dove-modifications branch from 731c206 to bb1707c Compare January 17, 2025 21:23
@dylanjm dylanjm changed the title [WIP] Dove modifications Dove modifications Mar 1, 2025
@dylanjm dylanjm marked this pull request as ready for review March 1, 2025 00:15
Copy link
Collaborator

@PaulTalbot-INL PaulTalbot-INL left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Initial surface review, very few comments. I did not comment on many commented lines that might be removed; I'll save that for a future review.

## All InputSpecs for Interactions are defined within the DOVE.src.Interactions.
## If a new VP node needs to be added, find someway to add a fixed-value version
## to DOVE first! Then modify it in here. This will keep feature parity with DOVE.
## YOU HAVE BEEN WARNED!
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

bravo

sub.addSub(new_sub)

# We have to iterate a level deeper to get to CashFlow nodes
for sub in input_specs.subs:
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

can this be merged with the loop above by keeping the econ "if" as the first if? Probably not necessary or even very impactful but may save a little computational effort

# when recreating the ValuedParam version of <reference_price>. Otherwise it gets deleted and is no
# longer seen as an available input option. We should find a way to dynamically add child subs by perhaps
# adding a key to `econ_subs_to_modify` dictionary like "add_subs". For now we add a conditional checking
# if we are modifying <reference_price> and then directly add <levelized_cost> to the new input definition.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

10 laps for you. I agree, we need a cleaner way to do this at some point.

@ Out, None
"""
Interaction.__init__(self, **kwargs)
HeronInteraction.__init__(self, **kwargs)
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

do we not need __init__ from DoveProducer here as well?

@dylanjm dylanjm force-pushed the dove-modifications branch 2 times, most recently from 6403be3 to 691cca3 Compare April 27, 2025 23:57
@dylanjm dylanjm force-pushed the dove-modifications branch from 691cca3 to 08b3b4d Compare April 28, 2025 23:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants