Veda2.0 Released!


troubleshooting power price issues
#16
Ok, I looked at it once again, and it seems you are defining at least the NCAP_COST data with multiple currencies: In wepsruns_0003.dd you define them with USD10 until 2050 and in ADDDATA.gms you define them with USD20. Your costs will thus include both data until 2050, and thereafter only the ADDDATA.gms data. And NCAP_FOM seems to be in USD13+USD20? I think these would explain the price spikes around 2050, no?

I hope you understand this issue, apparently caused by using multiple currencies?  Such that if you define costs with multiple currencies for the same year indexes, your resulting costs will be the sum of the costs in different currencies, when converted to your target currency?  It is not a bug in TIMES, because one can use multiple currencies also in a meaningful way.  I think you should either filter out (TS_Filter) or update either set of cost data to zero under Veda, or you could also use a GAMS statement for removing the unwanted ones. Or you could put all the wepsruns_0003.dd cost data in another scenario, which is excluded from the run, when defining the costs with ADDDATA?

This is only my quick conclusion about it; I could also be wrong but it looks like you have a serious problem here.
Reply
#17
Rainbow 
I thought $ONEPS was set by default. I did add it at the beginning and ran on both my local machine and gams engine. the results were identical (with weird prices again [Image: sad.png]). I investigated the data I have in AddData.gms and it showed that NCAP_FOM was different between the suppxls and AddData --> No conflict is instigated by different gams license (sorry for not trying this before starting my thread). 


I have one other question: on how data is added to the model via AddData.gms: In veda, I only explicitly specify NCAP_COST and NCAP_FOM through 2050 and the model extrapolates these values through 2100. But my AddData.gms has values for NCAP_COST and NCAP_FOM explicitly through 2100. My understading is that AddData.gms overwrites values if they are already specified in the restart file and adds them if not found in it, is that right?
Reply
#18
No.  ADDDATA does not overwite the costs in your wepsruns_0003.dd scenario, because they are in a different currency!  Currency is an index of the cost parameters, and so they cannot be overwritten by another currency. Please see my post above.
Reply
#19
(14-07-2023, 10:35 PM)Antti-L Wrote: Ok, I looked at it once again, and it seems you are defining at least the NCAP_COST data with multiple currencies: In wepsruns_0003.dd you define them with USD10 until 2050 and in ADDDATA.gms you define them with USD20. Your costs will thus include both data until 2050, and thereafter only the ADDDATA.gms data. And NCAP_FOM seems to be in USD13+USD20?  I think these would explain the price spikes around 2050, no?

I hope you understand this issue, apparently caused by using multiple currencies?  Such that if you define costs with multiple currencies for the same year indexes, your resulting costs will be the sum of the costs in different currencies, when converted to your target currency?  It is not a bug in TIMES, because one can use multiple currencies also in a meaningful way.  I think you should either filter out (TS_Filter) or update either set of cost data to zero under Veda, or you could also use a GAMS statement for removing the unwanted ones. Or you could put all the wepsruns_0003.dd cost data in another scenario, which is excluded from the run, when defining the costs with ADDDATA?

This is only my quick conclusion about it; I could also be wrong but it looks like you have a serious problem here.
Oh I didn't see your reply as it was in page 2. Apologies. For some reason, I thought this might've happened. Thank you very much for going to the bottom of this, Antti. Mystery solved  Smile Smile Yaay!!!!

I also learnt a lot about the restart files, thanks to you!!! Many thanks
Reply
#20
(15-07-2023, 12:00 AM)Mahmoud Wrote: I thought $ONEPS was set by default.

No, OFFEPS is the default (just checked from GAMS online guide), and one should keep that in mind if creating input files outside VEDA.
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)