3. Sets, Switches and Parameters¶
3.1. Switches¶
Besides the basic data parameters described in Table 3.19 below, the user controls whether the linear or non-linear formulation is activated by means of the switches shown in Table 3.18. These switches are provided by the data handling system when the user indicates that the option is to be included in a run.
Switch |
Parameter Description |
|---|---|
$SET TIMESED NO |
Causes the Base Prices to be saved to a GDX file, for subsequent use in a policy analysis run based on any of the elastic demand options. |
$SET TIMESED YES |
Activates any of LP formulations used for Demand Functions (exact formulations depending on input data) |
$SET MICRO YES |
Activates any of NLP or mixed LP/NLP formulations used for Demand Functions (exact formulations depending on input data) |
3.2. Sets and Parameters¶
Like all other aspects of TIMES the user describes the demand functions for the energy system model by means of a Set and the Parameters and Switches described in this chapter. Table 3.19 below describes the User Input Parameters associated with defining the TIMES demand functions.
Parameter (Indexes) |
Units & defaults |
Parameter Description |
|---|---|---|
COM_PROJ (r,y,c) |
Commodity unit;
|
Exogenous reference (Baseline) demand projection of commodity c in region r and year y.
|
COM_AGG (r,y,c,com) |
Commodity units
|
Defines an aggregation of component demand c into an aggregate demand com in region r and year (period) y.
|
COM_VOC (r,y,c,bd) |
Dimensionless;
|
Defines the maximum demand variation in the lower / upper direction (bd=LO/UP) for demand c in region r and year y. The value gives the maximum deviation in proportion to the Baseline demand. Different values may be provided for each direction, thus demand elasticity curves may be asymmetric. |
COM_STEP (r,c,bd) |
Integer
|
Number of steps to use for the approximation of demand variation in the lower / upper direction (bd=LO/UP), and the associated change in producer/consumer surplus, for commodity c in region r, when using the elastic demand formulations. The shortcut bd=FX may be used for defining the same number of steps in both directions. |
COM_ELAST (r,y,c,s,bd) |
Dimensionless;
|
Elasticity of demand for commodity c, indicating the following:
|
Important remarks:
COM_PROJ should be explicitly defined by the user only for the component demands, and never for the aggregate demands.
As mentioned in Table 3.19, the substitution elasticities can be defined by specifying COM_ELAST(r,t,com,ANNUAL,’N’) for the aggregate demands. However, ‘FX’ elasticities for the component demands can be optionally specified for defining component-differentiated substitution elasticities. Nonetheless, even when doing so, COM_ELAST(r,t,com, ANNUAL,’N’) always defines the minimum substitution elasticity among the component demands of com.
Note that the aggregate demands are always at the ANNUAL level only, and thus only ANNUAL level own-price demand elasticities are supported for the demand aggregates.
When using the non-linear formulation, demand substitution is supported only at the ANNUAL level for the component demands of the CES aggregates. The demand variations will thus be proportionally the same for all timeslices.
Multi-level nested CES demand aggregations are also fully supported both in the non-linear and in the linearized case.
Recursive CES demand aggregations are not supported, neither in the non-linear nor in the linearized case.
The Cobb-Douglas case (\(σ_{k}=1\)) is also supported, but in the non-linear formulation it is handled by setting \(σ_{k}\) very close to unity.