PyPSA / PyPSA/technology-data

Interpolating data for higher-resolution pathway studies

Open
#282 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Issue first opened as a PR in PyPSA-Eur's PR #1986, now rightfully closed. For congruence, I'll copy-paste here the PR as was, with the caveat that the proposed were a work-around for PyPSA-Eur, not technology-data.

I've been toying around with the possibility of running year-by-year miopic optimisation. Shortly, I found that the only two extant obstacles were:

  • Missing yearly biomass potentials
  • Missing yearly technology costs

Thus, I've changed two things in this PR. First, I've created an elementary script that linearly interpolates the biomass potentials. Secondly, I've changed the retrieve.smk rule for the costs data from technology-data's `output'.

I'd like to ask if it possible to either:

  • Generate a year-by-year technology data for myoptic optimisation in PyPSA-Eur that would like to investigate finer pathways resolutions, or
  • Generate a script that locally interpolates data, thus retaining the existent structure in technology-data and interpolate the data locally for each user.

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 by reviewing the referenced PyPSA-Eur retrieve.smk rule and the technology-data outputs, then compare the two proposed approaches for year-by-year values. Done would be a documented, working way to provide interpolated biomass potentials and technology costs for finer-resolution pathway studies without breaking the existing data structure.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
data
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.