[Date Prev][Date Next][Thread Prev][Thread Next][Date index][Thread index]

From |
Jeannette Wicks-Lim <[email protected]> |

To |
[email protected] |

Subject |
st: Re: Re: interpreting ipshin results |

Date |
Fri, 19 Nov 2004 10:49:20 -0500 |

Thanks for this very helpful reply.

Yes, I am starting to wonder whether the unit root test for the nominal minimum wage is sensible or not.

As far as I know, it is common to use nominal values of the minimum wages so I guess I've become accustomed to that. Also, I'm interested in how wages change because of how people perceive the change in the nominal value of the minimum wage and because I'm using a lagged value of the minimum wage change, I don't think that estimated effects would be equivalent to those when using real values.

Thanks very much for your help!

Jeannette

----- Original Message ----- From: "Kit Baum" <[email protected]>

To: <[email protected]>

Sent: Friday, November 19, 2004 9:31 AM

Subject: st: Re: interpreting ipshin results

First note that lngap is not the ratio of two variables; it is the difference of two variables. The fact that the difference of logs is the ratio of the unlogged variables is not relevant here. I agree, though, that the difference of two variables is also likely to contain a unit root if one of them does.

But a panel unit root test is in some sense a box score over units of the panel; in the case of ipshin, it is an averaging of the dickey-fuller values for your states' individual t-ratios. It would be easy enough, as Nick suggests, to look at those values individually, and see whether the null that they are all I(1) is sensible here. ipshin is flexible in allowing for variations in lag length, etc. and allowing a fraction of the units of the panel to be I(1) while others are I(0). But it would be interesting to see what you get from the individual states' tests of stationarity.

I really question whether it makes any sense to treat the (log of the) minimum wage as a random variable. It is a policy variable, and to my understanding is a step function. Most periods it does not change; some periods, the legislature responds to pressure and increases it by a substantial amount. In economic modelling terms, it is a jump process (and only positive jumps are allowed in the nominal minimum wage). Although one can certainly apply mechanical time series techniques to such a variable, I wonder why it is sensible. I am not a labor economist, but I would think that the interesting thing would be the REAL (inflation-adjusted) minimum wage, using a state deflator, vs. the 5th REAL wage percentile. Now dividing each of those by the same price deflator will cancel out of your ratio (or difference of logs), but it makes more sense from the econometric standpoint to subject a real minimum wage (which is not a policy variable, but an outcome) to a unit root test than it does the series you are using.

I will add a message to ipshin indicating that the IPS tables are not applicable for more than 8 lags. That is why missing values are appearing in your output. I question whether 17 lags (almost 9 years) makes sense--although again if you're doing unit root tests on a jump process, any automatic lag selection procedure is likely to be fooled by its trajectory.

Kit Baum, Boston College Economics

http://ideas.repec.org/e/pba1.html

On Nov 19, 2004, at 2:33 AM, Jeanette wrote:

When I create

a third variable (log of 5th wage percentile - log of minimum wage,

or"lngap"), the IPSHIN test indicates that it is stationary. How can it be

that the ratio of a stationary and nonstationary variable is stationary?

(Some background info: the panels in this dataset are US states -- all 50,

the time points are 6 month intervals over 20 years).

* * For searches and help try: * http://www.stata.com/support/faqs/res/findit.html * http://www.stata.com/support/statalist/faq * http://www.ats.ucla.edu/stat/stata/

* * For searches and help try: * http://www.stata.com/support/faqs/res/findit.html * http://www.stata.com/support/statalist/faq * http://www.ats.ucla.edu/stat/stata/

**References**:**st: Re: interpreting ipshin results***From:*Kit Baum <[email protected]>

- Prev by Date:
**st: RE: RE: Question regarding web aware features** - Next by Date:
**st: Re: Information on multilevel models in STATA** - Previous by thread:
**st: Re: interpreting ipshin results** - Next by thread:
**st: psmatch2 update** - Index(es):

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