SYSSETTINGS
This is one of the three files in VEDA with a fixed name, which stands for System Settings. It is located in the root of the template folder, and is used to declare the very basic model structure like regions, timeslices, start year etc. It also contains interpolation rules for various attributes and some settings for the synchronization process. This file is flagged for import during any synchronization operation, and it is read at the end of the process. Here is a complete list of the basic declarations that are made in this file:
- Regions: the first table shown in Figure 1 maps the names used in B-Y templates to the model regions. For example, the B-Y template VT_REG_SectorName_VerX will create data for region REG and VT_MREG_SectorName_VerX for regions REG1 through REG10.
FIGURE 1: REGION AND TIMESLICE DECLARATION
FIGURE 2: MODELING HORIZON
- Modeling Horizon: this comprises the start year and period durations (Figure 2). Alternate period definitions can be made and the active one is declared under the tag ~ActiveDef. For example, Pdef-1 implies that the first period is 1 year long, the second has 2 years, third 5 years and so on. This table can be managed via a user interface in Advanced Functions – Add MileStone Years as well. All changes made there are automatically updated in the last two tables. StartYear can be changed only in the SysSettings file, and it is strongly recommended to start the synchronization process from scratch (Tools – Start from Scratch) if such a change is made.
FIGURE 3: CURRENCIES AND DEFAULT UNITS (BY SECTOR)
- Currencies: the list of currencies used in the model can be declared as shown in the first table above. The first one serves as the default currency throughout the model.
- Default Units: default units for processes and commodities, by sector, are declared as shown in the second table above.
FIGURE 4: USER-DEFINED COMMODITY GROUPS
- User-defined Commodity Groups: one can go quite far with VEDA-created commodity groups ( <ProcessName>_<CommodityType><I/O>; for example, EOILGAS_NRGI would be the group of NRG commodities on the Input side of process EOILGAS), but one does need special commodity groups at times. Especially those that cut across processes. This can be done (only) in the SysSettings file in the table shown above. Commodities can be filtered using set membership, name and description. Y in the region column creates a group with the specified name and description. There will be a user interface to manage this table in a future version of VEDA_FE.
FIGURE 5: CONTROLLING THE IMPORT PROCESS
- Dummy Imports: one can control the creation of dummy imports in the table shown above.
- Vintage Bounds: VEDA can automatically generate bounds to prohibit investments in processes when a newer vintage becomes available, assuming that the last two characters of the process name are used for the first year of availability. For example, TCAR05 will no longer be available for investment after TCAR15 becomes available. This feature is one of the surviving relics from the MARKAL days of VEDA, when full vintaging was not available. It can still be used as a parsimonious substitute for full vintaging option of TIMES. However, users must be much disciplined in naming processes while using this option.
All tables described so far are specific to the SysSettings file and are not supported in any other file in the system. The tables above are read only when the date-time stamp of this file changes.
Over and above all the special tables, SysSettings supports all the tables used in regular scenario files. It is recommended to have the following declarations via INS and UPD tables shown below:
- Interpolation settings
- Dummy Import prices
- Global constants – discount rate and year fraction in each timeslice
FIGURE 6: INTERPOLATION SETTINGS AND DUMMY IMPORT PRICES
FIGURE 7: GLOBAL CONSTANTS