Skip to content

how to deal with signals with partially missing data? #10

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

Closed
Tracked by #4
dsweber2 opened this issue Sep 27, 2023 · 5 comments
Closed
Tracked by #4

how to deal with signals with partially missing data? #10

dsweber2 opened this issue Sep 27, 2023 · 5 comments

Comments

@dsweber2
Copy link
Contributor

dsweber2 commented Sep 27, 2023

This may be something we can handle in extend_ahead and family, or it may have to be an additional input

@dsweber2 dsweber2 added this to the initial exploration milestone Sep 27, 2023
@dshemetov
Copy link
Contributor

dshemetov commented Sep 27, 2023

Options

  • Catch these errors and halt
  • Catch error and forecast nothing
  • Catch error and impute gaps in data

@nmdefries
Copy link
Contributor

Broadly, find a way to impute missing data.

epipredict fns complain about NAs a lot. Want at least one fn that can handle these. Maybe an arg can set the requested behavior (what we've done in other scripts: 0-fill, mean-fill, smoothing between two closest points)

@dshemetov
Copy link
Contributor

Related: cmu-delphi/epipredict#106

@dshemetov
Copy link
Contributor

Related #59

@dshemetov
Copy link
Contributor

dshemetov commented Nov 13, 2023

closed by #55

handled by using drop_na on the input data to the pipeline. we can open another issue if find we need imputation.

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

3 participants