Stata The Stata listserver
[Date Prev][Date Next][Thread Prev][Thread Next][Date index][Thread index]

st: GARCH estimation time issue

From   "gary tian" <[email protected]>
To   <[email protected]>
Subject   st: GARCH estimation time issue
Date   Thu, 2 Jun 2005 12:25:58 +1000

Dear Sir

I estimate GARCH model using intraday data about 30, 000 observations for 30
individual stocks.

When I use following estimation for one stock, the coefficients are same
with Eviews and Shazam but Stata need about 5 minutes and Eviews and Shazam
are bit of less time. However, it is ok.

arch r l.r, arch(1) garch(1) nolog

When I add volume in the variance equation to the following estimeation,

arch r l.r, het(vol) arch(1) garch(1) nolog

Stata need about 15 minutes and Eviews and Shazam are about 3 mintues. The
problem is that  the values of coefficients from Stata are very different
from those of Eviews and Shazam but significant levels are same. I check
Eviews I use Marquardt optimal algorithm. Ok, so I change to following
estimation of BFGS algorithm:

arch r l.r, het(vol) arch(1) garch(1) nolog bfgs

I wait to 45 minutes, it didn�t give me results, so I stop it.

Can you help to solve this problem? Because I really like Stata and do
everything. Thanks in advance.


-----Original Message-----
From: [email protected]
[mailto:[email protected]]
Sent: Thursday, 2 June 2005 11:56 AM

Received: by with SMTP id u4mr257731nzg;       Wed, 01 Jun 2005
	18:54:30 -0700 (PDT)
Received: by with HTTP; Wed, 1 Jun 2005 18:54:30 -0700 (PDT)
Message-ID: <[email protected]>
Date: Wed, 1 Jun 2005 21:54:30 -0400
From: Cody Knox <[email protected]>
To: [email protected]
Subject: st: HSHAZ iteration stopped at number 290.
Mime-Version: 1.0
Content-Type: text/plain;
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by
	id j521sZt04684
Sender: [email protected]
Reply-To: [email protected]
X-imss-version: 2.025
X-imss-result: Passed
X-imss-scores: Clean:2.00184 C:2 M:3 S:5 R:5
X-imss-settings: Baseline:3 C:2 M:2 S:2 R:1 (0.5000 0.5000)

Dear statalist,

I need your help.

I have been running HSHAZ for a large dataset with a number of
covariates. After going through 280 iterations, STATA (hshaz) showed
virtually the same log likelihood for about 10 iterations and then
stopped to move into the next iteration - what a disaster!

If it had sent an error message, I would have had no choice but to
give up. Bottom line is STATA is still running using most of the CPU
capacity - and about a day and a half has passed.

Does anyone have similar experience (and got it through and got the
estimated results later)? Any tips/help are welcome. - if I stop here,
I should run the program for another 20 days... please help me.


Cody Knox

*   For searches and help try:

*   For searches and help try:

© Copyright 1996–2024 StataCorp LLC   |   Terms of use   |   Privacy   |   Contact us   |   What's new   |   Site index