v0.6.0 Release Candidate
#594
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sync develop to master
Demand Response by Sector
Sector Demand Response Hotfix
for more information, see https://pre-commit.ci
Add Clustering weighting_strategy feature
Refactor PRM
Update Sector CO2L and TCT Constraints
Update PUDL path for sector studies
PRM bug fix
* eia fuel cost extraction updated * trn production plots update * furnace efficiency update * central marginal cost stores * dynamic cost scaling * methane tracking always on * correct marginal cost conversions * update lpg vehicle efficiency * ev policy implemented for endogenous investment * plotting color fix
* correct linepack calc * correct commercial water heaters
Adds downstream ch4 tracking and updates associated configuration documentation.
* update dag (#517) Update DAGs for documentation site * added for loop around the solve_network. New myopic and perfect foresight if statements in the solve_network function to pull the foresight type from a config file. Foresight type option still needs to be added to the repo_data/config/ files, as it is just manually added into the workflow/config currently to avoid init_pypsa_usa.sh reuse. With precommit fixes. * fixed errors with pulling the myopic foresight from config file, model running, gives same results as without myopic since we are not pulling from prior timesteps * moved for loop inside of the solve_network, removed the add_myopic constraint * first working version, no bugs, runs fully. needs checks to see if output matches expectations. output does combine first year with the existing infrastructure (need to fix). added in the time dependent components. added a limited part of c in the c.iterate_components, to just include what was in the previous timestep. * fixed the limited c.df to be for build years below the investment horizon, previously was years equal to the investment horizon * made it so that the links are properly removed, since their build year is 0 * first successful version to have results for all decades, needs first level checks but is giving reasonable results for myopic output. Key change was creating a deep copy of the c.pnl and adding all rather than just input time variables back in after removal * fixed the loop to be inclusive for c_lim rather than less than the planning horizon * updated the configtables documentation * Fix clim, other fix for perf foresight. * RPS updates * fixed the retirement issue for one time horizon * updated to m.add to carry over the custom fields * added the storage state_of_charge rollover, but this is leading to infeasible solve, need to fix * changed state of charge to just be the final snapshot, now feasible * updated the config files in repo_data, and the docs to show that myopic is available * n.madd for generators so that the attributes carry over. this is a fix that likely isnt ideal in the long run, but n.add doesn't carry these attributes over * [pre-commit.ci] auto fixes from pre-commit.com hooks for more information, see https://pre-commit.ci --------- Co-authored-by: Trevor Barnes <[email protected]> Co-authored-by: ktehranchi <[email protected]> Co-authored-by: Jones <[email protected]> Co-authored-by: Kamran Tehranchi <[email protected]> Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
Add lifetimes and build rates for sector technologies
* update dag (#517) Update DAGs for documentation site * [pre-commit.ci] pre-commit autoupdate updates: - [github.com/pycqa/isort: 5.13.2 → 6.0.0](PyCQA/isort@5.13.2...6.0.0) - [github.com/asottile/pyupgrade: v3.19.0 → v3.19.1](asottile/pyupgrade@v3.19.0...v3.19.1) - [github.com/psf/black-pre-commit-mirror: 24.10.0 → 25.1.0](psf/black-pre-commit-mirror@24.10.0...25.1.0) * new linting * [pre-commit.ci] pre-commit autoupdate updates: - [github.com/astral-sh/ruff-pre-commit: v0.1.4 → v0.9.9](astral-sh/ruff-pre-commit@v0.1.4...v0.9.9) * [pre-commit.ci] auto fixes from pre-commit.com hooks for more information, see https://pre-commit.ci * [pre-commit.ci] pre-commit autoupdate updates: - [github.com/astral-sh/ruff-pre-commit: v0.9.9 → v0.9.10](astral-sh/ruff-pre-commit@v0.9.9...v0.9.10) * [pre-commit.ci] pre-commit autoupdate updates: - [github.com/astral-sh/ruff-pre-commit: v0.9.10 → v0.11.0](astral-sh/ruff-pre-commit@v0.9.10...v0.11.0) * [pre-commit.ci] pre-commit autoupdate (#579) updates: - [github.com/snakemake/snakefmt: v0.10.2 → v0.11.0](snakemake/snakefmt@v0.10.2...v0.11.0) - [github.com/astral-sh/ruff-pre-commit: v0.11.0 → v0.11.5](astral-sh/ruff-pre-commit@v0.11.0...v0.11.5) Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com> * [pre-commit.ci] auto fixes from pre-commit.com hooks for more information, see https://pre-commit.ci * correct notebooks for precommit --------- Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com> Co-authored-by: Kamran Tehranchi <[email protected]> Co-authored-by: ktehranchi <[email protected]>
|
Should we pull the trigger on this ? @trevorb1 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changes proposed in this Pull Request
v0.6.0release candidate