This section describes the genesis and design purpose of the Veda syntax, which started with the Flexible Import tag - ~FI_T - in Excel VBA at the turn of the 21st century. Various tags and conventions have evolved over two decades to serve the core design philosophy of Veda.
Regions and Time
The system settings file (SysSettings) supports some tags that specify the basic structure of the model in terms of regions, time periods, time slices, currencies, and units.
The concept of BookRegions serves a core Veda principle that structures that are common across regions should be declared only once. This applies to the BaseYear templates that exist in the root of the Veda model folder. They are named as VT (Veda Template) _ BookRegion _ Sector _ Version. For example, a model may have ‘VT_ElecReg_ELC_v01’ and ‘VT_DemReg_EndUse_v01’ in the root folder to describe electricity supply in the first file and the demand in the second one. ElecReg could map to Electricity grid regions, which is a reasonable way to represent electricity supply, and DemReg could map to states or provinces, which is a reasonable way to represent demands.
This tag maps the book region (also called super region) to model regions. All declarations in base year templates that do not have a region specification apply to all regions mapped to their book region.
The first year of the model horizon.
To specify period lengths. TIMES automatically computes the middle years as milestone years (along with the StartYear).
This is an alternate way to specify the model periods - by directly specifying the milestone years for which the model will run. TIMES computes the period spans automatically when milestone years are specified. The last year of the model horizon can be specified (optional).
The default year to be used for any timeseries parameter.
List of currencies used in the model. The first entry in this table works as the default currency in Veda.
This tag is used to declare the default process (activity and capacity) and commodity units by sector.
Getting started with the RES
These tags define the key elements - processes, commodities, topology, and core parameters. These tags don’t support wild cards.
The data workhorses
These tags enable bulk insert or update of parameters via technology/commodity filters that are based on set membership, shortname, description, and topology. It is also possible to include existing parameters (and their values) as filter criteria.
TFM_INS-TS: value fields have years as column headers.
TFM_INS-AT: value fields have attributes as column headers.
TFM_INS-TSL: value fields have timeslices as column headers.
TFM_DINS-TS: value fields have years as column headers.
TFM_DINS-AT: value fields have attributes as column headers.
TFM_DINS-TSL: value fields have timeslices as column headers.
TFM_UPD-TS: value fields have years as column headers.
TFM_UPD-AT: value fields have attributes as column headers.
To create sets
The following tags enable creation of named groups of processes and commodities.
This works exactly like the INS tag, but supports text values for the following Veda attributes that can be used to override values that come from the original process/ commodity definition tables: PRC_PCG, PRC_TSL, PRC_VINT, COM_LIM, COM_TSL, COM_TYPE.
This is a legacy tag. Use attribute VDA_EMCB via any regular Veda tag instead.
This is a legacy tag. Use attribute FLO_EMIS via any regular Veda tag instead.