Flexibility for the emission components included in regional EoC budgets#2327
Flexibility for the emission components included in regional EoC budgets#2327tabeado merged 7 commits intoremindmodel:developfrom
Conversation
|
From REMIND standalone test runs: |
RahelMA
left a comment
RahelMA
left a comment
There was a problem hiding this comment.
Thank you, Tabea, for this very nice and helpful PR!
I only have some minor documentation comments.
| *' * (4): excl. other GHGs, incl. LULUCF CO2, incl. bunkers !! = REMIND default for global CO2 budget runs | ||
| *' * (5): excl. other GHGs, excl. LULUCF CO2, incl. bunkers | ||
| *' * (6): excl. other GHGs, excl. LULUCF CO2, excl. bunkers | ||
| *' Note: whether the LULUCF CO2 and the GHG emissions are taxed or not is determined by cm_multigasscen! |
There was a problem hiding this comment.
I see these variations offer the complete set of possibilities :) Im just a bit afraid that they lack plausibility... In general, its probably good to have this flexibility but we should give some guidance on whats useful.
In my view there are these central perspectives:
- policy perspective (what do national policymakers regulate/ target in policy targets (NDC, LTS)
emi|ghg|w/o bunkers|lulucf national accounting
(exclusion of LULUCF for poor data quality)
- modeling perspective starts from the CO2 budeget scenarios, here the allocation should be consistent with the peak/EOC budget calculation
Maybe we should add these two standard cases to the description?
There was a problem hiding this comment.
Thanks for the comment below, I now understood this point better as well and added information
| c_budgetscen "specify the emissions included in the emissions budget used in functionalFormRegi" | ||
| ; | ||
| c_budgetscen = 4; !! def = 4 !! regexp = [1-8] | ||
| *' * (1): incl. other GHGs, incl. LULUCF CO2, incl. bunkers |
There was a problem hiding this comment.
Maybe here it would be nice to use the naming of the output variables, clarifying explicitly LULUCF national accounting!
There was a problem hiding this comment.
From your wording, I am now very confused about the LULUCF data, so I will wait for you to specify what exactly you want to have mentioned here. To my knowledge, the normal REMIND CO2 budget calculation is not using national accounting but the MAgPIE data.
There was a problem hiding this comment.
Please pardon any confusion! The way you have it is only LULUCF modeling, that's correct. For policy implications, we could think about the national accounting and add the variant with the Grassi shift as done in the net-zero calculation here: pm_emiLULUCF_GrassiShift("2020",regi)
There was a problem hiding this comment.
But for now it's good; from my side, you can merge this PR ;)
2 participants
Purpose of this PR
This PR allows to specify which emission components are included in the regional EoC emission budgets, motivated by JustMIP requirements:
The default is set to the normal REMIND CO2 budget calculation.
Note:
cm_multigasscen. I.e. they are typically taxed even if not included in the emission budget the carbon tax is scaled to meet.In addition, we add a description of the relevant switches to be set for regional EoC budget runs in the realization.
Type of change
Indicate the items relevant for your PR by replacing ◻️ with ☑️.
Do not delete any lines. This makes it easier to understand which areas are affected by your changes and which are not.
Parts concerned
Impact
Checklist
Do not delete any line. Leave unfinished elements unchecked so others know how far along you are.
In the end all checkboxes must be ticked before you can merge.
make test) after my final commit and all tests pass (FAIL 0)remind2if and where it was neededforbiddenColumnNamesin readCheckScenarioConfig.R in case the PR leads to deprecated switchesCHANGELOG.mdcorrectly (added, changed, fixed, removed, input data/calibration)Further information (optional)
/p/tmp/tabeado/Equity/EOC_2511/remind_RegiPeak_new/p/tmp/tabeado/Equity/EOC_2511/remind_RegiPeak_new/compScen-2026-04-01_15.27.51-emi.pdf