-
Notifications
You must be signed in to change notification settings - Fork 41
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
add bau lcc outputs #550
add bau lcc outputs #550
Conversation
julia_src/Manifest.toml
Outdated
@@ -1,6 +1,6 @@ | |||
# This file is machine-generated - editing it directly is not advised | |||
|
|||
julia_version = "1.8.5" | |||
julia_version = "1.7.1" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should maintain v1.8+ for Julia here, as that is in line with most people's versions as well as the version in the Dockerfile (which sets how it's run in the containers). The easiest way to do that is to just update the envrionment from within the Julia Docker container instead of on your local OS. Let me know if you need help with that.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
addressed in 90d4146
Please check if the PR fulfills these requirements
See Julia equivalent: NREL/REopt.jl#333
What kind of change does this PR introduce?
(Bug fix, feature, docs update, ...)
Added the following BAU outputs: lifecycle_chp_standby_cost_after_tax, lifecycle_elecbill_after_tax, lifecycle_production_incentive_after_tax, lifecycle_outage_cost, lifecycle_MG_upgrade_and_fuel_cost
Does this PR introduce a breaking change?
(What changes might users need to make in their application due to this PR?)
No.
Other information:
Didn't include LCC components that will definitely be 0 for BAU such as technology CAPEX costs