NGFS config update, make sure historical CO2 prices are also used in delayed NPi scenario

orichters commented 3 months ago

Purpose of this PR

make sure historical carbon prices are used also if you run a delayed NPi scenario
move China to CO2 not GHG net Zero target in line with https://github.com/iiasa/ngfs-phase-5-workflow/issues/47 and https://github.com/remindmodel/development_issues/issues/291
NGFS scenario config update. Add h_cpol_noUkr scenario without the energy shock and fix on this until 2020. Adjust the reference run for the damage runs. Switch off sectoral differentiation in d_strain as agreed in NGFS consortium meeting. Disable cm_nash_autoconverge_lastrun as it never converges then.

File comparison: scenario_config_NGFS_v4.csv -> scenario_config_NGFS_v5.csv
Columns deleted: -
Columns added:   cm_implicitQttyTarget_tolerance
Renamed columns: -
Renamed rows:    -

Changes in the scenarios:
For all scenarios:
    path_gdx_ref: h_cpol -> h_cpol_noUkr

+ h_cpol_noUkr was added.
~ h_cpol:
    copyConfigFrom: SSP2-Base -> h_cpol_noUkr
~ h_ndc:
    path_gdx_bau: SSP2-Base -> h_cpol_noUkr
~ o_1p5c:
    cm_implicitQttyTarget_tolerance: 0.01 -> 0.1 (default: 0.01)
~ o_lowdem:
    cm_implicitQttyTarget_tolerance: 0.01 -> 0.1 (default: 0.01)
~ o_2c:
    regipol: NA -> regiCarbonPrice (default: none)
    cm_implicitQttyTarget: NA -> 2060.GLO.tax.t.CCS.biomass 2300, 2080.GLO.tax.t.CCS.biomass 2300 (default: off)
~ d_delfrag:
    regipol: NA -> regiCarbonPrice (default: none)
    cm_implicitQttyTarget: NA -> 2060.GLO.tax.t.CCS.biomass 2300, 2080.GLO.tax.t.CCS.biomass 2300 (default: off)
~ d_strain:
    cm_CO2TaxSectorMarkup: GLO.trans 2, GLO.build 2 -> NA (default: off)
    regipol: NA -> regiCarbonPrice (default: none)
    cm_implicitQttyTarget: NA -> 2060.GLO.tax.t.CCS.biomass 2300, 2080.GLO.tax.t.CCS.biomass 2300 (default: off)
~ o_2c_dni50_fixCprice:
    cm_wasteIncinerationCCSshare: 2050.GLO 0.5 -> NA (default: off)
~ o_2c_fixCprice:
    cm_wasteIncinerationCCSshare: 2050.GLO 0.5 -> NA (default: off)
~ d_delfrag_d50:
    path_gdx_ref: h_cpol -> h_cpol_d50
~ d_delfrag_d95:
    path_gdx_ref: h_cpol -> h_cpol_d95
~ d_delfrag_d50high:
    path_gdx_ref: h_cpol -> h_cpol_d50high
~ d_delfrag_d95high:
    path_gdx_ref: h_cpol -> h_cpol_d95high
~ d_strain_d50:
    path_gdx_ref: h_cpol -> h_cpol_d50
~ d_strain_d95:
    path_gdx_ref: h_cpol -> h_cpol_d95
~ d_strain_d50high:
    path_gdx_ref: h_cpol -> h_cpol_d50high
~ d_strain_d95high:
    path_gdx_ref: h_cpol -> h_cpol_d95high

File comparison: scenario_config_coupled_NGFS_v4.csv -> scenario_config_coupled_NGFS_v5.csv
Columns deleted: cm_nash_autoconverge_lastrun
Columns added:   .cm_nash_autoconverge_lastrun
Renamed columns: -
Renamed rows:    -

Changes in the scenarios:
~ SSP2-Base:
    start: NGFS -> NA
+ h_cpol_noUkr was added.

Type of change

[x] Minor change (default scenarios show only small differences)

Checklist:

[x] I performed a self-review of my own code
[x] I explained my changes within the PR, particularly in hard-to-understand areas
[x] I adjusted the reporting in remind2 where it was needed
[x] All automated model tests pass (FAIL 0 in the output of make test)
[x] The changelog CHANGELOG.md has been updated correctly

fpiontek commented 3 months ago

Warum soll der reference run für damage Läufe der h_cpol mit damages sein? Ich dachte, wir hatten das immer ohne, nur für die policy costs sollte es der mit sein (auch wenn das dann nicht wirklich policy costs sind)?

orichters commented 3 months ago

Warum soll der reference run für damage Läufe der h_cpol mit damages sein? Ich dachte, wir hatten das immer ohne, nur für die policy costs sollte es der mit sein (auch wenn das dann nicht wirklich policy costs sind)?

Es geht ja nur um die delayed transition scenarios mit cm_startyear = 2035. d_strain_d50 sollte doch bis 2030 identisch mit h_cpol_d50 sein, oder nicht?

fpiontek commented 3 months ago

Ah, klar, richtig, für die sollte das so sein.

remindmodel / remind