Skip to content

External coupling co2 emissions: - #3487

Open
jort-wolda wants to merge 3 commits into
masterfrom
emissions-external-coupling
Open

External coupling co2 emissions:#3487
jort-wolda wants to merge 3 commits into
masterfrom
emissions-external-coupling

Conversation

@jort-wolda

Copy link
Copy Markdown
Contributor

Context

Implemented changes

External coupling co2 emissions:

  • Steel
  • Fertilizers transformations
  • Refineries transformations
  • Chemicals other transformations

Related

Goes with pull requests:

Checklist

  • I have tested these changes
  • I have updated documentation as needed
  • I have tagged the relevant people for review

- Steel
- Fertilizers transformations
- Refineries transformations
- Chemicals other transformations
Based on PR review Claude
@kndehaan
kndehaan removed the request for review from robindesmit-quintel September 7, 2026 14:00
- input.co2 = 1.0
- use = energetic
- scaling_exempt = true
- use = non_energetic

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

use should be the same for the energy node counterpart, which is energetic for the steel node. Could you change this here?


- groups = [preset_demand, direct_emissions]
- input.co2 = 1.0
- scaling_exempt = true

@kndehaan kndehaan Sep 7, 2026

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

After second thought, I don't think we need the scaling_exempt defined on the four molecule nodes. scaling_exempt was needed for the other molecule nodes since they read a dataset value in the ~ demand line. A scaling was done for derived datasets (e.g. other country datasets), which was undesired. This was avoided with scaling_exempt = true.

For the four molecule nodes, however, the demand is set to 0, so I think scaling would not be applied.

Could you test whether the line can be removed by removing it, setting values for the related input and see if you get strange results that might be related to the removed line. Test this please for both a full dataset (e.g. nl2023) and few derived datasets (other countries). If nothing strange happens, you can remove this line on all four molecule nodes.

If the attribute can be removed, you can also remove the docstring about this.

- use = non_energetic
- sector_label = industry_fertilizers

~ demand = 0

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could you apply a float here (0.0), and also to the other molecule nodes?

@kndehaan

kndehaan commented Sep 7, 2026

Copy link
Copy Markdown
Member

General discussion points:

  • Unit of new inputs is in kton, all other absolute emission-related external coupling inputs (except new ones for static emissions) are in Mton. Should we apply Mton as well?
  • Emission sliders added to the respective sector sections in the model, not to Greenhouse gas emissions section
  • Emissions from the external coupling nodes are reported under Industry sector, whereas the node name indicated energy sector
  • industry_steel_external_coupling_node_co2 already existed, but it now works differently where CO2 is set via external coupling input. I therefore think we need a migration to preserve the "demand" on the node for existing scenarios.

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

Successfully merging this pull request may close these issues.

2 participants