Veda2.0 Released!


any way to set lower AF for 1st time period?
#1
Hi,

I'm looking to see if there is a way to lower the AF parameter for processes in the 1st time period that they are built.  I.e. if you were to build a power plant, the normal operating AF might be 80% but in the first time period, because of construction and other startup factors, the AF might only be 50%.  This would be linked to the first year that they are built, and not the first year that they are available. 

thanks,

Chris
Reply
#2
Yes, there is a way for doing that.

TIMES supports age-dependent AF factors.  First define the SHAPE parameter (the relative level of the availability, by the age of the plant).  Then define NCAP_AFX for the process, which specifies the shape index to be used, and you are done. The actual availability factor at age N will be the NCAP_AF multiplied by the SHAPE index for the age N.

You don't even need to define the process vintaged in order to use this feature, because the availability factors are capacity-related attributes (the VAR_NCAP variables are always vintaged in TIMES).

[EDIT:] After taking a quick look at the documentation, it seems that the documentation fails to mention the important fact that the shape index 1 is reserved for a constant shape of 1. So, it might be useful to note that the range of the available shape indexes for the user to define is from 2 to 100.

Reply
#3
Hi Antti,

Thanks for the reply.  I'm glad to hear that that age dependent AF factors exist.  I've looked through the VEDA documentation but do not see where/how to define the SHAPE parameter.  Can you explain to me how to do this?

Once I've specified this SHAPE function, it looks like that for a given process in the process description, I just make a column for NCAP_AFX, which specifies the shape that I'm interested in.  If I have only one SHAPE function, NCAP_AFX would simply be 2 for each relevant process?

thanks!

Chris
Reply
#4
See if the following example (related to the DEMO model) helps.



You don't need to define any interpolation option for SHAPE; it is always inter-/extrapolated.
But for NCAP_AFX, the default option is 10, and so you might want to use some other option (e.g. 5 as in the example).
Reply
#5
Thank you Antti, your example was very helpful for me to figure out how to incorporate this feature into my model.  I think it is working well and I greatly appreciate your help.

Chris
Reply


Possibly Related Threads…
Thread Author Replies Views Last Post
  time variant emission coefficient dgchoi 5 13,041 26-06-2023, 04:09 PM
Last Post: Antti-L
  SHARE-I/O for all process and all time horizon ejin 7 4,320 08-03-2023, 10:55 AM
Last Post: AKanudia
  Solar lower costs impact capacity constraints LucasD 10 10,027 18-12-2020, 03:04 PM
Last Post: AKanudia
  Non-optimal results when 'fixed result to x period' lppnog 1 2,856 30-11-2020, 09:26 PM
Last Post: Antti-L
  Problems to sync a small model with 8736 time-slices Pernille.S 21 38,340 28-05-2020, 12:01 AM
Last Post: AKanudia
  Time stepped algorithm -demand projection canismajoris 7 8,866 18-05-2020, 08:39 PM
Last Post: Antti-L
  Tips for reducing syncing time of SysSettings? Pernille.S 2 5,466 14-11-2019, 02:19 PM
Last Post: Pernille.S
  Very long sync time kogexo 10 16,556 30-10-2019, 07:57 PM
Last Post: kogexo
  auxiliary input of time commodity ignored Anita Prajapati 5 8,985 25-10-2019, 07:42 PM
Last Post: Anita Prajapati
  Synchronising takes too long time MohammedAbiAfthab 4 8,697 10-06-2019, 02:35 PM
Last Post: MohammedAbiAfthab

Forum Jump:


Users browsing this thread: 1 Guest(s)