Download the latest version of VEDA-FE (45824) and VEDA-BE (492012)

Veda Application Installation guide


a running problem when running the front end
#1
Photo 
Hi everyone, i running the veda model for more than two years, and are quite similiar to this model. however recently, I had met a problem, and tried to sovle it, but failed. so I come here for help. here is the question. I add a new scenario into my model, this scenario use the growth rate parameter to simulate the growth of coal power plant, but it would go wrong once I use this scenario.( you could see the GAMS result attached) [img]file:///C:\Users\zxq\Documents\Tencent Files\376056639\Image\C2C\QP0FO[RHTB4K@J_%R3~}U40.png[/img]. for your better understanding, I also put the excel file here, who can help me to sovle it ,thank you very much.


Attached Files Thumbnail(s)
   

.xls   Scen_GROWTHRATE_COA_TEST.xls (Size: 71 KB / Downloads: 8)
Reply
#2
Tools - User Options - Import settings - Create Dummy - Variables for UCs

Reimport your UC scenario after activating this option. It will make the diagnosis easier.
Reply
#3
(23-08-2016, 10:33 AM)AKanudia Wrote: Tools - User Options - Import settings - Create Dummy - Variables for UCs

Reimport your UC scenario after activating this option. It will make the diagnosis easier.


thank u very much!  it works well and gets feasible result after activating the option.  Big Grin Big Grin Big Grin
Reply
#4
(23-08-2016, 10:33 AM)AKanudia Wrote: Tools - User Options - Import settings - Create Dummy - Variables for UCs

Reimport your UC scenario after activating this option. It will make the diagnosis easier.


hi, AKanudia. I had a new problem right now. could you help me solve it? thanks. here is the question:
I wrote a series of growth rates of different generation technologies with low bound and up bound. please the file attach.  after I SYNC the file, I checked the updated data by veda view(basci fuction-browse/exit-veda view), but I found that the data can not be read, why?


Attached Files Thumbnail(s)
   

.xls   Scen_Growthrate_BS.xls (Size: 104 KB / Downloads: 5)
Reply
#5
(23-08-2016, 12:00 PM)yu03 Wrote:
(23-08-2016, 10:33 AM)AKanudia Wrote: Tools - User Options - Import settings - Create Dummy - Variables for UCs

Reimport your UC scenario after activating this option. It will make the diagnosis easier.


thank u very much!  it works well and gets feasible result after activating the option.  Big Grin Big Grin Big Grin



This was only to help diagnosis... You should check the dummy imports (output of process IMPNRGZ) and adjust the UCs that are forcing dummy imports.
Reply
#6
(05-09-2016, 09:06 AM)yu03 Wrote: I wrote a series of growth rates of different generation technologies with low bound and up bound. please the file attach.  after I SYNC the file, I checked the updated data by veda view(basci fuction-browse/exit-veda view), but I found that the data can not be read, why?

I guess you might be looking at the Browse VEDA view, and you are not seeing the UC_NCAP PARAMETERS there? Is that the question?  
I suggest to Browse with the TIMES View instead. VEDA should be able to show them there, but perhaps not in the VEDA view...

BTW: Looking at the parameters you define, I wonder why you are specifying UC_RHSRTS(2015)=5 for all constraints?
UC_RHSRTS(0)=5 is the interpolation option, which is fine, but UC_RHSRTS(2015)=5 will define an RHS constant for the equation in all periods 2015,... with the value 5. If your capacity unit is GW, that would mean a 5 GW extra constant in all of your growth constraints.
Reply
#7
(05-09-2016, 02:13 PM)Antti-L Wrote:
(05-09-2016, 09:06 AM)yu03 Wrote: I wrote a series of growth rates of different generation technologies with low bound and up bound. please the file attach.  after I SYNC the file, I checked the updated data by veda view(basci fuction-browse/exit-veda view), but I found that the data can not be read, why?

I guess you might be looking at the Browse VEDA view, and you are not seeing the UC_NCAP PARAMETERS there? Is that the question?  
I suggest to Browse with the TIMES View instead. VEDA should be able to show them there, but perhaps not in the VEDA view...

BTW: Looking at the parameters you define, I wonder why you are specifying UC_RHSRTS(2015)=5 for all constraints?
UC_RHSRTS(0)=5 is the interpolation option, which is fine, but UC_RHSRTS(2015)=5 will define an RHS constant for the equation in all periods 2015,... with the value 5. If your capacity unit is GW, that would mean a 5 GW extra constant in all of your growth constraints.


Hi, Antti. thanks for your prompt reply. here I explain why I set these serises data. I wanted to predict the future development of power sector. before I used the index of growth rate, the stock limit of different type of power technologies were used. but I thought stock limit would constraint the advantage of TIMES model, so I turned my mind to use growth rate. however, I am not fimiliar with the setting of growth rate, espeicially the meanning of RHS. do you mean I need to delete the UC-RHSRTS columm?  I had no idea about how to use the RHS. could you send me some materials about it, thanks very much,   Heart  
AND,  could you help me  correct the growth rate document? what I want to achieve is  the following goals.  the New capacity growth rate of one specific power technology should be between the low bound and  up bound.
Reply
#8
(05-09-2016, 01:05 PM)AKanudia Wrote:
(23-08-2016, 12:00 PM)yu03 Wrote:
(23-08-2016, 10:33 AM)AKanudia Wrote: Tools - User Options - Import settings - Create Dummy - Variables for UCs

Reimport your UC scenario after activating this option. It will make the diagnosis easier.


thank u very much!  it works well and gets feasible result after activating the option.  Big Grin Big Grin Big Grin



This was only to help diagnosis... You should check the dummy imports (output of process IMPNRGZ) and adjust the UCs that are forcing dummy imports.


Thanks, AKanudia, I will check the dummy imports after doing the steps that following what Annti said.  thank you again.
Reply
#9
The UC_* parameters have been explained in the documentation. See: http://iea-etsap.org/index.php/documentation

For example, your UC_GrowthOfcoa_LO constraint for 2015 is formulated as shown below (where p is the set of coal processes):

∑p VAR_NCAP(t)  ∑p VAR_NCAP(t–1)*UC_NCAP(t–1)^(M(t)M(t1)) + UC_RHSRTS(t)

Assuming that 2010 is the preceding period, this translates into:
∑p VAR_NCAP(2015)  ∑p VAR_NCAP(2010)*1.077284 + 5

The question is, whether you really want to add the constant 5 into the constraint.  If not, specify a zero UC_RHSRTS instead of 5 (do not remove the column, but enter zero into it).
Another question is whether you really want to constraint the growth in the new capacity variable VAR_NCAP.
I would think constraining the VAR_CAP variable might be more reasonable, especially as both 2010 and 2015 are history years, and will thus probably not have any VAR_NCAP at all. 
And maybe your growth constraints should actually start at 2020 instead of 2015?
Reply
#10
(05-09-2016, 04:56 PM)Antti-L Wrote: The UC_* parameters have been explained in the documentation. See: http://iea-etsap.org/index.php/documentation

For example, your UC_GrowthOfcoa_LO constraint for 2015 is formulated as shown below (where p is the set of coal processes):

∑p VAR_NCAP(t)  ∑p VAR_NCAP(t–1)*UC_NCAP(t–1)^(M(t)M(t1)) + UC_RHSRTS(t)

Assuming that 2010 is the preceding period, this translates into:
∑p VAR_NCAP(2015)  ∑p VAR_NCAP(2010)*1.077284 + 5

The question is, whether you really want to add the constant 5 into the constraint.  If not, specify a zero UC_RHSRTS instead of 5 (do not remove the column, but enter zero into it).
Another question is whether you really want to constraint the growth in the new capacity variable VAR_NCAP.
I would think constraining the VAR_CAP variable might be more reasonable, especially as both 2010 and 2015 are history years, and will thus probably not have any VAR_NCAP at all. 
And maybe your growth constraints should actually start at 2020 instead of 2015?

Hi, annti, thanks you a lot. I will change the setting according to what you suggest. BTW, in your reply, "*1.077284" is "^1.077284",right? and how this number (1.077284) come?
Reply
#11
Shy  No, it is "*1.077284".  It came from 1.015^5 = 1.077284.  The exponent 5 came from M(t)–M(t–1) = 2015–2010.
Reply
#12
(05-09-2016, 07:25 PM)Antti-L Wrote: Shy  No, it is "*1.077284".  It came from 1.015^5 = 1.077284.  The exponent 5 came from M(t)–M(t–1) = 2015–2010.


got it!thanks a lot. I try it.  Big Grin
Reply
#13
(05-09-2016, 07:25 PM)Antti-L Wrote: Shy  No, it is "*1.077284".  It came from 1.015^5 = 1.077284.  The exponent 5 came from M(t)–M(t–1) = 2015–2010.


Hi Antti. As you said, I changed the NCAP into CAP, remove 2015 data. set UC_RHSRTS(time=2020~50)=0. after I sync these changes into the model, I check them through TIMES view. it only show the UC_RHSRTS value, not the UC_CAP~LHS value or UC_CAP~RHS value. why this? 
AND, I upload the document of growth scenario, could you give some further advice to improve this? thanks very much!


Attached Files Thumbnail(s)
   

.xls   Scen_Growthrate_BS.xls (Size: 126.5 KB / Downloads: 5)
Reply
#14
Hmm... I don't know why they don't show up.  They do show up when I import the constraints for the coal plants into the DEMO model, see attached picture.
   
So, there must be still something wrong in your set-up, for example maybe ELC should read ELCC in your model, or some simple mistake like that (just for one long shot Blush ).

Note also that your constraint name for coal-UP is wrong (it is the same as for nuclear).  Good luck!
Reply
#15
I think it is not setting mistake. because the UC-CAP can not show up in the TIMES view in my model. when I put the growth rate document into the demo, the UC-CAP can show up. so I need to do some to make the UC-CAP show up.
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)