Support for new switches to represent trade scenarios with limited cooperation between regions

[Renato-Rodrigues]

Purpose of this PR

Added support for new switches to represent trade scenarios with limited cooperation between regions (WP5 of the ECEMF project)

• option to limit specific regions exports. See cm_XportRegiLim description in the main.lst file.

• option to define independent learning cumulative capacity for alternative region groups. See cm_altLearnRegiSet description in the main.lst file.

• update ECEMF scenario config file with WP5p1 scenarios.

Type of change

• New feature

Checklist:

• My code follows the coding etiquette
• I performed a self-review of my own code
• I explained my changes within the PR, particularly in hard-to-understand areas
• All automated model tests pass (FAIL 0 in the output of make test)
• The changelog CHANGELOG.md has been updated correctly

Further information (optional):

• Test runs are here:
  /p/projects/ecemf/REMIND/2040_scenarios/v04_2023_06_02_WP5/output

[robertpietzcker]

Based on experiments that Rahel did last week where she limited learning to the region itself, I guess here also the learning changes need to be adjusted a bit.

If I don't overlook something, the changes in remind/modules/22_subsidizeLearning/globallyOptimal/presolve.gms mean that ONLY the cumulative capacities in the "learning together" regions is taken into account. However, the parameters for the learning equation are calculated based on 2020 regional costs and 2020 GLOBAL capacity - meaning 2020 investment costs with separate learning will be much higher than the regional investment costs to which the model should be calibrated.

I proposed to Rahel to solve this by differentiating the time steps before 2020 and after 2020; using global learning until 2020 and then for time steps after 2020 taking the 2020 cumulative capacity of "out-group regions" and the full cumulative capacity of "in-group regions"

so for her it was only

pm_capCumForeign(ttot,regi,teLearn)$((ttot.val ge 2005) and (pm_SolNonInfes(regi) eq 1) ) = sum(regi2$((NOT sameas(regi,regi2))), pm_capCum0(ttot,regi2,teLearn));

pm_capCumForeign(ttot,regi,teLearn)$((ttot.val ge 2025) and (pm_SolNonInfes(regi) eq 1) and (cm_LearningSpillover eq 0)) = sum(regi2$((NOT sameas(regi,regi2))), pm_capCum0("2020",regi2,teLearn));ms

for you the second part would rather be something like

pm_capCumForeign(ttot,regi,teLearn)$((ttot.val ge 2025) and (pm_SolNonInfes(regi) eq 1) and (cm_LearningSpillover eq 0)) = 
sum(regi2$((NOT sameas(regi,regi2)) AND NOT(altLearnRegi22(regi2,teLearn), pm_capCum0("2020",regi2,teLearn)))

+ 
sum(regi2$((NOT sameas(regi,regi2)) AND (altLearnRegi22(regi2,teLearn), pm_capCum0(ttot,regi2,teLearn)));

or so.

I hope I am not mistaken and you already account for this somewhere :-)

[Renato-Rodrigues]

Is this what you had in mind?
cfbc646

There is one more thing that I don't get:
Why is pm_capCumForeign redefined in the 80_optimization\nash\presolve if it was already defined in the 22_subsidizedLeraning|globallyOptimal\presolve ?

[LaviniaBaumstark]

what is the status of this PR? will you continue working on it?

[Renato-Rodrigues]

yes, it is still a wip.

[LaviniaBaumstark]

what is the status of this PR? will you continue working on it?

[Renato-Rodrigues]

This is being further discussed in the ECEMF (WP 5.1), and in a few months it will be defined if the scenarios that require these changes will evolve into a publication or not.
If the decision is positive in the project side, this PR will be re-tested/updated and merged to the REMIND code.
If the decision is negative, I will delete the PR at the time.