-
Notifications
You must be signed in to change notification settings - Fork 6
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
does SE clustering actually work? #16
Comments
Hello,
If you want to compute clustered standard errors, you need to specify further arguments, see example below:
A further example is available in the vignette: Best wishes, |
Thanks for your answer. I should have read the documentation more thoroughly. In the second example you give, why would you need to specify the Using summary to print the clustered standard errors unfortunately makes a typical workflow of mine impossible: results <- list()
alpaca::feglm(y ~ x1 + x2 | x3, dat) |> summary() -> results[[1]]
alpaca::feglm(y ~ x1 + x2 | x3 | x4, dat) |> summary() -> results[[2]]
library(texreg)
results |> texreg()
#Error in extract(l[[i]], ...) :
# Neither texreg nor broom supports models of class summary.feglm.
alpaca::feglm(y ~ x1 + x2 | x3, dat) -> results[[1]]
alpaca::feglm(y ~ x1 + x2 | x3 | x4, dat) -> results[[2]]
library(texreg)
results |> texreg()
# no clustered standard errors Integration with other tools (such as texreg, stargazer,...) makes life a lot easer as is the case for fixest. |
here is a a modification that I made to simplify the clustering #17 (comment) |
Hi,
I was wondering whether standard error clustering actually works. In the code example you can see that clustering does not change the standard errors whereas I would expect them to move and fixest estimates them to change:
The text was updated successfully, but these errors were encountered: