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

Handling chng "missingness" #108

Open
dsweber2 opened this issue Mar 1, 2024 · 1 comment
Open

Handling chng "missingness" #108

dsweber2 opened this issue Mar 1, 2024 · 1 comment

Comments

@dsweber2
Copy link
Contributor

dsweber2 commented Mar 1, 2024

  • if we're trying to justify including change at all, having the "ideal" version (without contract induced data gaps) of the signal as a different covariate would be useful. This could be a different data target called e.g. chng_ideal. This means rewriting the history using historic lag patterns, but with "future" data (which is only latent because of logistics/contracts/etc).
  • imputation/extrapolation? maybe dangerous
@dsweber2
Copy link
Contributor Author

dsweber2 commented Mar 1, 2024

could execute the first of these is by imputation from the eventual as_of versions that are present, using historic revision patterns.

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

1 participant