There must always be at least one model configuration YAML file, probably called
model.yaml or similar. This file can import any number of additional files.
This file or this set of files must specify the following top-level configuration keys:
name: the name of the model
model: model settings
run: run settings
techs: technology definitions
tech_groups: tech group definitions
locations: location definitions
links: transmission link definitions
Model settings (
model) affect how the model and its data are built by Calliope, while run settings (
run) only take effect once a built model is run (e.g. interactively via
model.run()). This means that run settings, unlike model settings, can be updated after a model is built and before it is run, by modifying attributes in the built model dataset.
YAML configuration file format¶
All configuration files (with the exception of time series data files) are in the YAML format, “a human friendly data serialisation standard for all programming languages”.
Configuration for Calliope is usually specified as
option: value entries, where
value might be a number, a text string, or a list (e.g. a list of further settings).
Calliope allows an abbreviated form for long, nested settings:
can be written as:
Calliope also allows a special
import: directive in any YAML file. This can specify one or several YAML files to import. If both the imported file and the current file define the same option, the definition in the current file takes precedence.
Using quotation marks (
") to enclose strings is optional, but can help with readability. The three ways of setting
text below are equivalent:
Sometimes, a setting can be either enabled or disabled, in this case, the boolean values
false are used.
Comments can be inserted anywhere in YAML files with the
# symbol. The remainder of a line after
# is interpreted as a comment.
See the YAML website for more general information about YAML.
Calliope internally represents the configuration as
AttrDicts, which are a subclass of the built-in Python dictionary data type (
dict) with added functionality such as YAML reading/writing and attribute access to keys.