Baseline tuning

baseline_tuning selects model-data operations used to tune the baseline. It can configure:

• real interest rates in the base year; and
• monetary-policy adjustments.

The effective operation depends on the regional entry:

YAML	Meaning
no baseline_tuning section	No tuning operation is configured
a defaults operation	Applies to every region not named in region_overrides
a complete region_overrides operation	Completely replaces the default for that region
monetary region_overrides: {OIL: {exclude: true}}	Excludes OIL from INTX tuning, including when a default exists

A regional adjustment or transition is never a partial amendment. It must contain every field needed by its selected method or transition. Monetary policy also accepts the separate, exact {exclude: true} override form; mixing it with transition fields is invalid. Real-interest-rate tuning does not accept exclusions.

Monetary exclusions work with or without defaults and preserve existing database INTX values. When no effective transitions remain, summary and apply report no configured operations and write no files. See monetary-policy tuning for selection, file handling and the implementing-package compatibility boundary. Schema version remains 1.

Configure both tuning operations

baseline_tuning:
  real_interest_rates_in_base_year:
    propagation:
      other_domestic_nominal_price_indices: true
      wages: true
    defaults:
      adjustment_method: range
      floor_real_interest_rate: 0.0
      ceiling_real_interest_rate: 7.5

  monetary_policy_adjustments:
    projections_file_name: baseline_INTX_projections.csv
    defaults:
      start_year: 2023
      end_year: 2030
      annual_decay_percent: 50.0

The YAML selects the economic operations. The maintained python/update_model_data.py script separately chooses whether each operation is disabled, shown as a summary, or applied with apply.