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

Extensions and refinements for the trimming of propensity scores (IRM & IIVM) #109

Open
MalteKurz opened this issue May 25, 2021 · 0 comments
Assignees
Labels
enhancement extension of existing feature

Comments

@MalteKurz
Copy link
Member

Trimming as part of the ML estimation and prediction step

  • At the moment the trimming of propensity scores is part of the "score evaluation step", see
    if (self.trimming_rule == 'truncate') & (self.trimming_threshold > 0):
    m_hat[m_hat < self.trimming_threshold] = self.trimming_threshold
    m_hat[m_hat > 1 - self.trimming_threshold] = 1 - self.trimming_threshold
  • Therefore, the exported predictions in property predictions are not yet trimmed. Presumably, it would be more reasonable to make the trimming during the "ML estimation and prediction step". Otherwise users might question whether the trimming really happens.

New trimming rule 'discard'

  • Currently, we only have implemented the trimming_rule 'truncate'. As alternative, we also want to offer the trimming_rule 'discard'. For this we need to find a stable way to exclude observations from subsequent steps. Predictions can obviously just be set to np.nan. In subsequent steps these observations need to be excluded. In the repeated cross-fitting case this can then result in different number of observations being evaluated for different random sample splits. At the beginning we might want to prevent these technically challenging cases and only allow trimming_rule = 'discard' for n_rep == 1.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement extension of existing feature
Projects
None yet
Development

No branches or pull requests

2 participants