{smcl}
{* 9oct2002}{...}
{hline}
help for {hi:attr}{right:(SJ2-4: st0026)}
{hline}


{title:Calculate the average treatment effect on the treated using radius matching}

{p 12 17 2}
{cmd:attr}
{it:outcome treatment}
[{it:varlist}] 
[{it:weight}]
[{cmd:if} {it:exp}]
[{cmd:in} {it:range}]
[{cmd:,} 
{cmd:pscore}{cmd:(}{it:scorevar}{cmd:)} 
{cmd:logit}
{cmdab:index}
{cmdab:radius(}{it:#}{cmdab:)}
{cmdab:comsup}
{cmdab:det:ail}
{cmdab:boot:strap }
{cmdab:r:eps(}{it:#}{cmdab:) }
{cmdab:noi:sily}
{cmdab:d:ots }
]

{p 8 8 2}{cmd:fweight}s, {cmd:iweight}s, and {cmd:pweight}s are allowed;
see help {help weights}.


{title:Description}

{p 4 4 2} {cmd:attr} estimates the average treatment effect on the treated
(ATT) using radius matching. {cmd:attr} should be run after the
correct propensity score specification; i.e.,  the one satisfying the
balancing property has been found using, for example, {cmd:pscore}.
If users do not provide a variable name for the propensity score, the
propensity score is estimated based on the specification in {it:varlist}. 
Note that in this case the balancing property is not tested.

{p 4 4 2} It is left under the responsibility of the user to select the
{cmd:comsup} option if the user provided propensity score has been
estimated on a common support for treated and controls.  Otherwise,
the ATT is estimated using also the observations outside the common
support for which the propensity score may not be balanced.

{p 4 4 2} The ATT is computed by averaging over the unit-level treatment
effects of the treated where the control(s) matched to a treated observation
is/are those observations in the control group that lie within the
user-defined {cmd:radius} (the default radius is 0.1). If there are multiple
best controls, the average outcome of those controls is used.


{title:Options}

{p 4 8 2}  
{cmd:pscore(}{it:scorevar}{cmd:)} specifies the name of the user-provided
variable name for the estimated propensity score. If no name is provided
the propensity score is estimated based on the specification in {it:varlist}.

{p 4 8 2}                                                      
{cmd:logit} uses a logit model to estimate the propensity score instead of the
default {cmd:probit} model when the option {cmd:pscore(}{it:scorevar}{cmd:)}
is not specified by the user.  Otherwise, no effect is produced.

{p 4 8 2}                                                      
{cmd:index} requires the use of the linear index as the propensity score 
when the option {cmd:pscore(}{it:scorevar}{cmd:)} is not specified by the user.
Otherwise, no effect is produced.

{p 4 8 2}{cmd:radius(}{it:#}{cmd:)} specifies the size of the radius. The
default is 0.1.

{p 4 8 2} 
{cmd:comsup} restricts the computation of the ATT to the region of
common support.

{p 4 8 2} 
{cmd:detail} displays more detailed output documenting the steps performed to
obtain the final results.

{p 4 8 2} {cmd:bootstrap} bootstraps the standard error of the
treatment effect.

{p 4 8 2}{cmd:reps(}{it:#}{cmd:)} specifies the number of bootstrap
replications to be performed.  The default is 50.  This option produces an
effect only if the {cmd:bootstrap} option is specified.

{p 4 8 2}{cmd:noisily} requests that any output from the replications be
displayed.  This option produces an effect only if the {cmd:bootstrap} option
is specified.

{p 4 8 2}{cmd:dots} requests that a dot be placed on the screen at the
beginning of each replication.  This option produces an effect only if the
{cmd:bootstrap} option is specified.


{title:Remarks}

{p 4 4 2} Please remember to use the {cmd:update query} command before running
this program to make sure you have an up-to-date version of Stata installed.
Otherwise, this program may not run properly.

{p 4 4 2} The treatment has to be binary.

{p 4 4 2} When users do not specify their own previously estimated propensity
score, the bootstrap encompasses the estimation of the propensity score based
on the specification given by {it:varlist}. This procedure is actually
recommended to account for the uncertainty associated with the estimation of
the propensity score.  Even more so when the {cmd:comsup} option is specified
because in this case the region of common support changes with every bootstrap
sample, and bootstrapped standard errors pick up this uncertainty as well. So,
typically users would first identify a specification satisfying the balancing
property -- using {cmd:pscore} -- and then provide exactly this
specification in {it:varlist} and use bootstrapped standard errors.


{title:Saved results} 

{p 4 4 2} The program stores the estimated treatment effect, its standard
error and the t statistic respectively in the scalars {cmd:r(attr)},
{cmd:r(seattr)}, and {cmd:r(tsattr)}.

{p 4 4 2} The number of treated and the number of controls are stored 
respectively in the scalars {cmd:r(ntr)} and {cmd:r(ncr)}.

{p 4 4 2} The bootstrapped standard error and t statistic are stored 
respectively in the scalars {cmd:r(bseattr)} and {cmd:r(btsattr)}.


{title:Examples}

{p 4 8 2}{cmd:. attr wage training age age2 exp exp2}

{p 4 8 2}{cmd:. attr wage training age age2 exp exp2, radius(0.01)}

{p 4 8 2}{cmd:. attr wage training age age2 exp exp2, logit boot dots}

{p 4 8 2}{cmd:. attr wage training age age2 exp exp2, index boot reps(100)}

{p 4 8 2}{cmd:. attr wage training age age2 exp exp2, comsup boot reps(100)}


{title:Authors} 
 
	{browse "http://www.sobecker.de":Sascha O. Becker} 
	Center for Economic Studies, University of Munich 
  
	{browse "http://www.iue.it/Personal/Ichino":Andrea Ichino} 
	Department of Economics, European University Institute, Florence 
  
{p 4 4 2}Email {browse "mailto:so.b@gmx.net":so.b@gmx.net} or {browse "mailto:andrea.ichino@iue.it":andrea.ichino@iue.it} if you observe any problems. 
			
	
{title:Acknowledgments}

{p 4 4 2} The way to implement the propensity score estimation in the
bootstrap procedure has been adapted from the {cmd:psmatch} program
written by Barbara Sianesi (University College London and Institute
for Fiscal Studies) Email: barbara_s@ifs.org.uk. 


{title:Also see}

{p 4 14 2}Online:  help for {help pscore}, {help atts}, {help attk},
{help attnw}, {help attnd} (if installed), and {help bs}.


{p 14 14 2}Further details on the analytical formulas and on the algorithms 
used in these programs  can be found under  
{browse "http://www.sobecker.de":http://www.sobecker.de} 
or 
{browse "http://www.iue.it/Personal/Ichino":http://www.iue.it/Personal/Ichino}.

