I am interested to know what is the best or most convenient way to have different sets of costs of renewables. One conservative and the other more optimistic. Since the costs of different technologies are included in the input files. I was wondering whether there are any methods or features in VEDA that I can use to import two sets of input for costs to avoid syncing all the input files every time I change the costs in the input.
I am interested to know what is the best or most convenient way to have different sets of costs of renewables. One conservative and the other more optimistic. Since the costs of different technologies are included in the input files. I was wondering whether there are any methods or features in VEDA that I can use to import two sets of input for costs to avoid syncing all the input files every time I change the costs in the input.
Thank you very much for your time!
I would use Regular scenarios with different sets of input costs. And every next RUN you only choose a sets of Costs you want in Run Manager by selecting a scenario.
I gues.
What you are trying to accomplish is Veda's raison d'etre. Well, one of the most important ones, at least.
I would do this via UPD tables in regular or parametric scenario files. One example is attached, where the costs are being scaled by simple multipliers across all years (and regions and techs). This can be made as specific as needed - for regions, techs and/or years.
Efficiency consideration: UPD tables slow things down if they are more than 10-15 rows. I would recommend INS/DINS tables if you want very specific alternate assumptions. You just need to remember that the original assumptions will apply for any combination of indexes that is not specified in such a scenario file.
Note also that in a Scenario file you can also filter out the old data on a time-series basis, by adding the column TS_Filter, and putting there 0/1. In this way the original assumptions will not apply even for combinations of indexes that are not specified in the scenario file. So, you can be sure the new time-series will fully override the old one.
(03-02-2021, 03:46 PM)Antti-L Wrote: Note also that in a Scenario file you can also filter out the old data on a time-series basis, by adding the column TS_Filter, and putting there 0/1. In this way the original assumptions will not apply even for combinations of indexes that are not specified in the scenario file. So, you can be sure the new time-series will fully override the old one.
Thank you! That's very helpful. I was wondering whether it can also be applied to efficiency, then which attribute should I use?
>I was wondering whether it can also be applied to efficiency, then which attribute should I use?
You mean TS_Filter? Sure, TS_Filter can be used for any time-series attribute in a TFM_INS/TFM_DINS table. All efficiency parameters (e.g. ACT_EFF, FLO_EFF, STG_EFF, ACT_FLO, PRC_ACTFLO, NCAP_BPME, NCAP_CDME, COM_IE, IRE_FLO, and in VEDA EFF, CEFF, INPUT, OUTPUT, VDA_FLOP), are TS attributes, and so it should not matter which one you use, as long as you specify TS_Filter for the efficiency parameter instance you want to be filtered out. If you just want to filter out a time-series without defining any new value(s), you could use Year=0 and value=0.
