-
Notifications
You must be signed in to change notification settings - Fork 0
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
.se_type_1, .se_type_2 hard coded? #32
Comments
Thank you, @acoppock, for noting this issue. This is due to my lack of sufficient experience in package development. I set defaults in some internal functions used within But I still see the same standard errors by running the following code:
If you added
This is because the default for |
@acoppock , can you also try the following script?
All of these methods produce the same standard errors. |
Thank you for looking into this @yhoriuchi ! On the clusters issue, I had assumed you would be clustering standard errors at the respondent level ("id") -- I believe that's standard practice? I have heard the argument that we don't need to cluster because the random assignment is at the profile level. However, following the rule to "cluster at the level of sampling or assignment, whichever is higher" would suggest clustering at the respondent level. All that to say, I would have thought the default for by the way, I'm not sure how to correctly pass the id variable to
|
Thanks to the team for all the work on this project and package. In
projoint_level
, I think that the values of.se_type_1
and.se_type_2
aren't being passed topj_estimate
, which seems to hard code both values as "classical".as a result, the two calls below yield the same standard error estimates.
The text was updated successfully, but these errors were encountered: