Sets and Parameters - iea-etsap

Table 9: Option codes for the extrapolation of SHAPE indexes
Option code
Action
= 2 Extrapolation between and outside data points
Example:
The user has specified the following two SHAPE indexes and a control option for
extrapolation:
NCAP_AFX('REG', '0', 'PRC1') = 1;
NCAP_AFX('REG', '1995', 'PRC1') = 12;
NCAP_AFX('REG', '2010', 'PRC1') = 13;
In this case, all modelyears (v) between 1995 and 2010 will get the shape index 12. No
extrapolation is done for modelyears (v) beyond 2010 or before 1995.
The extrapolation options are currently available for the following SHAPE parameters, which
are an indicator for the SHAPE curve that should be applied to the corresponding parameter:
• NCAP_AFX,
• NCAP_FOMX,
• NCAP_FSUBX,
• NCAP_FTAXX,
• FLO_FUNCX.
3.1.2 Inheritance and aggregation of timesliced input parameters
As mentioned before, processes and commodities can be modelled in TIMES on different
timeslice levels. Some of the input parameters, which describe a process or a commodity, are
timeslice specific, i.e. they have to be provided by the user for specific timeslices, e.g. the
availability factor NCAP_AF of a power plant operating on a ‘DAYNITE’ timeslice level.
During the process of developing a model, the timeslice resolution of some processes or even
the entire model may be refined. One could imagine for example the situation that a user
starts developing a model on an ‘ANNUAL’ timeslice level and refines the model later by
refining the timeslice definition of the processes and commodities. In order to avoid the need
for all the timeslice related parameters to be re-entered again for the finer timeslices, TIMES
supports the inheritance and aggregation of parameters along the timeslice tree (see Figure 1).
Inheritance in this context means that input data being specified on a coarser timeslice level
(higher up the tree) are inherited to a finer timeslice level (lower down the tree), whereas
aggregation means that timeslice specific data are aggregated from a finer timeslice level
(lower down the tree) to a coarser one (further up the tree). The inheritance feature may also
be useful in some cases where the value of a parameter should be the same over all timeslices,
since in this case it is sufficient to provide the parameter value for the ‘ANNUAL’ timeslice
which is then inherited to the required finer target timeslices 20 .
20 The term target timeslice level or target timeslice is used in the following as synonym
for the timeslice level or timeslices which are required by the model generators depending on
the process or commodity timeslice resolution (prc_tsl and com_tsl respectively).
42