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 and terminal conditions;
  • 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.

Common long-run growth

Set calibration.effective_labor_productivity_growth_rate_in_steady_state to an annual percentage log growth rate: 1.4 means 1.4 per cent. technology_advancement_rates.csv contains percentage-point deviations from that common rate and defaults to zeros. See calibration settings for the formula, internal Python units and migration instructions.

Build 200 introduces these semantics as a breaking change within schema_version: 1. Build 199 and earlier used absolute percentage rates in the advancement CSV and decimal units for configured growth. The schema version remains 1 and does not distinguish old decimal-valued configurations and absolute-rate CSVs from migrated inputs. Pair old inputs with their old software release, or migrate both inputs together before using the updated implementation. Numeric magnitude and build identifiers do not trigger automatic conversion.

Terminal conditions

projections.terminal_closure selects how the model continues beyond the last projection year. See Terminal conditions for the economic assumptions, YAML settings for opting into the equilibrium closure, and instructions for restoring the original terminal calculation.

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.

Table of contents