Adding spatially resolved CO2 removal by perennialization
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
Research direction
Start by reviewing the analogous issue 2140 and technology-data pull request 255, then locate the model configuration for links. Confirm how the perennialization link should consume electricity, produce biogas, and remove CO2 across regions. Done means the regional potential assumptions and technology inputs are represented in the model; the issue mentions no tests or files to run.
Written by the indexing model from the issue text.
Description
Same argument as in: https://github.com/PyPSA/pypsa-eur/issues/2140
Perennialization = conversion of annual crops into perennial systems that enhances carbon removal through continuous photosynthesis, deeper root systems, and reduced soil disturbance. Combined with green biorefinery, it also increases biogas potential.
Electricity input and biogas output associated with capturing 1 ton CO2 via perennialization, as well as costs, are already included in the technology-data repository
https://github.com/PyPSA/technology-data/pull/255
Potential removal in every region can be estimated assuming that first-generation biofuel crops are no longer cultivated in Europe by 2050 and that perennial crops can fully replace the land previously allocated to these crops.
Also, assuming an emission reduction of 2 tCO2e/(ha·a), which corresponds to the replacement of maize with a grass-clover mixture
We have estimated the removal potential of perennialization in Europe as 43 MtCO2/a, with additional biogas production of 37 MWh/a
More details: https://arxiv.org/abs/2603.25663
Perennialization can be modelled as a link that consumes electricity, produces biogas and removes CO2.
This is a description, and a PR will follow.
- Dominant language
- Python
- Stars
- 615
- Forks
- 459
- Avg merge
- 4d 14h
- Merged PRs (30d)
- 6
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from PyPSA/pypsa-eur
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Individual NUTS level definition not working in `clustering.administrative.countries` config setting Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
bancolombia/sentinel#23 ·
-
test md OpenCI
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
bug client
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100