PyPSA / PyPSA/pypsa-eur

Fix the electricity and heat consumption of carbon capture in industry

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

Nobody has claimed this yet.

Dominant language
Python
Stars
615
Forks
459
Avg merge
4d 14h
Merged PRs (30d)
6

Description

At the moment the energy demand for carbon capture for process heat from gas and solid biomass is simply modelled as a 10% loss of energy:
https://github.com/PyPSA/pypsa-eur-sec/blob/27cc2935be3c3453779eb2917a002de3166826e1/scripts/prepare_sector_network.py#L1531
https://github.com/PyPSA/pypsa-eur-sec/blob/27cc2935be3c3453779eb2917a002de3166826e1/scripts/prepare_sector_network.py#L1567
Carbon capture from process emissions involves no energy use:
https://github.com/PyPSA/pypsa-eur-sec/blob/27cc2935be3c3453779eb2917a002de3166826e1/scripts/prepare_sector_network.py#L1704
There are assumptions for carbon capture electricity and heat demand for post-combustion capture on cement kilns we can use, but it involves disaggregating the carbon capture and carbon management to each node, so that we can attach to the heat and electricity buses at each node.

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/prepare_sector_network.py at the linked lines 1531, 1567, and 1704 to trace how carbon capture energy demand and carbon management are modelled. Review the existing cement kiln post-combustion capture assumptions and how heat and electricity buses are connected at each node. Done means the gas, solid biomass, and process-emission cases use the intended electricity and heat demands without losing node-level connections.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
backend
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.