Skip to content

Deprecate extend_by_vres - #327

Open
fneum wants to merge 1 commit into
masterfrom
deprecate-extend-by-vres
Open

fneum wants to merge 1 commit into
masterfrom
deprecate-extend-by-vres

Conversation

@fneum

@fneum fneum commented Oct 7, 2026 •

Copy link
Copy Markdown
Member

Closes #232.

Why

Wind and solar power plants are already in the default output: GEM is fully included, and MASTR covers Germany. pm.powerplants(extend_by_vres=True) added them again from outdated OPSD data (2020) and counted them twice. As agreed in #232, the option goes; wind and solar stay included.

Changes

  • pm.powerplants(extend_by_vres=True) emits a FutureWarning.
  • extend_by_VRE() (and df.powerplant.extend_by_VRE()) is marked with @deprecated(deprecated_in="0.10.0", removed_in="0.11.0").
  • The old behaviour stays for one release, so results do not change without notice.
  • Bugfix: from_url=True silently ignored extend_by_vres; it now applies it like the other code paths.
  • Bugfix: the deprecated extendby_kwargs called logger.warning(DeprecationWarning, ...), which failed inside logging. It now emits a FutureWarning.

Wind and solar power plants are already included from GEM and MASTR.
The option added them again from outdated OPSD data and counted them
twice. Closes #232.

Also apply extend_by_vres with from_url=True and emit a proper
FutureWarning for the deprecated extendby_kwargs.

This branch has not been deployed

No deployments
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.

Rerunning with extend_by_vres results extreme overcapacity

1 participant