Skip to content

Conversation

@hdunham
Copy link
Collaborator

@hdunham hdunham commented Sep 22, 2022

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?

feature

What is the current behavior?

No ERP tool

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

  • Energy Resilience and Performance Tool:
    • Uses functionality added to the REopt Julia package in v0.27.0 to calculate outage survival reliability metrics for a DER scenario, which can be based on the results of a REopt optimization
    • Django models ERPMeta, ERPGeneratorInputs, ERPPrimeGeneratorInputs, ERPElectricStorageInputs, ERPPVInputs, ERPOutageInputs, ERPOutputs
    • /erp endpoint to which users POST ERP inputs (calls ERPJob())
    • /erp/<run_uuid>/results endpoint that GETs the results of an ERP job (calls erp_results())
    • /erp/help endpoint that GETs the ERP input field info (calls erp_help())
    • /erp/chp_defaults endpoint that GETs ERP CHP/prime generator input defaults based on parameters prime_mover, is_chp, and size_kw (calls erp_chp_prime_gen_defaults())
    • Tests in resilience+stats/tests/test_erp.py
  • Added field production_factor_series to Django models WindOutputs and PVOutputs
  • Changed scalar_to_vector helper function to scalar_or_monthly_to_8760
  • Changed GeneratorInputs fields fuel_slope_gal_per_kwh and fuel_intercept_gal_per_hr to electric_efficiency_full_load and electric_efficiency_half_load to represent the same fuel burn curve in a different way consistent with CHPInputs

Does this PR introduce a breaking change?

not to the stable version of the API (v2)

Other information:

@hdunham hdunham requested a review from Bill-Becker September 22, 2022 05:13
hdunham and others added 29 commits September 22, 2022 01:21
setting max to other field was giving error
This was causing a db error if there was an error or null result for
mean_cumulative_outage_survival_final_time_step
@Bill-Becker
Copy link
Collaborator

@hdunham I've made all the changes to the deployment resource stuff. I also merged master into develop, after I merged master into this erp branch. For some reason the file comparison is still showing some "changes" being requested in this develop <- erp PR even though the develop branch already has those changes. I checked the "merge conflicts" that was causing the issue in the REopt.jl PR, but this one doesn't show any conflicts.
image
This does not reflect the state of develop since I merged master into develop.

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