Sets and Parameters - iea-etsap

Table 3: Parameters that can have values defined for any year, irrespective of
datayear 12
Attribute name
G_DRATE
G_CHNGMONY
MULTI
COM_CUMPRD
COM_CUMNET
CM_HISTORY
Description
General discount rate for currency in a particular year
Exchange rate for currency in a particular year
Parameter multiplier table with values by year
Cumulative limit on gross production of a commodity for a
block of years
Cumulative limit on net production of a commodity for a block
of years
Climate module calibration values; not part of the standard
TIMES code, but included in the climate module extension
(see chapter 7 for a description of the climate module).
2.2.2.2 Timeslices
The milestoneyears can be further divided in sub-annual timeslices in order to describe for
the changing electricity load within a year which may affect the required electricity generation
capacity, or other commodity flows that need to be tracked at a finer than annual resolution.
Timeslices may be organised into four hierarchy levels only: ‘ANNUAL’, ‘SEASON’,
‘WEEKLY’ and ‘DAYNITE’ defined by the internal set tslvl. The level ANNUAL consists
of only one member, the predefined timeslice ‘ANNUAL,’ while the other levels may include
an arbitrary number of divisions. The desired timeslice levels are activated by the user
providing entries in set ts_group(r,tslvl,s), where also the individual user-provided timeslices
(s) are assigned to each level. An additional user input set ts_map(r,s1,s2) is needed to
determine the structure of a timeslice tree, where timeslice s1 is defined as the parent node of
s2. Figure 6 illustrates a timeslice tree, in which a year is divided into four seasons consisting
of working days and weekends, and each day is further divided into day and night timeslices.
The name of each timeslice has to be unique in order to be used later as an index in other sets
and parameters. Not all timeslice levels have to be utilized when building a timeslice tree, for
example one can skip the ‘WEEKLY’ level and directly connect the seasonal timeslices with
the daynite timeslices. The duration of each timeslice is expressed as a fraction of the year by
the parameter G_YRFR(r,s). The user is responsible for ensuring that each lower level group
sums up properly to its parent timeslice, as this is not verified by the pre-processor. The
definition of a timeslice tree is region-specific. When different timeslice names and durations
are used in two regions, which are connected by an exchange process, the mapping
parameters IRE_CCVT(r,c,reg,com) for commodities and IRE_TSCVT(r,s,reg,ts) for
timeslices have to be provided by the user to map the different timeslice definitions. When the
same timeslice definitions are used, these mapping tables do not need to be specified by the
user.
12 The purpose of this table is to list those parameters whose year values are independent
of the input datayears associated with most of the regular parameters, and therefore should
not be specified for datayears. For example, a value for MULTI(j,'2012') would not include
2012 in datayears if 2012 were not relevant to the other input parameters.
22