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

"CR1" Formula #22

Closed
wviechtb opened this issue Aug 17, 2017 · 4 comments
Closed

"CR1" Formula #22

wviechtb opened this issue Aug 17, 2017 · 4 comments

Comments

@wviechtb
Copy link

Shouldn't the adjustment factor for "CR1" be m / (m - p), where m is the number of clusters and p the rank of the model matrix (instead of m / (m - 1))? This would be analogous to 'HC1'. See, for example, MacKinnon and White (1985).

@jepusto
Copy link
Owner

jepusto commented Aug 17, 2017

We use the definition from Cameron and Miller (2015, p. 9). There's not a clear right answer even for very simple cases because the degree of bias depends on whether the predictors are identified within each cluster or between clusters:

  • If you've got all between-cluster predictors (no within-cluster variation), then m / (m - p) will be a closer approximation.
  • If the predictor of interest is identified within each cluster, then the CRVE is roughly the sample variance of the cluster-specific slope estimates, in which case m / (m - 1) will be a closer approximation.

But I think the take-away is clear: CR1 (either version) doesn't account for the fact that the degree of bias adjustment depends on the structure of the predictors. Better to use CR2, which takes these features into account, instead.

@wviechtb
Copy link
Author

I agree that CR2 is better. I was just comparing results from clubSandwich with robust() from metafor, where I use m / (m - p) by default. One can set adjust = "Stata2", which then uses m / (m - 1), but this is currently undocumented (and adjust = "Stata1" which is the same as CR1S, but see issue #23). Would you mind adding m / (m - p) as another option (as CR1<?>)?

@jepusto
Copy link
Owner

jepusto commented Aug 17, 2017 via email

@wviechtb
Copy link
Author

Is the rationale just compatibility/comparability with metafor?

Indeed. Thanks for considering.

jepusto added a commit that referenced this issue Aug 18, 2017
@jepusto jepusto closed this as completed Aug 18, 2017
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

2 participants