We have developed some time series (ARIMA) and smoothing models (Holt-Winters) that forecast monthly air traffic revenues. These flows are quite large on a daily basis, with monthly aggregates being accordingly even larger.
These models seem to work very well on a quarterly and annual basis. When using monthly forecasts, however, we get issues with February. The extra few days the other months have make a huge difference in terms of $ received.
It seems that the first February forecast after the end of historical data always has very large growth when comparing to February of the previous year. This settles down in the following February forecasts. Obviously this is masked in quarterly and annual forecasts. It does make some sense for the ARIMA models, which use AR components from months that have a few days more than January and other months. Holt-Winters is also affected by this, especially in the level component.
So the question I have is should every February be adjusted for this discrepancy, or does EViews somehow account for the number of days in a month when doing a monthly forecast? It seems to me that if these methods will "bleed" growth from other months into February that never would have existed due to the shorter number of days, a February adjusted is needed given the large amount of flows. If such an adjustment is necessary, can you advise on an acceptable method? One I can see is simply normalizing the forecast base on days. For example, the average number of days in a month is 365/12=30.42 days. Now if February's forecast is too high, would we take forecast*(28days/30.42days).
Any advice is great!
For econometric discussions not necessarily related to EViews.
1 post • Page 1 of 1
Who is online
Users browsing this forum: Google [Bot] and 2 guests