-
Notifications
You must be signed in to change notification settings - Fork 66
Energy Performance and Reliability Tool #365
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
Conversation
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
This reverts commit 4ae360d.
will revert this commit later
This reverts commit 587fa8a.
…opt.jl branch using" This reverts commit 4a219a3.
This reverts commit bd7f912.
|
@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. |

Please check if the PR fulfills these requirements
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)?
/erpendpoint to which users POST ERP inputs (callsERPJob())/erp/<run_uuid>/resultsendpoint that GETs the results of an ERP job (callserp_results())/erp/helpendpoint that GETs the ERP input field info (callserp_help())/erp/chp_defaultsendpoint that GETs ERP CHP/prime generator input defaults based on parametersprime_mover,is_chp, andsize_kw(callserp_chp_prime_gen_defaults())resilience+stats/tests/test_erp.pyscalar_to_vectorhelper function toscalar_or_monthly_to_8760Does this PR introduce a breaking change?
not to the stable version of the API (v2)
Other information: