Closed anddis closed 5 years ago
Yes! See Stuart (2008, p2063) and Stuart (2010, p11) for some examples. The important matter is that the denominator should remain the same before and after adjustment so that the change in mean balance is not conflated with a change in variances (the balance of which is assessed separately). This is also what MatchIt
and twang
use when assessing balance.
Consider the following example: the mean difference of X is 2 before matching, and the standard deviations in both groups are 2, so the unadjusted SMD is 1. Let's say after matching the mean difference is now 1, but the standard deviations in both groups have shrunk to .9. The adjusted SMD using the unadjusted standard deviation is .5, but the SMD using the adjusted standard deviation is 1.11, indicating balance has worsened, when in reality, the bias in the effect estimate has decreased. This is an extreme example in which the conclusions dramatically reverse, but it's possible for the wrong conclusion to be drawn when comparing your new SMD to a set threshold in less egregious cases.
Thanks for your prompt and informative response, Noah!
Hello,
Not really a bug/issue with
cobalt
, rather a question about SMDs I'd be grateful if you could help me with.Following a 1:1 NNM matching, some of the treated subjects are left unmatched. When computing the SMD,
cobalt
(with the options.d.denom = "treated"
) uses the SD in all treated subjects, ie including those unmatched. This is consistent withMatchIt
's behaviour.In a similar fashion,
cobalt
with the options.d.denom = "pooled"
computes the denominator of the SMDs using the SD in all untreated subjects (matched and unmatched).I understand that the denominator of a SMD is –at the end of the day– arbitrary: it's just a value used to standardise the MD (duh!) and we could use –in principle– the SD of any population.
However, I wonder if you have any reference that supports the use of just those SDs as opposed to the SDs in the subjects (treated and untreated) who are successfully matched.