My understanding is that -xtlogit- calls -clogit- as a convenience for users familiar with the -xt- commands. I am one of these users.
I correct standard errors for within-individual clustering with either -vce(robust)- for -xt- commands or -vce(cluster individual)-. However, -xtlogit- lacks these options, so I typically block bootstrap to correct standard errors for within-individual clustering.
Today I read the -clogit- help file and learned that -clogit- offers -vce(robust)- and -vce(cluster individual)-! In my limited testing, clustered -clogit- and block bootstrapped -xtlogit- estimate similar standard errors.
My question: Why does -clogit- offer clustered standard errors while -xtlogit- does not? Did I waste years of my life (OK, hours
) block bootstrapping standard errors with -xtlogit-? Are there cases where -clogit- is not a suitable alternative to -xtlogit-? It seems the -xtlogit- help file should point users to -clogit- for more options, or maybe it does somewhere.
I correct standard errors for within-individual clustering with either -vce(robust)- for -xt- commands or -vce(cluster individual)-. However, -xtlogit- lacks these options, so I typically block bootstrap to correct standard errors for within-individual clustering.
Today I read the -clogit- help file and learned that -clogit- offers -vce(robust)- and -vce(cluster individual)-! In my limited testing, clustered -clogit- and block bootstrapped -xtlogit- estimate similar standard errors.
My question: Why does -clogit- offer clustered standard errors while -xtlogit- does not? Did I waste years of my life (OK, hours

Comment