+- IEA-ETSAP Forum (https://iea-etsap.org/forum)
+-- Forum: Model Generators (https://iea-etsap.org/forum/forumdisplay.php?fid=2)
+--- Forum: TIMES (https://iea-etsap.org/forum/forumdisplay.php?fid=8)
+--- Thread: The constraints of 2015 still work in 2020 (/showthread.php?tid=206)
The constraints of 2015 still work in 2020 - q-z17 - 21-02-2022
Hello Dr. Antti, I set constraints on 2015 to fix the flo_share in final energy and the NCAP_AF in electrity plants process. The values on 2015 and 2020 are different and shows correct in the "item details " of Veda2 software. But when I check the results, the constraints of 2015 still work in 2020. For example, the share of final energy in 2020 follow the value which I set for 2015. This make me confuse and I try some different I/E value like 0, 3, 5 but doesn't work. Could you please tell me where might go wrong ? Regards Qiang Zhang
RE: The constraints of 2015 still work in 2020 - Antti-L - 22-02-2022
If you are fixing input shares by FLO_SHAR(FX), please use interpolation option 1. And similarly if you use NCAP_AFA(FX) (or NCAP_AF(FX)). They have worked well for me. But you should also recall that FLO_SHAR and NCAP_AF are vintage-dependent, and so it is preferable to use NCAP_AFA if you want to fix the capacity factors only in the Base year, because NCAP_AFA is never vintaged. If necessary, with user-constraints you can always define non-vintaged constraints for a single year. If you need more help, please show the technology parameters (from VEDA2 Item Details) to see how you are defining your share constraints, and tell also whether the process/processes are vintaged or not.
RE: The constraints of 2015 still work in 2020 - q-z17 - 23-02-2022
(22-02-2022, 12:11 AM)Antti-L Wrote: If you are fixing input shares by FLO_SHAR(FX), please use interpolation option 1. And similarly if you use NCAP_AFA(FX) (or NCAP_AF(FX)). They have worked well for me. But you should also recall that FLO_SHAR and NCAP_AF are vintage-dependent, and so it is preferable to use NCAP_AFA if you want to fix the capacity factors only in the Base year, because NCAP_AFA is never vintaged. If necessary, with user-constraints you can always define non-vintaged constraints for a single year. If you need more help, please show the technology parameters (from VEDA2 Item Details) to see how you are defining your share constraints, and tell also whether the process/processes are vintaged or not.Thank you Dr. Antti-L. Following your suggestion, I found that the processes are vintaged. I am trying to fix it.