Skip to content
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

Blackbox dispatcher #288

Closed
wants to merge 7 commits into from
Closed

Blackbox dispatcher #288

wants to merge 7 commits into from

Conversation

dhill2522
Copy link
Contributor


Pull Request Description

What issue does this change request address?

#287

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

This adds a new dispatcher to HERON that operates parallel to the existing Pyomo methods. This methods uses a ported version of the Chickadee algorithm now using cyipopt rather than pyoptsparse as an interface to IPOPT.

This dispatcher supports arbitrary transfer functions for HERON components expressed as Python functions in an associated Python script. This allows implementing transfer functions as external simulations, look-up tables, non-linear python methods or a wide variety of other possible cases.


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.

@GabrielSoto-INL
Copy link
Collaborator

Closing this PR, see discussion #320 for details

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