IEA-ETSAP Forum
Milestone Years-period length - Printable Version

+- IEA-ETSAP Forum (http://iea-etsap.org/forum)
+-- Forum: Model Generators (http://iea-etsap.org/forum/forumdisplay.php?fid=2)
+--- Forum: TIMES (http://iea-etsap.org/forum/forumdisplay.php?fid=8)
+--- Thread: Milestone Years-period length (/showthread.php?tid=64)



Milestone Years-period length - sld - 05-05-2014

Hi,

I have a question regarding the specification of Milestone Years.

I'd like to calibrate the model data in years 2001 and 2005, and then have results for 2010, 2020, 2030…etc, every 10 years, maybe up to 2100. For the time being I am working with the model until 2020 only.

So I am introducing Milestone Years: 2001, 2005, 2010, 2020… (I attach a picture form Answer, it's easier to understand what I am trying to explain).uploads/37/M.Y..jpg

My question refers to the Beginning and End of periods which include each Milestone Year.

For Year 2001, If possible, I'd like to have Beginning=End=Milestone Year (M.Y). I am working with Answer, and it doesn't let me do it because it doesn't respect any of the 3 methods detailed there (B and E halfway between M.Y. / B and E such that M.Y. at middle of B and E / User Specify B for First M.Y. and E for every M.Y). So the best I can do is force Answer to allow me to have 2 years in the first period. After doing that I input Beginning year of period 2, and the rest of the periods are defined. The first 4 periods (until 2020) are all different lengths. I don't really mind about it, I know the reporting values are average over the period.

So my question is, can I define the first period as just one year in Times? Can I do it in Answer? If I can't do it in Answer, does it look bad when reporting that the first period (calibration one) has 2 years (being strict my data is not average over 2 periods but just 2001 data)?

Is it bad practise to have the periods all of different lengths? To solve this, I could input different Milestone Years, but I just don't like how it looks reporting 2014, or 2022 compared to 2015/20.

Any comments are welcome

Thanks!




Milestone Years-period length - Antti-L - 05-05-2014

Using the third option "User specifies B for First Milestone Year...", I am not seeing the problem:


Using periods all of different lengths may cause some distortion in marginal costs when using the original standard TIMES formulation. But if you use the option $SET OBLONG YES, most of such distortions should be eliminated.




Milestone Years-period length - sld - 28-05-2014

Thank you, Antti.
Sorry for taking so long to respond, for some reason I didn't get the email saying you responded my question.
Thanks again!