Skip to content
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

Allow the selection of custom fork of technology-data #970

Merged
merged 2 commits into from
Mar 19, 2024

Conversation

koen-vg
Copy link
Contributor

@koen-vg koen-vg commented Mar 18, 2024

Sometime like this seems to be necessary in order to use pypsa-eur with technology-data using a different configuration than default; for instance, using 2023 euros instead of 2020 euros ;)

Feel free to suggest alternative ways of doing this if my proposed solution seems a bit ad-hoc.

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.
  • A release note doc/release_notes.rst is added.

@fneum fneum disabled auto-merge March 19, 2024 07:27
@fneum fneum merged commit 3940d2e into PyPSA:master Mar 19, 2024
5 of 6 checks passed
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.

2 participants