Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cement update not linking properly with regional markets for clinker? #184

Closed
kebamba opened this issue Sep 23, 2024 · 2 comments
Closed

Comments

@kebamba
Copy link

kebamba commented Sep 23, 2024

When I create a new database and I only update the cement industry, there are some cement production typew for which the clinker is not linked to the regional clinker market but to clinker production. Thus, it is not taking into account the adoption of CCS in the clinker production for this regions. Example ("model": "image", "pathway": "SSP2-RCP26", "year": 2050. From Ecoinvent v3.9.1 cutoff):
39.8% of 'cement production, Portland (RoW)' comes from 'cement production, Portland (INDIA)'. However, the clinker input for 'cement production, Portland (INDIA)' is 'clinker production (INDIA)', instead of 'market for clinker production (INDIA)'. This is very influential in the climate change results, as 'clinker production (INDIA)' emits ~1.02 kgCO2/kg cement, while 'market for clinker (INDIA) emits ~0.65 kgCO2/kg cement.

The same happens for other regional markets. Also when trying other IMAGE pathways. Am I overlooking something?

@romainsacchi
Copy link
Collaborator

Hi @kebamba,
I understand the issue. That is because some cement production datasets in the original ecoinvent database use the clinker production dataset directly, not the market. I'll fix this and will let you know.

romainsacchi pushed a commit that referenced this issue Oct 3, 2024
@romainsacchi
Copy link
Collaborator

72f656e fixes the issue. You can pip install directly from the repo to try it out or wait for the next 1.2.4 release (maybe later today). Re-open the issue is not solved.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants