-
Notifications
You must be signed in to change notification settings - Fork 37
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
Fepois: More rigorous tests for separation #457
Comments
I'd be interested in working on this |
Awesome, then I'll assign this issue to it. Maybe we could approach it one separation check at a time, with multiple PRs? This is just a suggestion, I am happy to follow your lead on how to structure the PR(s) =) |
Yes, seems sensible to do it method by method. I was thinking of initially focussing on |
With #660 the user can specify
My understanding is that Would it therefore make sense to close this issue and open two separate issues for the implementation of |
Yes, I think we can close this - I think with the two separation tests we have, we're actually covered really well =) |
Context
In alignment with
fixest
,pyfixest
currently only implements a very basic check for separation.PyFixest currently implements the most basic separation check, which is equivalent to ppmlhdfe's separation(fe).
Ppmlhdfe implements three more separation checks; it would be nice if
fepois()
would support some of them.For a primer on separation, see the primer on separation by the ppmlhdfe team.
To Do:
fepois
andFepois
interfaces.The text was updated successfully, but these errors were encountered: