Veda2.0 Released!


CUM Value
#1
Hi guys.

I have a question to using Cumulative values.

In our model we have these milestone years  ( 2018-2020-2025-2030-2035-2035-2040-2045-2050


"Tech1" has allocated free emission CO2_1 (ENV)  for (not CUMULATIVE years) 2018: 6 ktCO2 - 2019: 5.5 ktCO2 - 2020: 5.0 ktCO2 

(CUMULATIVE years2021-2025: 8.0 ktCO2 - 2025-2030: 7 ktCO2 - 2030-2035: 6.9 ktCO2 - 2035-2040: 4.5 ktCO2 - 2040-2045: 3.0 ktCO2 - 2045-2050: 2 ktCO2

Years 2018-2019-2020 are not cumulative values, 

How can be used attribute CUM for period  2021-2025- 8 kt CUM CO2
                                                             2025-2030- 7 kt CUM CO2
                                                             2030-2035- 6.9 kt CUM CO2
                                                             2035-2040- 4.5 kt CUM CO2
                                                             2040-2045- 3 kt CUM CO2
                                                             2045-2050- 2 kt CUM CO2

And what happend with years 2022-2023-2024-2025 and so on ?
Thanku very much.

Please see attached my CO2_Trading file


Attached Files
.xlsx   SubRES_CO2_Trading.xlsx (Size: 35.15 KB / Downloads: 4)
Reply
#2
You can use ACT_CUM for defining cumulative activity bounds for processes and FLO_CUM for cumulative flow bounds.  In VEDA, the default year range is BOH-EOH, and so to use any other range you must use the Year column. It seems you want to define such bounds for many overlapping 6-year ranges: 2025–2030, 2030–2035, 2035–2040, 2040–2045, 2045–2050. While technically ok, they seem a bit strange, especially as each of them overlaps two periods. However, I think using a scenario file for defining ACT_CUM / FLO_CUM with any non-default year ranges would be recommended.
Reply
#3
(09-04-2021, 03:21 PM)Antti-L Wrote: You can use ACT_CUM for defining cumulative activity bounds for processes and FLO_CUM for cumulative flow bounds.  In VEDA, the default year range is BOH-EOH, and so to use any other range you must use the Year column. It seems you want to define such bounds for many overlapping 6-year ranges: 2025–2030, 2030–2035, 2035–2040, 2040–2045, 2045–2050. While technically ok, they seem a bit strange, especially as each of them overlaps two periods. However, I think using a scenario file for defining ACT_CUM / FLO_CUM with any non-default year ranges would be recommended.

Hi Antti

Now i see in not good approach.

Do i have to define FLO_CUM ? What if only value i have will be 6 yrs-range value ?

CO2_1       CUM        Years    Flo_Cum
                8.4 kt       2021         ?
                               2022
                               2023
                               2024
                               2025
                7 kt          2026
                               2027
                               2028
                               2029
                               2030
Flo_Cum is up to me to define in that 5/6 yrs range ?

I created a table for CO2_1 emissions free allocation. What do you think is the better approach to solve this ? 
Thank you


Attached Files
.xlsx   CO2_Table.xlsx (Size: 35.56 KB / Downloads: 2)
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)