Veda2.0 Released!


Modifying Timeslice and sector definitions
#1
Good afternoon,
I'm quite new using VEDA, so probably you will think my questions are stupid.
My problem is I'm trying to improve a model already wirking and I'm having some problems.
I'd like to imcrease the time slices' number, but I have notce that it's impossible to do it without creating a new model.
When I create a new model it doesn't work.
Is it possible to modify the old model?? And furthermore, is it possible to create sectors once you have already create the model??
Thank you for your help
Maria
Reply
#2
Both the things you mention - modifying timeslices and sectors, are very much possible to do in a working model. All you need to do is to start the SYNC process from scratch after making such changes.
You can do this with the Start from scratch option under the Tools menu.
Apart from the two changes referred to here, changes in regional definition is the only other case when one needs to start from scratch. This is because with these changes, any of the previously processed information can potentially be invalid.
Reply
#3
Thanksssss!
You've been really usefull!
I have a new problem now maybe you know have to solve....
Once I have changed the TS while running the model it doesn't obtian an optimal solution. the LST archive sais that thereis a problem while assignent tha com_fr and there is something dividded by zero.
Can all the TS have the same length and the same demand load??
Tank you again
Reply
#4
I am glad you find this site useful.
The most likely cause is that that you have missed the G_YRFR declaration for one of the new timeslices.
Just filter all G_YRFR and COM_FR declarations in Browse and make sure that all the new slices are covered. There is no problem with having equal durations and/or load.
Reply
#5

I have checked many times in Browse the slices and there are all cover. Is there any where, where I could check where do I have the problem??

I have check the LST archive but I it's not really clear...
Thanks again!
Reply
#6
Send me the LST file and the following screenshots:
  1. The ~TimeSlices table in SysSettings file
  2. Browse screen with only G_YRFR selected (in Attributes list)
  3. Browse screen with only COM_FR selected (in Attributes list)

You can post these on the forum.

If this does not work, we will do a Gotomeeting. See www.gotomeeting.com. Where are you located? Please update a few key fields in your user profile.
Reply
#7
Maria Wrote:the LST archive sais that thereis a problem while assignent tha com_fr and there is something dividded by zero.

Maria: Could you post also the .LST file on the Forum, because I am interested to see what causes the assignment problem and divide by zero.  I could try to add some QA checks that would help the user correcting such modeling errors.

Thanks,
Antti
Reply
#8

Thank you so much. The model is now running, but with strong results. I think my problem was that the model I was using is old, and had strange headings. so there was a problem of comunication between VEDA and GAMS.

Any way, if you want I can't post you later the files.
Thanks again.
María
Reply
#9

Good morning,

sorry for bothering you again but I'm getting crazy. After solving my problems with the slices i discovered new ones. Although before changing them it was running prefectly, If a technolgy has capital cost associated the model doesn't rum. It sais there is a problem with CRF, what I don't understand, because i have checked the browse as you recommended me and rate is not 0 and all the technologies have a life different from 0.
Furthurmore, this error I can solve just without associating invcost, when  I run the model it gets an optimal solution, but whem I open VEDA BE, don't work any tecnology.
I can't post the screenshoot of the LST file, but this is what it sais, all the errors it show are:
----  35761 Assignment CST_IREC      0.000     0.016 SECS      5 Mb      0
----  35768 Loop                     0.000     0.016 SECS      5 Mb
----  35781 Loop                     0.000     0.016 SECS      5 Mb
----  35815 Loop                     0.000     0.016 SECS      5 Mb
----  35882 Assignment CST_COME      0.000     0.016 SECS      5 Mb      0
----  35907 Assignment CST_COMC      0.000     0.016 SECS      5 Mb      0
----  35918 Assignment PAR_OBJSAL    0.000     0.016 SECS      5 Mb      0
----  35921 Assignment CST_SALV      0.000     0.016 SECS      5 Mb      0
----  35928 Assignment PAR_ACTL      0.000     0.016 SECS      5 Mb     23
**** Exec Error at line 35929: division by zero (0)
----  35929 Assignment PAR_ACTM      0.000     0.016 SECS      5 Mb    230
----  35934 Clear      RTP_CAPYR     0.000     0.016 SECS      5 Mb
----  35935 Assignment RTP_CAPYR     0.000     0.016 SECS      5 Mb      0
----  35936 Assignment VAR_CAP       0.000     0.016 SECS      5 Mb      0
----  35938 Assignment PAR_CAPL      0.000     0.016 SECS      5 Mb      0
----  35940 Assignment PAR_CAPM      0.000     0.016 SECS      5 Mb      0
----  35941 Assignment PAR_CAPLO     0.000     0.016 SECS      5 Mb      0
----  35942 Assignment PAR_CAPUP     0.000     0.016 SECS      5 Mb      0
----  35944 Assignment PAR_NCAPL     0.000     0.016 SECS      5 Mb      0
----  35945 Assignment PAR_NCAPM     0.000     0.016 SECS      5 Mb      0
----  35953 Assignment PAR_COMPRDL    0.000     0.016 SECS      5 Mb      0
----  35954 Assignment PAR_COMPRDM    0.000     0.016 SECS      5 Mb      0
----  35955 Assignment PAR_COMNETL    0.000     0.016 SECS      5 Mb      0
**** Exec Error at line 35956: division by zero (0)
----  35956 Assignment PAR_COMNETM    0.000     0.016 SECS      5 Mb     23
**** Exec Error at line 35959: division by zero (0)
----  35959 Assignment PAR_COMBALEM    0.000     0.016 SECS      5 Mb     23
**** Exec Error at line 35960: division by zero (0)
----  35960 Assignment PAR_COMBALGM    0.000     0.016 SECS      5 Mb    207
----  35961 Assignment PAR_PEAKM     0.000     0.016 SECS      5 Mb      0
----  35967 Clear      F_INOUT       0.000     0.016 SECS      5 Mb
----  35968 Assignment F_INOUT       0.000     0.016 SECS      5 Mb      0
----  35969 Assignment F_INOUT       0.000     0.016 SECS      5 Mb      0
Thanks again!!
Reply
#10
I think these errors are due to the discount rate G_DRATE not being defined. The discount rate must be positive, i.e. a zero discount rate cannot be used. Try defining some non-zero discount rate for your model, if it is still missing as I suspect.
Reply


Possibly Related Threads…
Thread Author Replies Views Last Post
  UC for specific timeslice zheng 1 1,356 26-06-2022, 09:39 PM
Last Post: Antti-L
  Transport sector speed guozhi1305 2 3,009 11-10-2021, 01:54 PM
Last Post: guozhi1305
  Where are the case definitions stored? kogexo 2 3,833 16-04-2020, 07:10 PM
Last Post: kogexo
  Storage modelling, timeslice resolution and G_CYCLE alro 11 14,628 13-05-2019, 04:26 PM
Last Post: Antti-L
  region definitions that are sector-specific Anna (AKR) 4 8,403 19-03-2019, 01:24 PM
Last Post: Anna (AKR)
  Electricity Sector Issues Tanzeel 0 3,605 09-02-2017, 10:50 PM
Last Post: Tanzeel
  Problems @ material sector Tjerk 4 10,637 21-10-2016, 07:04 PM
Last Post: Tjerk
  constrain storage out to be in adjacent timeslice cyang 6 12,976 31-08-2015, 04:53 AM
Last Post: Antti-L
  Allocate endogenous upstream emissions to a sector cyang 0 3,755 24-05-2012, 02:39 PM
Last Post: cyang

Forum Jump:


Users browsing this thread: 1 Guest(s)