05-03-2024, 09:36 PM
For a period of 1 year in 2020, we would expect the cumulative flow it to be [CPX(2019-2001) - CPX(2020-2001)]*OCOM, so (1-0.1)/(30-1)*1=0.03 in your example I guess.
Veda2.0 Released!
NCAP_CPX and NCAP_OCOM
|
05-03-2024, 09:36 PM
For a period of 1 year in 2020, we would expect the cumulative flow it to be [CPX(2019-2001) - CPX(2020-2001)]*OCOM, so (1-0.1)/(30-1)*1=0.03 in your example I guess.
06-03-2024, 01:01 AM
Ok, thanks, I get what you expect (although I was asking about cumulative flows over all periods). So, you expect the flows corresponding to all the implied retirements before the base year to be inaccessible (no material can be recovered).
06-03-2024, 02:43 PM
Yes, exactly ! The cumulative flow "lost" before the base year would be [1 - CPX(2019-2001)]*OCOM, while the cumulative flow over all periods after the base year would be [CPX(2019-2001) - 0]*OCOM
03-04-2024, 01:48 PM
It is now available in v4.8.0. As there was no design offered for the user "interface", it is now available when defining FLO_FUNCX(r,'0',p,'CAPFLO',com) = 3; In other words, just an IE option 3 for shaping the CAPFLO of com. In that case the NCAP_OCOM will be applied to the retired capacity in each period (as defined by NCAP_CPX) instead of to the whole capacity at the end of the lifetime. Moreover, NCAP_DLAG is also taken into account.
05-04-2024, 02:19 PM
Ok, great, thank you Antti for the update.
|
« Next Oldest | Next Newest »
|
Possibly Related Threads… | |||||
Thread | Author | Replies | Views | Last Post | |
About NCAP_OCOM | [email protected] | 1 | 302 |
28-03-2025, 06:50 PM Last Post: [email protected] |
|
Retirement profile for new technology: SHAPE & NCAP_CPX attributes | vahid.aryanpur | 3 | 3,813 |
12-01-2021, 06:02 PM Last Post: vahid.aryanpur |