Veda2.0 Released!


About RNW capacity
#1
Dear all,
     When setting the capacity for PV, the parameters for PV are 400 GW and 2500 GW in 2030 and 2060, respectively. However, the results are  400 for 2030, 200 for 2050, 2500 for 2060. It is correct from the least cost of objective function, while it is unreasonable for the real path. Could you please help me to correct it?
    Thank you very much.
Zhi Guo


Attached Files
.xlsx   UC_SOLAR_CAP.xlsx (Size: 9.25 KB / Downloads: 2)
Reply
#2
Looks as if your interpolation option would somehow be ignored, or perhaps you have defined an overriding value somewhere else. Could you thus show all the UC_RHSRT parameters for this constraint from Browse or Items detail (with all dimensions expanded, including Scenario).
Reply
#3
(10-05-2022, 05:00 PM)Antti-L Wrote: Looks as if your interpolation option would somehow be ignored, or perhaps you have defined an overriding value somewhere else. Could you thus show all the UC_RHSRT parameters for this constraint from Browse or Items detail (with all dimensions expanded, including Scenario).

       Thank you very much. As you suggested, I found the wrong from Browse and corrected it. Now I have another question, could you please help me ? Compared with BAU, I set the tax for CO2  from power sector. The reality is that I levy tax from 2025, while the results show that the CO2 emission show the reduction trend from 2019 rather than 2025. Is there any wrong with the interpolation or how to correct it?
    Thank you very much.
Zhi GUO


Attached Files
.xls   Scen_CO2_TAX_300.XLS (Size: 44.5 KB / Downloads: 2)
Reply
#4
Quote from the documentation:

As a general rule, all cost parameters in TIMES are densely interpolated and extrapolated. This means that the parameters will have a value for every single year within the range of years they apply, and the changes in costs over years will thus be accurately taken into account in the objective function.  The user can use the interpolation options 1–5 for even cost parameters. Whenever an option is specified for a cost parameter, it will be first sparsely interpolated/extrapolated according to the user option over the union of modelyear and datayear, and any remaining empty data points are filled with the EPS value. The EPS values will ensure that despite the subsequent dense interpolation the effect of user option will be preserved to the extent possible. However, one should note that due to dense interpolation, the effects of the user options will inevitably be smoothed.

You have defined the IE option 5 for COM_TAXNET, and your first data point is 0.001 in 2024 in your tax scenario. As you can see from the explanation above, this results in the EPS value (zero) being filled for the preceding model milestone year. If that year is 2019, the resulting tax will be zero in 2019, and it is then interpolated from that zero value in 2019 to the value 0.001 in 2024. If you want the tax to be strictly zero until 2024, you should just define a zero value for 2024, instead of 0.001.

Concerning the CO2 emissions showing a reduction trend from 2019, please also recall that a TIMES model is by default solved with perfect foresight, where policies implemented in the future are assumed to be known by the decision-makers and may thus affect investments also in earlier years.

However, 2019 is a historical year, and therefore you should not need any investments into new capacity in that period. You can model all the capacities that were existing in 2019 with past investments or residual capacities, and therefore you can disable any new investments in 2019.  Consequently, when properly modelled, you should not see any impact of the CO2 tax imposed in 2025 on the power sector investments in 2019.  And neither should that tax affect the operating decisions of power plants in the period 2019, if the tax remains zero in that period. Therefore, you should not see any impact on emissions in 2019.

However, if deemed useful, you can also disable the impact of any tax imposed in 2025 or later on any earlier investments or operation, by running the model first without the new policy, and then by fixing all the historical model periods to that "BAU" solution, when running the model with any new policies. VEDA/TIMES does indeed support an easy way of fixing the first periods to a previous solution.
Reply
#5
(12-05-2022, 02:21 PM)Antti-L Wrote: Quote from the documentation:

As a general rule, all cost parameters in TIMES are densely interpolated and extrapolated. This means that the parameters will have a value for every single year within the range of years they apply, and the changes in costs over years will thus be accurately taken into account in the objective function.  The user can use the interpolation options 1–5 for even cost parameters. Whenever an option is specified for a cost parameter, it will be first sparsely interpolated/extrapolated according to the user option over the union of modelyear and datayear, and any remaining empty data points are filled with the EPS value. The EPS values will ensure that despite the subsequent dense interpolation the effect of user option will be preserved to the extent possible. However, one should note that due to dense interpolation, the effects of the user options will inevitably be smoothed.

You have defined the IE option 5 for COM_TAXNET, and your first data point is 0.001 in 2024 in your tax scenario. As you can see from the explanation above, this results in the EPS value (zero) being filled for the preceding model milestone year. If that year is 2019, the resulting tax will be zero in 2019, and it is then interpolated from that zero value in 2019 to the value 0.001 in 2024. If you want the tax to be strictly zero until 2024, you should just define a zero value for 2024, instead of 0.001.

Concerning the CO2 emissions showing a reduction trend from 2019, please also recall that a TIMES model is by default solved with perfect foresight, where policies implemented in the future are assumed to be known by the decision-makers and may thus affect investments also in earlier years.

However, 2019 is a historical year, and therefore you should not need any investments into new capacity in that period. You can model all the capacities that were existing in 2019 with past investments or residual capacities, and therefore you can disable any new investments in 2019.  Consequently, when properly modelled, you should not see any impact of the CO2 tax imposed in 2025 on the power sector investments in 2019.  And neither should that tax affect the operating decisions of power plants in the period 2019, if the tax remains zero in that period. Therefore, you should not see any impact on emissions in 2019.

However, if deemed useful, you can also disable the impact of any tax imposed in 2025 or later on any earlier investments or operation, by running the model first without the new policy, and then by fixing all the historical model periods to that "BAU" solution, when running the model with any new policies. VEDA/TIMES does indeed support an easy way of fixing the first periods to a previous solution.
     Thanks for your reply. It is useful for me.
Zhi GUO
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)