harmonize Xport input data, improve gdx_ref fixing #1412
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Purpose of this PR
core/datainput.gms
that adjusts the historic trade patterns was responsible for an inconsistencies between trade values in the scenario and the reference scenarios fort < cm_startyear
.pm_IO_trade
was loaded forttot
, but the rescaling only happened fort
ttot
, the problem is fixed, also leading to harmonized trade patterns in 2000 for theNPi
run.Results
shows no difference anymore.
Different to before the fix:
The difference between the two NPi runs:
See
/p/tmp/oliverr/remind/compScen-exportfix-2023-09-15_11.39.46-H12-short.pdf
(still running)I thought it may fix more than that, but the only reporting variable that is affected are the
PE|Production|Net|Oil
and|Gas
variables because in this line trade is affecting own consumption coefficients in extraction sector. ThesePE|Production|Net|*
variables now don't complain anymore in the checks done with this script.Type of change
Checklist:
FAIL 0
in the output ofmake test
)CHANGELOG.md
has been updated correctly