Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Order of estimation on PS5 #34

Open
olivianatan opened this issue Feb 5, 2017 · 3 comments
Open

Order of estimation on PS5 #34

olivianatan opened this issue Feb 5, 2017 · 3 comments

Comments

@olivianatan
Copy link
Contributor

@rickecon -
Maybe I'm missing something, but I'm not sure why parts A and B of Q 1 aren't switched. We need to specify alpha to get our z_t series, so it makes sense to me to first estimate (alpha, beta), then estimate (rho, mu), since our results there vary by what we use for alpha - What am I missing?
Olivia

@bobaekang
Copy link
Contributor

@rickecon In addition to the question posed by @olivianatan, I am also wondering if we should assume the value for z_0 to be something to get a vector for z_{t-1}, just as we did in PS3. Is it different this time? Or should we just use a (99, 1) vector for each variable? Maybe I'm just not understanding how to approach this problem...

@rickecon
Copy link
Owner

rickecon commented Feb 7, 2017

@olivianatan and @bobaekang . You're right. Here is the correct way to estimate the Brock and Mirman (1972) model by GMM.

  1. Guess a values for alpha, beta, rho, and mu.
  2. Given alpha and the data r_t and k_t, you can use the first order condition of the firm for r_t to back out the series for z_t.
  3. Once you have z_t, you can compute the four moments listed in the problem set.
  4. Your GMM estimates for alpha, beta, rho, and mu are the ones that minimize the weighted sum of squared errors from those four moment conditions.

I will update the problem set question after class.

@rickecon
Copy link
Owner

rickecon commented Feb 7, 2017

I just pushed the changes to Exercise 1 in Problem Set 5.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants