G-Cubed Model configuration
Build 199 uses model_configuration.yaml in the root of each model-build directory. The file identifies the model and records model-wide settings used for data preparation, baseline projections, solutions and diagnostics.
Related YAML documentation: model configuration YAML, model years, model file names and baseline tuning.
Where the file belongs
For model version 6W, build 199, the path is:
6W/199/model_configuration.yaml
The file’s model.version and quoted model.build values must match that path.
schema_version: 1
model:
version: "6W"
build: "199"
sector_count: 6
years:
base: 2023
last_projection: 2150
mapping_columns:
gtap:
country: "W"
commodity: standard_6
What it controls
The configuration can declare:
- model identity, reference regions and model features;
- database, calibration and projection years;
- GTAP and, where required, Ember mapping columns;
- overrides for conventional model filenames;
- calibration values;
- projection-input preservation;
- stable-manifold, solution and diagnostic settings; and
- baseline tuning for base-year real interest rates and monetary-policy adjustments.
Omitted optional settings use the documented G-Cubed defaults. Unknown fields, duplicate keys, unsafe filenames and incorrect YAML types are errors.
Baseline tuning
Baseline tuning belongs in model configuration, not a design or setup file. A defaults operation applies to every unlisted region. A region_overrides entry completely replaces that default for one region.
The YAML selects an economic operation. The maintained model-data update script separately chooses whether to disable, summarise or apply it.