Include magpie Climate Change in NGFS-related runs#2301
Include magpie Climate Change in NGFS-related runs#2301lecfab wants to merge 1 commit intoremindmodel:developfrom
Conversation
mishkos
left a comment
mishkos
left a comment
There was a problem hiding this comment.
I understand that SSP2-NDC is used in other projects, not only NGFS. My intention was to include climate change impacts in MAgPIE only for NGFS. But since there is no clear distinction for the NDC scenario for NGFS and other projects, this will lead to inconsistency as other scenarios have nocc per default. Is it possible to make a distinct name for NGFS NDC scenario? And also for other commonly defined scearios which are also used in NGFS?
| SSP2_lowEn-PkBudg650;0;;;SSP2|NDC|AR-natveg|nocc_hist;y2030;1;2025;2050;0.03;2025;2050;0.3;const2030;734;;0;0;2030;2030;2030 | ||
| SSP2-EcBudg400;0;;;SSP2|NDC|AR-plant|nocc_hist;y2030;1;2050;2070;0.02;2050;2070;0.2;const2030;734;;0;0;2050;2040;2050 | ||
| SSP2-NDC;0;;;SSP2|NDC|AR-natveg|nocc_hist|rcp4p5;y2150;1;;;0;;;0;const2030;734;;0;1;2030;2030;2030 | ||
| SSP2-NDC;0;;;SSP2|NDC|AR-natveg|cc|rcp4p5;y2150;1;;;0;;;0;const2030;734;;0;1;2030;2030;2030 |
There was a problem hiding this comment.
I understand that SSP2-NDC is used in other projects, not only NGFS. My intention was to include climate change impacts in MAgPIE only for NGFS. But since there is no clear distinction for the NDC scenario for NGFS and other projects, this will lead to inconsistency as other scenarios have nocc per default. Is it possible to make a distinct name for NGFS NDC scenario? And also for other commonly defined scearios which are also used in NGFS?
There was a problem hiding this comment.
We can keep some switches separate between NGFS and default, if we have to (there are anyway two config files, because the title of scenarios differ).
But the general idea is that all choices that we make for "standard" NGFS runs (CP, NDC, 1.5°, 2°) should feed into the default.
Agreed that it's better to have consistency across default scenarios! But don't know if we want all of them to have CC or noCC... =) Who should decide on that?
|
@lecfab It was decided at the NGFS consortium meeting that we should go with no climate change impacts in the Ag sector. Eventually we can test sensitivity to cc in some scenarios. We will have to revert this change :/ |
Good to know thanks! So for the config, we can also remove the rcp tags? |
3 participants
Purpose of this PR
New default in MAgPIE uses climate change impacts. For NGFS, each scenario is now associated with its RCP, and Climate Change impact is taken into account.
This PR merges de NGFS switches into default.
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)