Elevate WP2p3 temp

[RahelMA]

Purpose of this PR

Update the ELEVATE WP2.3 template to the latest and final submission.

• fixing CurPol runs to NPi2025 until 2030
  

• reduce ambition in the second half of the century from
  
  to
  

• For documentation, include switch cm_constEmiSSA

ELEVATE: Shift to a post-2055 carbon price increase in SSA to avoid the growth-induced emissions increase in the second half of the century. This is a project related fix for the issue of increasing emissions in SSA after 2040.

Change the start year of NDC and LTS to 2030, as 2025 now runs in infes for CAZ and cm_startyear 2030 follows our new default.

Chance in the config:

Columns deleted: -
Columns added:   c_changeProdCost, cm_CESMkup_ind, cm_constEmiSSA
Renamed columns: -
Renamed rows:    -

Changes in the rows:
~ ELV_CurPol_NPi:
    description: was changed (default: REMIND run with default settings)
~ ELV-SSP2-CP-D0:
    cm_startyear: 2005 -> 2030 (default: 2005)
~ ELV-SSP2-CP-D1:
    cm_startyear: 2005 -> 2030 (default: 2005)
~ ELV-SSP2-CP-D3:
    cm_startyear: 2005 -> 2030 (default: 2005)
~ ELV_NDC2030:
    cm_startyear: 2025 -> 2030 (default: 2005)
    c_changeProdCost: NA -> 1 (default: 5)
    cm_constEmiSSA: NA -> on
~ ELV-SSP2-NDC-D0:
    c_changeProdCost: NA -> 1 (default: 5)
    cm_constEmiSSA: NA -> on
~ ELV-SSP2-NDC-D1:
    c_changeProdCost: NA -> 1 (default: 5)
    cm_constEmiSSA: NA -> on
~ ELV-SSP2-NDC-D3:
    c_changeProdCost: NA -> 1 (default: 5)
    cm_constEmiSSA: NA -> on
~ ELV-SSP2-LTS:
    cm_startyear: 2025 -> 2030 (default: 2005)
    c_changeProdCost: NA -> 1 (default: 5)
    cm_constEmiSSA: NA -> on
~ ELV-SSP2-NDC-LTS:
    c_changeProdCost: NA -> 1 (default: 5)
    cm_constEmiSSA: NA -> on
~ ELV-SSP2-1000:
    c_changeProdCost: NA -> 1 (default: 5)
~ ELV-SSP2-650:
    cm_taxCO2_startyear: 200 -> 100 (default: -1)
    cm_taxCO2_IncAfterPeakBudgYr: 3 -> 1 (default: 0)
    cm_multigasscen: 3 -> 2 (default: 3)
    description: was changed (default: REMIND run with default settings)
    c_changeProdCost: NA -> 1 (default: 5)
    cm_CESMkup_ind: NA -> Elec_Push (default: standard)

$allwarnings
NULL

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: /p/projects/elevate/WP2.3/submission_10042025 (based on master 3.5),
  /p/tmp/rahelma/ElevateWP2_3/develop/output (dev 3.5.0.dev447)
• Comparison of results (what changes by this PR?):
  /p/tmp/rahelma/ElevateWP2_3/develop/output/ouput/compare_scenarios_2025-07-10_16.42.07.pdf

[laurinks]

Could you explain what you would like to achieve with this line?

If I am not mistaken, smax(ttot2$( ttot2.val gt 2055 ), ttot2.val) is equal to the largest element in the set, i.e. 2150.

[laurinks]

FYI: For ScenarioMIP, we have submitted under 3.5-4.11 since the latest MAgPIE release was 4.11.0.

[laurinks]

Could you mention here that this switch only affects the 45_carbonprice/NDC implementation? And maybe also what it does, i.e. use exponentially increasing carbon price in SSA from 2055.