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

average_late with poor overlap or compliance #553

Closed
ginward opened this issue Oct 27, 2019 · 1 comment
Closed

average_late with poor overlap or compliance #553

ginward opened this issue Oct 27, 2019 · 1 comment

Comments

@ginward
Copy link
Contributor

ginward commented Oct 27, 2019

Is it possible for #490 to calculate Cov[Y, Z | X = x] / Cov[W, Z | X = x] | W=1 , or Cov[Y, Z | X = x] / Cov[W, Z | X = x] | Z=1? From the covariance term in the denominator, it looks like the denominator will explode.

I am estimating average treatment effects with continuous treatments. However, my dataset is imbalanced (only a small set of population is assigned to treatment), meaning that many compliance scores are close to 0.

I got the following warnings from the average_late function:

Warning messages:
1: In average_late(entry.forest) :
  Estimated treatment propensities take values between -1.534 and 3.004 and in particular get very close to 0 or 1. Poor overlap may hurt perfmance for average conditional local average treatment effect estimation.
2: In average_late(entry.forest) :
  The instrument appears to be weak, with some compliance scores as low as -0.1285

Because there is no overlap or treated option available to deal with the low propensity score issue. Is there a reason why these two options were not implemented?

@ginward ginward changed the title average_partial_effect and average_late with poor overlap average_partial_effect and average_late with poor overlap and compliance Oct 30, 2019
@ginward ginward changed the title average_partial_effect and average_late with poor overlap and compliance average_late with poor overlap or compliance Oct 31, 2019
@ginward ginward closed this as completed Nov 7, 2019
@jtibshirani
Copy link
Member

Hello @ginward, I've noticed that you have opened and closed a few issues without any discussion. Could you please hold off on closing an issue until it has been resolved?

If you ended up finding the answer to your question, you can add it in a comment for future reference. We would like to avoid issues that contain open questions with no answer -- many people read over GitHub issues when debugging/ looking for information, and it can be confusing to see closed issues with no resolution.

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