PyPSA / PyPSA/technology-data

Disentangle parameters for post-combustion carbon capture

Open
#276 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Hi @euronion ,

Thanks for explaining so thoroughly what you mean.

I have looked into this and realised this isn't actually a result of any of my code changes. These are the values extracted within the existing loop in any case; all I did was add my technology to the loop. I think it would be the wrong approach to change this within a pull request to include one more technology, because (i) it might break others' code if they rely on these outputs and update technology-data, and (ii) the change in data will be harder to trace if hidden within a PR commit for a different issue.

Regarding the solution, I have been working closely with the DEA's PDF document on carbon capture, and they give a figure allowing you to calculate an "uplift factor" for how much to change the specific total investment, including all the "hereof" mentions. Therefore, I would find the first structure you suggest more confusing, as for me it's natural to work simply with the total specific investment, without having to add up its constituent parts to get there. The second structure would then be better, just to check - this implies removing the following lines in name_list:

            (
                "CO₂ compression and dehydration - Electricity input",
                "compression-electricity-input",
            ),
            ("CO₂ compression and dehydration - Heat out", "compression-heat-output"),

I believe this would result in just the yellow-highlighted values being reported, and the red highlighted ones would no-longer be supported:

image

Provided I've understood you correctly, I could implement this change, but, as mentioned, maybe it would be better as its own separate PR?

Thanks!

Originally posted by @jonathan-peel in https://github.com/PyPSA/technology-data/pull/253#discussion_r3247043524

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 locating the name_list definition and reading the discussion in pull request #253 about the post-combustion carbon-capture parameters. Check how the two compression entries affect the reported technology-data outputs. Done means the parameter structure matches the agreed interpretation and the unsupported values are no longer reported.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
data
Issue type
Refactor
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.