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

Update default year for IRENA RES scaling #1106

Merged
merged 2 commits into from
Sep 27, 2024

Conversation

cpschau
Copy link
Contributor

@cpschau cpschau commented Sep 20, 2024

Changes proposed in this Pull Request

This PR updates the default year for RES capacity estimation based on the latest IRENA data (electricity:estimate_renewable_capacities:year), that happens in add_electricity.py. Additionally, the configuration table and the corresponding comment in config.default.yaml have been adjusted accordingly.

The IRENA data used in powerplantmatching now includes information up to 2023 (https://github.com/PyPSA/powerplantmatching/blob/9a63ed0363e748a6967673c00cb2a6dd7d6c80c4/powerplantmatching/package_data/config.yaml#L64). For the case of Brazil this update entails significant changes in capacity (onshore wind: 17.2 GW -> 29.1 GW; solar: 8.4 GW -> 37.4 GW).

Checklist

  • I consent to the release of this PR's code under the AGPLv3 license and non-code contributions under CC0-1.0 and CC-BY-4.0.
  • I tested my contribution locally and it seems to work fine.
  • Code and workflow changes are sufficiently documented.
  • Newly introduced dependencies are added to envs/environment.yaml and doc/requirements.txt.
  • Changes in configuration options are added in all of config.default.yaml and config.tutorial.yaml.
  • Changes in configuration options are also documented in doc/configtables/*.csv and line references are adjusted in doc/configuration.rst and doc/tutorial.rst.
  • A note for the release notes doc/release_notes.rst is amended in the format of previous release notes, including reference to the requested PR.

@davide-f
Copy link
Member

Great @cpschau :D
Many thanks for the contribution! This is neat and ready-to-be-merged.
Does this PR requires the new powerplantmatching version to have the updated IRENA data?

@cpschau
Copy link
Contributor Author

cpschau commented Sep 26, 2024

Great @cpschau :D Many thanks for the contribution! This is neat and ready-to-be-merged. Does this PR requires the new powerplantmatching version to have the updated IRENA data?

Hey @davide-f ,

the IRENA update was introduced in the PPM release v0.5.13, so not so new anymore 😃

@davide-f
Copy link
Member

Great @cpschau :D Many thanks for the contribution! This is neat and ready-to-be-merged. Does this PR requires the new powerplantmatching version to have the updated IRENA data?

Hey @davide-f ,

the IRENA update was introduced in the PPM release v0.5.13, so not so new anymore 😃

This looks good to me!
We have a problem with powerplantmatching because the Global Energy Monitoring has changed permission access to the data.
This problem is solved with the new powerplantmatching version.
Would you mind to add such constraint? powerplantmatching>=0.6?

@cpschau
Copy link
Contributor Author

cpschau commented Sep 26, 2024

Great @cpschau :D Many thanks for the contribution! This is neat and ready-to-be-merged. Does this PR requires the new powerplantmatching version to have the updated IRENA data?

Hey @davide-f ,
the IRENA update was introduced in the PPM release v0.5.13, so not so new anymore 😃

This looks good to me! We have a problem with powerplantmatching because the Global Energy Monitoring has changed permission access to the data. This problem is solved with the new powerplantmatching version. Would you mind to add such constraint? powerplantmatching>=0.6?

Done!

@davide-f
Copy link
Member

As CI successds, this is merged :D

@davide-f
Copy link
Member

@FabianHofmann currently the CIs are experiencing issues with the installation of micromamba.
This applies here and also #1113 but with different reasons.
Is there a reason why using micromamba instead of conda given the issues?
mamba was performing better in resolving the envs, but conda seemed to have moved to mamba libs for that.
Shall we revise and/or open an issue?

@davide-f
Copy link
Member

Note, this is a reported issue with the latest micromamba update:
mamba-org/micromamba-releases#58

FYI @finozzifa

@davide-f
Copy link
Member

@cpschau FYI I removed the constraint on powerplantmatching to let the CI run, ready to merge as it completes :)

@davide-f davide-f merged commit ea99d74 into pypsa-meets-earth:main Sep 27, 2024
4 of 6 checks passed
davide-f added a commit to davide-f/pypsa-earth that referenced this pull request Oct 20, 2024
…caling

Update default year for IRENA RES scaling
davide-f added a commit to davide-f/pypsa-earth that referenced this pull request Oct 20, 2024
…caling

Update default year for IRENA RES scaling
davide-f added a commit to davide-f/pypsa-earth that referenced this pull request Oct 20, 2024
…caling

Update default year for IRENA RES scaling
nilgpe pushed a commit to nilgpe/pypsa-earth that referenced this pull request Oct 20, 2024
…caling

Update default year for IRENA RES scaling
davide-f added a commit to davide-f/pypsa-earth that referenced this pull request Oct 20, 2024
…caling

Update default year for IRENA RES scaling
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