Repository navigation
Show how GCAM output files become MARIO mix shocks - #1
Draft
LorenzoRinaldi wants to merge 3 commits into
Draft
LorenzoRinaldi wants to merge 3 commits into
LorenzoRinaldi wants to merge 3 commits into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The existing study starts from prepared mix workbooks and machine-specific paths, making the GCAM-to-MARIO interpretation difficult to follow. This adds an executable route from physical GCAM CSV outputs through explicit technology/region concordances and share normalisation to native MARIO
u,sandYcchanges, with actual coefficients read back alongside the expected formula.The README and executed notebook follow one published wind-generation value (4.51167191 EJ/yr) into a 0.391284374506 share and a MARIO coefficient. Users can inspect inputs without a database, isolate electricity or steel, run both on a small teaching SUT, or apply the same functions to extended EXIOBASE. The teaching inventories/demand are clearly fictional; GCAM inputs are actual study results.
Included inputs and behaviour:
SteelProdTechexport. Their EU-12 + EU-15 sums match all 504 published EU27 scenario/year/route values (maximum absolute difference 1.42e-14 Mt/yr).Validation: 25 tests passed, all 11 notebook code cells executed, documentation/input hashes checked, and the figure visually inspected. The full 23-region source was prepared, exported and reloaded. An installed wheel then ran the user CLI outside the checkout and offline; independent checks verified the unchanged baseline and satellite coefficients, conserved electricity/supply totals, electrolysis exclusion, output hashes and actual coefficient values. The live fixed-record download/resume path was checked on a small source file; large matrices already verified from the byte-equivalent v1.3.2 record were reused.
The historical study scripts, inventories and derived workbooks are unchanged. This new route applies EU mix shocks, retaining background demand/trade and other regions' mixes. It does not run GCAM or claim full reproduction of the paper's figures or absolute consumption/import volumes. The old driver's unapplied demand/import logic is documented in
docs/research-workflow.mdrather than silently treated as a working trade shock.Evidence:
docs/verification.md,verification/full-model.json, source receipts and the executednotebooks/GCAM_to_MARIO.ipynb.