Can GARCH(1,1) be applied to homoskedastic time series when comparing against heteroskedastic time series?

Can GARCH(1,1) be applied to homoskedastic time series when comparing against heteroskedastic time series?

Manage alerts

Loading saved threads...

Charlie · External communityPost link
External question — Cross Validated Stack Exchange Author: Charlie Original post: https://stats.stackexchange.com/questions/28321 License: CC BY-SA 3.0 — https://creativecommons.org/licenses/by-sa/3.0/ Adaptation: HTML converted to plain text; contact email addresses removed. I would like to compare a daily trade w.t.d. $index over the period of 10 years+ versus the shorter term (170 days) using GARCH(1,1) . The short term data derives from the 10 year+ data. The trouble is that the 10 year time series is heteroskedastic, whereas the shorter data is not. Can I apply GARCH(1,1) on the shorter term data as well even though it's not heteroskedastic (on the basis that it would be heteroskedastic if they were to be measured over a long period of time, and that the shorter period data derived from the longer period data)?
Quote
Report
StasK · External communityPost link
External answer — Cross Validated Stack Exchange Author: StasK Original post: https://stats.stackexchange.com/a/28371 License: CC BY-SA 3.0 — https://creativecommons.org/licenses/by-sa/3.0/ Adaptation: HTML converted to plain text; contact email addresses removed. If there is no heteroskedasticity in the "short" sample (or, in other words, the sample size of the "short" sample is insufficient to detect the heteroskedasticity), then it is the same as saying that the (heteroskedasticity) autoregression coefficients are equal to zero. This is the model nested in any (G)ARCH model, and thus your comparison becomes the comparison of the (G)ARCH coefficients "long" sample with zero (which, as you indicated, is rejected). If there are any mean/shift parameters, you can compare them straightforwardly, too.
Quote
Report
Ron · External communityPost link
External answer — Cross Validated Stack Exchange Author: Ron Original post: https://stats.stackexchange.com/a/28448 License: CC BY-SA 3.0 — https://creativecommons.org/licenses/by-sa/3.0/ Adaptation: HTML converted to plain text; contact email addresses removed. I am credulous that if there is no heteroskedasticity in the short series, you have not to use GARCH model to fit your data. If you want to convey the meaning that the short series have no heteroskedasticity, you can make a ARCH-LM test, which easily make on the statistics software like EViews, and get an answer that the long series have heteroskedasticity but the short one haven't. This process can get the answer you want.
Quote
Report
John · External communityPost link
External answer — Cross Validated Stack Exchange Author: John Original post: https://stats.stackexchange.com/a/34168 License: CC BY-SA 4.0 — https://creativecommons.org/licenses/by-sa/4.0/ Adaptation: HTML converted to plain text; contact email addresses removed. As StasK's answer mentions, a short-term GARCH-like volatility model can be embedded in a long-term forecast. A better comparison might be to compare a GARCH(1,1) model to an FIGARCH model. In the equity markets which you seem to be focusing on, the partial autocorrelation function tends to deteriorate slowly. This is indicative of a fractionally integrated volatility process. By contrast, a GARCH(1,1) process tends to have volatility quickly revert back to the mean. So it is possible that the GARCH(1,1) process is picking up a homoskedastic process when more data would reveal that volatility exhibits long-memory. It would be a mistake to remove this data from consideration. In addition, as a result of the different properties of the variety of volatility models, the time horizon is very important for volatility forecasts. For instance, a one-day ahead volatility forecast is going to be very similar to the estimate of today's volatility. However, a quarter or a year head volatility forecast might be substantially different.
Quote
Report

Post Reply

Checking account access…