My TIAM model has an excel file for each region (16) and for each sector (5) so in total 80 files. So I wanted to reduce the industrial files just to one. I started by creating a new file just with two regions to observe if the file works, so it did, the model turned well. Then I continued to add all the other regions, and after doing that and turning the model I received error 172 (element is redefined) for commodities (you can find the lst file in this link: https://drive.google.com/drive/folders/1...share_link as it is too heavy to be uploaded here).
In this sense, I would like to know why this is happening, and if you can help me to solve the issue.
Thank you very much.
(11-04-2023, 03:03 PM)AKanudia Wrote: Are you using Veda_FE or Veda2.0?
Can you upload the file that resulted in these errors?
I am using VEDA 2.0 version 2.6.1.1
The files that I modified are the syssettings and the one IND files (I archived the old IND files). The syssettings file is attached here, and the IND file you can find it in the following link (it is too heavy to be uploaded directly): https://drive.google.com/drive/folders/1...share_link
I tested with the files provided, and I can confirm the problem: Basically all topology entries were duplicated in the resulting Base.dd file! But why that is the case is unknown to me...
The rule in Veda_FE used to be that one region can not be a member of two super regions. We just took a quick look, and I think this requirement could be relaxed with a small change in the code.
We will make a trial version available to you (after some tests at our end).
Apologies for the delay. The assumption that one region will appear in only one super-region is rather deep in the code. However, we realized that you can model Industry as a SubRES to accomplish what you are trying to do.
The only thing to remember is that all regional data must come from the SubRES trans file. You cannot use regions in FI_T tables of SubRES files.
Feel free to seek clarifications on this suggestion.
(10-05-2023, 06:39 AM)AKanudia Wrote: Apologies for the delay. The assumption that one region will appear in only one super-region is rather deep in the code. However, we realized that you can model Industry as a SubRES to accomplish what you are trying to do.
The only thing to remember is that all regional data must come from the SubRES trans file. You cannot use regions in FI_T tables of SubRES files.
Feel free to seek clarifications on this suggestion.
Amit,
Thank you very much for your answer. I will proceed to apply your modeling recommendations, and I will keep you updated with the results.