Notice: On April 23, 2014, Statalist moved from an email list to a forum, based at statalist.org.
| From | "Caskey, Judson" <judson.caskey@anderson.ucla.edu> |
| To | "statalist@hsphsun2.harvard.edu" <statalist@hsphsun2.harvard.edu> |
| Subject | st: forcing an exact match with ps2match |
| Date | Thu, 2 Sep 2010 10:38:54 -0700 |
FYI, I found a way to force exact matches with psmatch2. I needed this because I wanted to force within year matches, but my data did not have enough treated observations per year to estimate the logit p-score model within year. Here is an example of forcing within-year matches to estimate the effect of union membership on wages: webuse nlswork logit union collgrad age tenure not_smsa c_city south nev_mar predict pscore if e(sample), pr gen pscore2=year*10+pscore psmatch2 union, pscore(pscore2) outcome(ln_wage) caliper(0.5) This works because the psmatch2 code does not force the propensity score to be between 0 and 1. A 1985 observation with a p-score of 0.086 will have pscore2=850.086, which, given the caliper, can only be matched to other 1985 observations. This approach can be used to force exact matches on other variables by just expanding what goes into pscore2. * * For searches and help try: * http://www.stata.com/help.cgi?search * http://www.stata.com/support/statalist/faq * http://www.ats.ucla.edu/stat/stata/