PyPSA / PyPSA/powerplantmatching

error using combine_multiple_datasets with powerplantmatching.data.GEM()

Open
#237 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

needs triage
Dominant language
Python
Stars
227
Forks
74
Avg merge
6d 17h
Merged PRs (30d)
4

Description

Version Checks (indicate both or one)
  • I have confirmed this bug exists on the lastest release of powerplantmatching.

  • I have confirmed this bug exists on the current master branch of powerplantmatching.

Issue Description

Hi, I’m following a minimal example from the readthedocs but run into an error with the combine_multiple_datasets function that’s traced back to duke.py

Any clues as to why ‘pm.data.GEM()’ may be running into this issue? Thanks!

Reproducible Example
import powerplantmatching as pm
entsoe_ppm = pm.data.ENTSOE()
gem = pm.data.GEM()
dfs = [gem.powerplant.aggregate_units(), entsoe.powerplant.aggregate_units()]
intersection = pm.matching.combine_multiple_datasets(dfs)
Expected Behavior

#error in duke.py
#logger.debug("Comparing files: %s", ", ".join(labels))
#TypeError: sequence item 0: expected str instance, NoneType found

I only get this error in using ‘pm.data.GEM()’. Any other source that I attempt to match with ENSTOe works (JRC, GCPT, GEO, etc)

Installed Versions
Replace this line.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Run the minimal example with the documented powerplantmatching release or master version, then inspect combine_multiple_datasets and the referenced duke.py location where the labels are joined. Compare the GEM and ENTSOE inputs and capture the complete traceback and installed versions; done means GEM can be combined with ENTSOE without the TypeError and the regression is covered by a test.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
data-engineering
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.