PRISMAupdate

[RahelMA]

Purpose of this PR

The purpose of this PR is to update the PRISMA config in accordance with the first submission.

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

• ◻️ GAMS Code
• ◻️ R-scripts
• ◻️ Documentation (GAMS incode documentation, comments, tutorials)
• ◻️ Input data / CES parameters
• ◻️ Tests, CI/CD (continuous integration/deployment)
• ☑️ Configuration (switches in main.gms, default.cfg, and scenario_config*.csv files)
• ◻️ Other (please give a description)

Impact

• ☑️ Bug fix
• ◻️ Refactoring
• ◻️ New feature
• ◻️ Change of parameter values or input data (including CES parameters)
• ◻️ Minor change (default scenarios show only small differences)
• ◻️ Fundamental change of results of default scenarios

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.

• I executed the automated model tests (make test) after my final commit and all tests pass (FAIL 0)
• I adjusted the reporting in remind2 if and where it was needed
• I adjusted the madrat packages (mrremind and other packages involved) for input data generation if and where it was needed
• My code follows the coding etiquette
• I explained my changes within the PR, particularly in hard-to-understand areas
• I checked that the in-code documentation is up-to-date
• I adjusted forbiddenColumnNames in readCheckScenarioConfig.R in case the PR leads to deprecated switches
• I updated the CHANGELOG.md correctly (added, changed, fixed, removed, input data/calibration)

Further information (optional)

• Runs with these changes are here: REMIND MAgPIE scenarios: /p/tmp/rahelma/cleaning export /p/tmp/leaha/prisma/remind/output/export
• Comparison of results (what changes by this PR?):

[lea-hayez]

@RahelMA I cannot tell what you changed in the PRISMA configs compared to the first submission? Is it anything more than these changes related to the NDC-LTS standard run?

[RahelMA]

@RahelMA I cannot tell what you changed in the PRISMA configs compared to the first submission? Is it anything more than these changes related to the NDC-LTS standard run?

It's mainly the StayingAlive scenario

Here is the change to your branch /p/tmp/leaha/prisma/remind/config/scenario_config_PRISMA.csv

SSP2-StayingAlive:
    start: 1 -> 1,AMT,2
    copyConfigFrom: NA -> SSP2-AsymmetricRoll-Back
    cm_targetDelay: off -> prisma (default: off)
    cm_RenShareTargetValue: "2050.(CAZ 0.62,CHA 0.83,EUR 0.88,IND 0.94,JPN 0.74,LAM 0.78,MEA 0.79,NEU 0.66,OAS 0.9,REF 0.58,SSA 0.91,USA 0.9).SolarWindElec" -> 2050.(CAZ 62,CHA 83,EUR 88,IND 94,JPN 74,LAM 78,MEA 79,NEU 66,OAS 90,REF 58,SSA 91,USA 90).SolarWindElec, 2100.(CAZ 66,CHA 82,EUR 91,IND 95,JPN 75,LAM 86,MEA 97,NEU 71,OAS 94,REF 87,SSA 96,USA 92).SolarWindElec (default: off)
    cm_LTSexcludeRegi: USA -> off (default: USA)
    carbonpriceRegi: none -> netZero (default: none)
    path_gdx_ref: SSP2-AsymmetricRoll-Back -> /p/tmp/leaha/prisma/remind/output/C_SSP2-NPi2025_2026-05-11_17.46.13/fulldata.gdx
    path_gdx_bau: SSP2-AsymmetricRoll-Back -> /p/tmp/leaha/prisma/remind/output/C_SSP2-NPi2025_2026-05-11_17.46.13/fulldata.gdx
    path_gdx_carbonprice: SSP2-AsymmetricRoll-Back -> NA
    path_gdx_refpolicycost: SSP2-AsymmetricRoll-Back -> /p/tmp/leaha/prisma/remind/output/C_SSP2-AsymmetricRoll-Back_2026-05-13_15.10.56/fulldata.gdx
    subsidizeLearning: off -> globallyOptimal (default: off)
    cm_iterative_target_adj: 0 -> 9 (default: 0)

[lecfab]

Do we still want to keep the shared config up to date? if not we should delete it to avoid confusion for the future set of runs :)
https://docs.google.com/spreadsheets/d/1rtAqGCN6ubpS_hEwufr67ws0M_viweQwafYAtIRUKI0

[RahelMA]

Do we still want to keep the shared config up to date? if not we should delete it to avoid confusion for the future set of runs :) https://docs.google.com/spreadsheets/d/1rtAqGCN6ubpS_hEwufr67ws0M_viweQwafYAtIRUKI0

Yes, I think we should keep it! So we update to the latest submission?