Posts: 28
Threads: 7
Likes Received: 0 in 0 posts
Likes Given: 0
Joined: Dec 2019
Dear all,
I have some trouble using the Results tab. I am running a scenario in which I am using PRC_RESID to assign existing capacities of trade processes. My run seems to have worked and the values I found for these trade processes look fine in the results tab. The problem is that when comparing these values with the values of the VD file, I get something different.
I do have troubles importing the results into veda BE because the model is large. It is then a little difficult to tell if the import of results in VEDA2.0.
Do you have any idea of what I did wrong?
Thank you in advance for your help!
Mahmoud
Posts: 1,057
Threads: 41
Likes Received:
18 in 15 posts
Likes Given: 23
Joined: May 2010
Reputation:
18
need more information: send screen shots of what you see in the VD file and the results tab. One likely cause of confusion is the region dimension on trade processes. Make sure you have it in the rows of your data view.
Posts: 28
Threads: 7
Likes Received: 0 in 0 posts
Likes Given: 0
Joined: Dec 2019
Posts: 1,057
Threads: 41
Likes Received:
18 in 15 posts
Likes Given: 23
Joined: May 2010
Reputation:
18
1. are you sure that there is only one scenario you are looking at in results?
2. confirm that the VD file in Results is the same as the VD file you imported in R. The latest version will show you the timestamp and path of the VD file when you hover on scenario name.
Posts: 1,057
Threads: 41
Likes Received:
18 in 15 posts
Likes Given: 23
Joined: May 2010
Reputation:
18
And are you solving the model without crossover?
Posts: 1,956
Threads: 26
Likes Received: 55 in 47 posts
Likes Given: 15
Joined: Jun 2010
23-09-2020, 02:45 PM
(This post was last modified: 23-09-2020, 03:22 PM by Antti-L.)
You say: "The problem is that the vd file does not report any values for the processes for which PRC_RESID is imposed and only reports values for those without PRC_RESID values in input. "
The attributes in the vd file are created by TIMES. If what you say is true (the vd file does not report any Var_CAP values for processes for which PRC_RESID is imposed), it would seem to imply that there is a bug in TIMES or in the GAMS GDX2VEDA utility. If that's what you are saying, it would be good to have a reproducible case. However, if your statement is based on the results from processing the vd file with R, you could also have a problem in that processing. Note that the PRC_RESID capacities should have zero as the vintage index in Var_Cap.
But I don't actually see why the values would be doubled in the Results... I am not seeing such myself, for any bilateral trade processes.
Posts: 28
Threads: 7
Likes Received: 0 in 0 posts
Likes Given: 0
Joined: Dec 2019
@Amit :
1) Yes I was looking at one scenario. I reproduced the situation on a demo model and I got the same value for VAR_Cap in the results tab as the PRC_RESID values imposed.
@Amit @Antti
2) indeed, I was having a problem with my script. As in old Veda, the VD file don't have any dat index (VD_MMDD) I was importing old studies and not the the last runs. My bad. I am sorry for this. Now there is no difference between the imposed values and the those I get from importing the vd files in R. The only difference is with the result tab but I will try to fix this and keep you updated.
@Amit :
3) Yes, I am running the model without crossover (It's way more faster). I Think that's why I get non zero values that should be zero if I run with crossover. By the way, I don't know if there is way to run the model without crossover and still eliminate very small values that should not show up in the results ?
Thank you both for your help and sorry for the delay !
Best regards,
Mahmoud
Posts: 28
Threads: 7
Likes Received: 0 in 0 posts
Likes Given: 0
Joined: Dec 2019
30-09-2020, 09:32 PM
(This post was last modified: 01-10-2020, 03:34 PM by canismajoris.
Edit Reason: Faults in the text.
)
Update :
I had v145 installed. I could not see the timestamp and path of the VD file when hovering on scenario name in the result tab. I guess that I missed something in the installation process. I have just installed v161 of Veda2.0. Things are working well again :
- I can see the timestamp and path of the VD file when hovering on scenario name in the result tab.
- I have the same results when comparing to my post-processing script.
Thanks again.