31-08-2021, 02:56 PM

Dear Dr Antti,

I tried the above suggestion assuming only 1% decline but somehow my model becomes infeasible. I tried once in the year 2032 and again in the year 2047 and in both cases, the model becomes infeasible. Model Data horizon is from 2012 to 2082.

I tried referring to the TIMES manual based on the parameters you have used for developing the user constraint.

TIMES Documentation:

Defining Growth Constraint: all growth coefficients are specified for the RHS variables, the dynamic constraint will be assumed to be of type (t–1,t), and the growth constraints are now generated for the period pairs t–1 and t for all periods of the model horizon.

To build a dynamic user constraint of type (t–1,t), between the periods t–1 and t, the

modeller should indicate the desired type by defining for the constraint any UC_ATTR

attribute using the 'RHS' side.

In addition, the desired set of time periods that will be used

as the second period in the pairs(t–1,t) should be identified by defining the RHS constant

parameter for those periods t.

VS> I am not sure how we are defining the use of the second period in the above method.

TIMES documentation: The input parameters for defining the coefficients UC_COMNET should have an index side,

which can be either LHS or RHS. The LHS index corresponds always

to the period t, while the RHS index is related either to the t+1 or the t–1 term.

I tried the above suggestion assuming only 1% decline but somehow my model becomes infeasible. I tried once in the year 2032 and again in the year 2047 and in both cases, the model becomes infeasible. Model Data horizon is from 2012 to 2082.

I tried referring to the TIMES manual based on the parameters you have used for developing the user constraint.

TIMES Documentation:

Defining Growth Constraint: all growth coefficients are specified for the RHS variables, the dynamic constraint will be assumed to be of type (t–1,t), and the growth constraints are now generated for the period pairs t–1 and t for all periods of the model horizon.

To build a dynamic user constraint of type (t–1,t), between the periods t–1 and t, the

modeller should indicate the desired type by defining for the constraint any UC_ATTR

attribute using the 'RHS' side.

In addition, the desired set of time periods that will be used

as the second period in the pairs(t–1,t) should be identified by defining the RHS constant

parameter for those periods t.

VS> I am not sure how we are defining the use of the second period in the above method.

TIMES documentation: The input parameters for defining the coefficients UC_COMNET should have an index side,

which can be either LHS or RHS. The LHS index corresponds always

to the period t, while the RHS index is related either to the t+1 or the t–1 term.