Skip to content

Update PyPSA dependency >= V1 - #762

Open
apigott wants to merge 20 commits into
developfrom
update/pypsa-v1
Open

Update PyPSA dependency >= V1#762
apigott wants to merge 20 commits into
developfrom
update/pypsa-v1

Conversation

@apigott

@apigott apigott commented Jun 11, 2026

Copy link
Copy Markdown
Collaborator

Closes #701

Changes proposed in this Pull Request

Updates PyPSA-USA to track changes made in PyPSA V1

Checklist

  • I tested my contribution locally and it seems to work fine.
  • Code and workflow changes are sufficiently documented.
  • Changed dependencies are added to envs/environment.yaml.
  • Changes in configuration options are added in all of config.default.yaml.
  • Changes in configuration options are also documented in doc/configtables/*.csv.

@apigott
apigott requested a review from martacki June 12, 2026 02:39
@apigott
apigott marked this pull request as ready for review June 19, 2026 03:50
@apigott

apigott commented Jun 19, 2026

Copy link
Copy Markdown
Collaborator Author

The biggest concern I have is around changing the unit commitment implementation. The default attr isn't available as part of pypsa v1 so I borrowed the implementation mostly from the pypsa-eur implementation. Open to discussion about the change of method and addition of data/unit_commitment.csv though.

@apigott
apigott requested a review from ktehranchi June 19, 2026 03:52

@ktehranchi ktehranchi left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A few things:

In PyPSA-USA we always merge new developments to the develop branch first before moving to master. We make releases from develop -> master when there are large feature bumps. So i would change this to merge into develop.

RE: Unit-committment. I'm fine to move toward the data-source and method used in pypsa-eur for UC... we currently take it from the public version of the wecc ads, matched on the unit, then fill missing data with the averages of the WECC dataset... but would be fine to use a flat csv to fill any missing data... But i think this can be a different PR.

@apigott
apigott changed the base branch from master to develop July 6, 2026 17:09
@apigott

apigott commented Jul 6, 2026

Copy link
Copy Markdown
Collaborator Author

Target branch has been changed. Can you clarify the preference for how to do the UC in a different PR? .default is not a PyPSA attribute in V1 so it requires at least a temporary change in this PR or another PR pulled into this one

@trevorb1

trevorb1 commented Jul 7, 2026

Copy link
Copy Markdown
Collaborator

Thanks for the work on this, @apigott! Quick question, have you run the sector network with this, or just the electrical network? If you haven't actually run the sector network, I can run it over the next couple of days to make sure nothing broke with sector studies.

@apigott

apigott commented Jul 10, 2026

Copy link
Copy Markdown
Collaborator Author

@trevorb1 I haven't had a chance to test the sectoral coupling

@trevorb1

trevorb1 commented Aug 6, 2026

Copy link
Copy Markdown
Collaborator

@apigott Sorry, this PR slipped my mind! Il try to do a test of it this weekend!

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.

Upgrade PyPSA to v1.0.0

3 participants