PyPSA / PyPSA/technology-data

order_data: inputs for electrical or heat "consumption" are converted to efficiencies or filtered out

Open
#214 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

feature low priority
Dominant language
Python
Stars
130
Forks
59
PR merge metrics
No merged PRs in 30d

Description

Checklist

  • I am using the current master branch or the latest release. Please indicate: YES

ISSUE:

When adding new technologies (e.g. from DEA) which are consuming electricity or heat (i.e. processes for e- fuel production), the electricity and heat consumption is read from the initial excel files but filtred out in the final df, or re-calculated as electrical or heat efficiency

Following the main, if the indexes "electricity consumption" and "heat consumption" are present in the original excel file they are correctly saved in the df "tech_data" but are not included (or strangely modified) in the df "data".

this happens within function "order_data" because all the indexes containing "Electrical" or "Heat" are converted to efficiencies:
https://github.com/PyPSA/technology-data/blob/98fa9218d57638a7156c33dc07749ac3624bd974/scripts/compile_cost_assumptions.py#L2045-L2054

This requires extra code specific for each technology to bypass this issue, which is not sustainable in the long term.
e.g.: https://github.com/PyPSA/technology-data/blob/98fa9218d57638a7156c33dc07749ac3624bd974/scripts/compile_cost_assumptions.py#L2056-L2093

Error Message

there is no error in the code, but the final .csv files have the wrong data

Suggestion

modify this part of the code :
https://github.com/PyPSA/technology-data/blob/98fa9218d57638a7156c33dc07749ac3624bd974/scripts/compile_cost_assumptions.py#L2045-L2054
to don't label electrical and heat consumption as efficiencies.

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

Start in scripts/compile_cost_assumptions.py, in order_data around lines 2045–2054, and compare the original tech_data values with the final data output. Check how indexes containing “Electrical” or “Heat” are classified, then verify that consumption inputs remain unchanged rather than being converted or filtered. Confirm the resulting final CSV files contain the expected consumption data.

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
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.