Download the latest version of VEDA-FE (45828) and VEDA-BE (492014)

Veda Application Installation guide


How to set emission factor for each year of a specific process during its lifetime?
#1
Hello, everyone!
In VEDA-FE, for example, a process with lifetime of 10 years starts to operate in 2010, and we can set the emission factor for 2011-2020. But when there is another process that can be used in any year during 2020-2050, how can we set the value of emission factor for each year during its lifetime, as we don't know the exact time that the model will choose to use this process? Thanks in advance for any help and attention!

Best,
XW
Reply
#2
I don't see the problem, but maybe I am missing something.

If the emission factor is constant, you can just define a single value for any convenient year, and TIMES will use that value for the emission factor over the process lifetime.

If the emission factor is a function of time (e.g. according to changes in standards), you can define the values at multiple years, and TIMES will interpolate and extrapolate the time-series over all model years, and will use the corresponding values for the process, whenever it will operate.  If the process is not vintaged, the emission factor will change over the lifetime of each vintage, according to the defined trajectory. However, if the process is vintaged, the factor will be constant over the lifetime of each vintage (equal to the value in the commissioning year).

Only if the emission factor is a function of the operating age of the process, or if the process is vintaged and you want the emission factor to be changing over its lifetime, you would need a more complicated set-up. Let me know if that is the issue.
Reply
#3
(23-02-2017, 09:39 PM)Antti-L Wrote: I don't see the problem, but maybe I am missing something.

If the emission factor is constant, you can just define a single value for any convenient year, and TIMES will use that value for the emission factor over the process lifetime.

If the emission factor is a function of time (e.g. according to changes in standards), you can define the values at multiple years, and TIMES will interpolate and extrapolate the time-series over all model years, and will use the corresponding values for the process, whenever it will operate.  If the process is not vintaged, the emission factor will change over the lifetime of each vintage, according to the defined trajectory. However, if the process is vintaged, the factor will be constant over the lifetime of each vintage (equal to the value in the commissioning year).

Only if the emission factor is a function of the operating age of the process, or if the process is vintaged and you want the emission factor to be changing over its lifetime, you would need a more complicated set-up. Let me know if that is the issue.


Thank you, Antti~
So sorry that I didn't to describe the problem correctly. And it's exactly the issue you mentioned, the emission factor is a function of the operating age of the process, that I'm trying to handle.  For example, the lifetime of process A is 10 years, and the emission factor is different for each year over its lifetime.
Reply
#4
OK, then you need to shape the emission factor.  

Shaping a flow attribute, such as an emission factor, is only possible for vintaged processes, because only in that case the flow variables are vintage-specific. Shaping an attribute involves defining the base development of the attribute for the process, a generic SHAPE index, and an attribute linking a SHAPE index to the process-specific attribute. A (random) example is given below, for the CH4 emissions from the OILDST input of the process EGASOIL005 in the DEMO model:

[Image: attachment.php?aid=234]

In the example, the base development of the emission factor is defined by the FLO_EMIS(OILDST,CH4)=10 attribute. Note that if a time-series is defined, the base coefficient will be vintage-dependent. Then a shape index SHAPE(index,age) is defined, according to the desired change in the attribute value, by age. The age is specified in the Year column, and the index number in the Other_indexes column. Finally, that SHAPE index is applied to the FLO_EMIS() coefficient by specifying FLO_FUNCX(r,y,p,com,com)=index.
You don't need to define any interpolation option for SHAPE; it is always inter-/extrapolated.  But for FLO_FUNCX, the default option is 10, and so you might want to use some other option (e.g. 5 as in the example).

Note that the SHAPE index 1 is reserved for a constant shape of 1.


Attached Files Thumbnail(s)
   
Reply
#5
(24-02-2017, 09:49 PM)Antti-L Wrote: OK, then you need to shape the emission factor.  

Shaping a flow attribute, such as an emission factor, is only possible for vintaged processes, because only in that case the flow variables are vintage-specific. Shaping an attribute involves defining the base development of the attribute for the process, a generic SHAPE index, and an attribute linking a SHAPE index to the process-specific attribute. A (random) example is given below, for the CH4 emissions from the OILDST input of the process EGASOIL005 in the DEMO model:

[Image: attachment.php?aid=234]

In the example, the base development of the emission factor is defined by the FLO_EMIS(OILDST,CH4)=10 attribute. Note that if a time-series is defined, the base coefficient will be vintage-dependent. Then a shape index SHAPE(index,age) is defined, according to the desired change in the attribute value, by age. The age is specified in the Year column, and the index number in the Other_indexes column. Finally, that SHAPE index is applied to the FLO_EMIS() coefficient by specifying FLO_FUNCX(r,y,p,com,com)=index.
You don't need to define any interpolation option for SHAPE; it is always inter-/extrapolated.  But for FLO_FUNCX, the default option is 10, and so you might want to use some other option (e.g. 5 as in the example).

Note that the SHAPE index 1 is reserved for a constant shape of 1.


Thank you, Antti!
This perfectly solves the problem that I'm confronting with now!
Reply
#6
(24-02-2017, 09:49 PM)Antti-L Wrote: OK, then you need to shape the emission factor.  

Shaping a flow attribute, such as an emission factor, is only possible for vintaged processes, because only in that case the flow variables are vintage-specific. Shaping an attribute involves defining the base development of the attribute for the process, a generic SHAPE index, and an attribute linking a SHAPE index to the process-specific attribute. A (random) example is given below, for the CH4 emissions from the OILDST input of the process EGASOIL005 in the DEMO model:

[Image: attachment.php?aid=234]

In the example, the base development of the emission factor is defined by the FLO_EMIS(OILDST,CH4)=10 attribute. Note that if a time-series is defined, the base coefficient will be vintage-dependent. Then a shape index SHAPE(index,age) is defined, according to the desired change in the attribute value, by age. The age is specified in the Year column, and the index number in the Other_indexes column. Finally, that SHAPE index is applied to the FLO_EMIS() coefficient by specifying FLO_FUNCX(r,y,p,com,com)=index.
You don't need to define any interpolation option for SHAPE; it is always inter-/extrapolated.  But for FLO_FUNCX, the default option is 10, and so you might want to use some other option (e.g. 5 as in the example).

Note that the SHAPE index 1 is reserved for a constant shape of 1.

Dear Antti,I am also trying to set some age-based emission factors. I tried your example on the demo model. The table is copied exactly as yours:
   
And I also turn on the vintage option for the process EGASOIL005:
   
But I always got an error like that:
   
I have succeeded in introducing an age-based FIXOM cost use the SHAPE attribute like this example. But I have been struggling with the age-based emission coefficient for days. Could you please help me to figure out what is wrong with my setting?
Reply
#7
But what are those errors?  
Can you not post the listing file *.LST from that run where you get these errors, to see what they are?
The listing file is in the Work folder (see the Case manager, box "GAMS Work folder"). Please zip-compress it before uploading.
Reply
#8
(21-04-2019, 12:24 AM)Antti-L Wrote: But what are those errors?  
Can you not post the listing file *.LST from that run where you get these errors, to see what they are?
The listing file is in the Work folder (see the Case manager, box "GAMS Work folder"). Please zip-compress it before uploading.


The *.LST file is attached, Thanks a lot!

.zip   LST.zip (Size: 2.08 KB / Downloads: 1)
Reply
#9
Ok, the errors appear to be like this:

Code:
5650  ROW.2010.EGASOIL005._CommGrp_MISSING.CH4.ANNUAL 10
****                      $338           $170

Thus, VEDA is not getting the source group from Other_Indexes.

This could be because VEDA thinks that they should be numbers... I am not sure, I am not a VEDA expert.

You could try adding a new line below the headers, with a star (*) in the Attribute column, and text in all other columns but 123 in the AllRegions column (see attached picture).  But if that doesn't help, ask the VEDA people for help with these errors.


Attached Files Thumbnail(s)
   
Reply
#10
(21-04-2019, 07:06 PM)Antti-L Wrote: Ok, the errors appear to be like this:

Code:
5650  ROW.2010.EGASOIL005._CommGrp_MISSING.CH4.ANNUAL 10
****                      $338           $170

Thus, VEDA is not getting the source group from Other_Indexes.

This could be because VEDA thinks that they should be numbers... I am not sure, I am not a VEDA expert.

You could try adding a new line below the headers, with a star (*) in the Attribute column, and text in all other columns but 123 in the AllRegions column (see attached picture).  But if that doesn't help, ask the VEDA people for help with these errors.

Thanks a lot, Adding a new line did not work for me. but I solve the problem by putting these settings in three different TFM~INS tables.(The setting of shape in one, the setting of FLO_EMIS in one, and the setting of FLO_FUNCX in one). Thanks a lot for helping me in even the weekend.  Heart
Reply


Forum Jump:


Users browsing this thread: 2 Guest(s)