cmu-delphi / cmu-delphi/exploration-tooling

Handling chng "missingness"

Open
#108 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
HTML
Stars
2
Forks
2
PR merge metrics
No merged PRs in 30d

Description

- 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

Contributor guide

No contributing guide indexed for this repository

Research direction

The issue names no files, tests, or entry points; start by locating the existing chng signal, its historical lag data, and the forecaster evaluation path. Clarify whether a separate chng_ideal target is wanted and whether imputation or extrapolation is acceptable. Done should include an agreed treatment of contract-induced gaps and validation of the resulting covariate.

Written by the indexing model from the issue text.

Assessment

Domain
data
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.