I wish to use IRE_FLO_SUM to generate commodities that duplicate the electricity trade, with negative values for export and positive values for import. I am currently only succeeding to to so for the base year, and not for other model periods. See models files.
How do I make the IRE_FLO_SUM work for other years than base year? All help is highly appreciated!
I have previously done this successfully in ANSWER. Using IRE_FLOSUM is a the first step to model stochastic electricity trade prices.
Not clear where the problem is. Regarding TIMES, defining IRE_FLOSUM for other years than base year is no different. And in VEDA you can define the Year in all tables. But in VEDA2 the index positions have for some reason been changed compared to VEDA1, such that the source commodity is now the commodity and Other_indexes should have IE,IO,com2.
You said "See models files." What files do you mean?
08-02-2021, 06:23 PM (This post was last modified: 08-02-2021, 06:24 PM by Antti-L.)
You have defined interpolation options -1 and 1 for many of the IRE_FLOSUM, including those shown in your results in the picture. Why is that so? These options prevent the extrapolation of the values to other years.
The easy solution would thus be to remove the I/E option because IRE_FLOSUM is by default fully inter-/extrapolated. However, it is not clear to me why you define those I/E options -1 and 1 for them in the first place. Maybe there is a good reason?
It was not my intention and there is no good reason to define these strange interpolation rules. Thank you very much for pointing it out. I have now changes "AllRegions" to "ValField" and it seems to work.
(09-02-2021, 02:30 AM)Pernille.S Wrote: I have now changes "AllRegions" to "ValField" and it seems to work.
Thanks Pernille. I tried to search the Forum and the VEDA documentation for "ValField" but could not find any information. Can you or @Amit give some more info: When would using "ValField" be necessary for some data table or individual parameter to work properly in VEDA2.0? Until now, IRE_FLOSUM has worked well for me, even with using AllRegions. But it seems this may not always be the case?
Dear Antti, I must admit that it was based on a bit trial and error that made think about this solution. I therefore think @Amit is the best to give more information about this.
As per Information - Veda tags, the following col headers can be used for the value dimension in INS (and several other) tables: value, valfield, val_field, allregions.
If changing allregions to valfield is making a difference in some case, please create an example in a demo model.
