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

Energy Resilience Performance tool, IRA defaults updates, CHP defaults, other minor #438

Merged
merged 473 commits into from
Mar 17, 2023

Conversation

Bill-Becker
Copy link
Collaborator

@Bill-Becker Bill-Becker commented Mar 14, 2023

See PRs:

Please check if the PR fulfills these requirements

  • CHANGELOG.md is updated
  • Tests for the changes have been added (for bug fixes / features)
  • Docs have been added / updated (for bug fixes / features)

What kind of change does this PR introduce?

(Bug fix, feature, docs update, ...)
See PR list and descriptions in those PRs.

What is the current behavior?

(You can also link to an open issue here)

What is the new behavior (if this is a feature change)?

Does this PR introduce a breaking change?

(What changes might users need to make in their application due to this PR?)

Other information:

… can be included without inputs coming from reopt run uuid
…uts_cumulative_survival_final_time_step_and.py
@Bill-Becker Bill-Becker marked this pull request as ready for review March 16, 2023 16:42
@Bill-Becker Bill-Becker changed the title Energy Resilience Performance tool, IRA defaults updates, other minor Energy Resilience Performance tool, IRA defaults updates, CHP defaults, other minor Mar 17, 2023
@Bill-Becker
Copy link
Collaborator Author

See PRs:

Please check if the PR fulfills these requirements

  • CHANGELOG.md is updated
  • Tests for the changes have been added (for bug fixes / features)
  • Docs have been added / updated (for bug fixes / features)

What kind of change does this PR introduce?

(Bug fix, feature, docs update, ...)

What is the current behavior?

(You can also link to an open issue here)

What is the new behavior (if this is a feature change)?

Does this PR introduce a breaking change?

(What changes might users need to make in their application due to this PR?)

Other information:

@Bill-Becker Bill-Becker merged commit 8a3fc70 into master Mar 17, 2023
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.

None yet

6 participants