I have specific share-I and share-O for different technology processes, and assume the values are the same over all years. Currently I specify the share-I and share-O values for each process one by one period year. For example, in the ETHANE_cracking process, three inputs (Ethane, NG, and Elec) are used, and the share-I(~2020 until 2050) of each material are 80%, 10%, and 10%. I noticed that I can use extrapolation function with Year=0 and ALL region=3, but it asks me to specify the process and commodity name, and I have tons of processes and input/output commodities. Is there any easier way to define the share-I and share-O for all processes?
I have a feeling that you may not be using the rule-based approach of Veda to its full potential. You can share some of your large tables, if you want, and we will tell you if Veda can simplify things for you.
I have a feeling that you may not be using the rule-based approach of Veda to its full potential. You can share some of your large tables, if you want, and we will tell you if Veda can simplify things for you.
Hi Akanudia,
The source you suggested is what I looked at before, but I did the same as it has in the SysSettings, and it didn't work with saying that no records are read in that sheet. I just shared my tables and that would be great if you can find a solution for me.
This thread is under the VEDA Front End Sub-forum, so it maybe first confirm: Are you using VEDA-FE, and not VEDA2? The Demo_Adv_Veda example is for VEDA2.
Anyway, your shares are fixed (FX), and so you should of course add a row with LimType = FX, to get some records generated with that SysSettings table, which is indeed the easiest solution for you. Another solution would be to use columns with headers Share-I~0 and Share-O~0 in the FI_T table, and put the desired IE options there. With either method you could then remove all the redundant Share-I~YYYY and Share-O~YYYY columns.
(08-03-2023, 01:19 AM)Antti-L Wrote: This thread is under the VEDA Front End Sub-forum, so it maybe first confirm: Are you using VEDA-FE, and not VEDA2? The Demo_Adv_Veda example is for VEDA2.
Anyway, your shares are fixed (FX), and so you should of course add a row with LimType = FX, to get some records generated with that SysSettings table, which is indeed the easiest solution for you. Another solution would be to use columns with headers Share-I~0 and Share-O~0 in the FI_T table, and put the desired IE options there. With either method you could then remove all the redundant Share-I~YYYY and Share-O~YYYY columns.
Hi Antti,
Thanks for your reply. I am using VEDA2 but it's still saying no records are read in the TFM_MIG table in the SysSettings sheet. I tried Share-I~0 in the FI_T table and it works well for one output commodity (ethylene), however the other two output commodities have no results across the time horizon. Do you know why? Should I define a commodity group for all outputs?
(08-03-2023, 01:19 AM)Antti-L Wrote: This thread is under the VEDA Front End Sub-forum, so it maybe first confirm: Are you using VEDA-FE, and not VEDA2? The Demo_Adv_Veda example is for VEDA2.
Anyway, your shares are fixed (FX), and so you should of course add a row with LimType = FX, to get some records generated with that SysSettings table, which is indeed the easiest solution for you. Another solution would be to use columns with headers Share-I~0 and Share-O~0 in the FI_T table, and put the desired IE options there. With either method you could then remove all the redundant Share-I~YYYY and Share-O~YYYY columns.
Hi Antti,
Thanks for your reply. I am using VEDA2 but it's still saying no records are read in the TFM_MIG table in the SysSettings sheet. I tried Share-I~0 in the FI_T table and it works well for one output commodity (ethylene), however the other two output commodities have no results across the time horizon. Do you know why? Should I define a commodity group for all outputs?
Thanks,
Enze
Hi Antti,
I think I should keep the column of SHARE-I/O~2020, and then it is fixed, right?
08-03-2023, 04:23 AM (This post was last modified: 08-03-2023, 04:29 AM by Antti-L.)
Yes, of course you must leave one column for the share values, either SHARE-I/O (without any year) or e.g. SHARE-I/O~2020. I am not sure what you mean by fixed, though, but if you mean the LimType, then yes, default is FX.
I just tested myself with both methods, and they both worked fully as expected, by doing what I suggested. So, I have no idea why you conclude that the SysSettings method does not work, or that the FI_T method would not work.
No commodity groups are needed to be specified anywhere for either method to work.