Adding Clinker Process Emissions

[toniseibold]

Changes proposed in this Pull Request

During clinker production, the calcination process leads to unavoidable process emissions independent of what's used to supply the heat.
For endogenous heat modelling and cement modelling it is helpful to have this emissions factor in technology data.

The data is from the IPCC Database EF ID 213926 and shows a value of 0.52 tonne CO2/tonne clinker produced
Compared to e.g. POSTED it is slightly higher:
total emissions - coal demand x coal emissivity
0.6361765 − 0.6634401×0.3361 = 0.413194282 tCO2/tclinker

Happy to hear thoughts on that

Checklist

• Code changes are sufficiently documented; i.e. new functions contain docstrings and further explanations may be given in doc.
• Data source for new technologies is clearly stated.
• Newly introduced dependencies are added to environment.yaml (if applicable). not applicable
• A note for the release notes doc/release_notes.rst of the upcoming release is included.
• I consent to the release of this PR's code under the GPLv3 license.

[bobbyxng]

do you mean "Original values 0.5089 [Mt] per Mt clinker"? or is Mt a typo?

[bobbyxng]

LGTM, only a minor comment question on the original values' unit.

[Copilot]

Pull request overview

This PR adds an explicit clinker calcination (process) CO₂ emissions factor to the technology-data cost tables, making clinker/cement sector modelling able to account for unavoidable process emissions independent of heat supply.

Changes:

• Added carbondioxide-output = 0.52 t_CO2/t_clinker for cement dry clinker to inputs/manual_input.csv.
• Propagated the new carbondioxide-output row into the generated outputs/costs_*.csv and outputs/US/costs_*.csv snapshots for all model years.
• Added a corresponding entry to the upcoming release notes.

Reviewed changes

Copilot reviewed 16 out of 16 changed files in this pull request and generated 15 comments.

Show a summary per file

File	Description
outputs/US/costs_2050.csv	Adds clinker process CO₂ output row to US 2050 cost snapshot
outputs/US/costs_2045.csv	Adds clinker process CO₂ output row to US 2045 cost snapshot
outputs/US/costs_2040.csv	Adds clinker process CO₂ output row to US 2040 cost snapshot
outputs/US/costs_2035.csv	Adds clinker process CO₂ output row to US 2035 cost snapshot
outputs/US/costs_2030.csv	Adds clinker process CO₂ output row to US 2030 cost snapshot
outputs/US/costs_2025.csv	Adds clinker process CO₂ output row to US 2025 cost snapshot
outputs/US/costs_2020.csv	Adds clinker process CO₂ output row to US 2020 cost snapshot
outputs/costs_2050.csv	Adds clinker process CO₂ output row to global 2050 cost snapshot
outputs/costs_2045.csv	Adds clinker process CO₂ output row to global 2045 cost snapshot
outputs/costs_2040.csv	Adds clinker process CO₂ output row to global 2040 cost snapshot
outputs/costs_2035.csv	Adds clinker process CO₂ output row to global 2035 cost snapshot
outputs/costs_2030.csv	Adds clinker process CO₂ output row to global 2030 cost snapshot
outputs/costs_2025.csv	Adds clinker process CO₂ output row to global 2025 cost snapshot
outputs/costs_2020.csv	Adds clinker process CO₂ output row to global 2020 cost snapshot
inputs/manual_input.csv	Adds the clinker process CO₂ output factor to the input assumptions table
docs/release_notes.rst	Notes the clinker process emissions addition in the upcoming release section

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[toniseibold]

@fneum Following problem:
If I compare the statistical data from JRC IDEES with the new calculated data I am way off (assuming that "process emissions" are solely coming from the clinker production). That would result in a gap of 16.25 Mt for the PyPSA-DE model scope alone.
To hit the values from JRC IDEES I would have to adjust the factor to 0.711.