-
Notifications
You must be signed in to change notification settings - Fork 0
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
dropping rows with NA's in relevant columns only #105
Conversation
I'm going to run just the data targets in production to make sure this does the right thing too. |
… errors,launch_max big
…ion-tooling into dropOnlyNecessaryNAs
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seems fine to me at a high level skim.
so after I also added the necessary changes to get |
34602e2
to
aee17ff
Compare
0eb5d36
to
393147e
Compare
We definitely need to figure out a better way to deal with dates for |
The reason our forecasters were underperforming was that when merging the chng and hhs dataset, we were removing any rows with NA's. This fixes things to only remove NA's inside a forecaster, and only for columns actually used in forecasting. For an example of the problematic data, compare
which is the last hhs data, while
which is the last chng data
joined matches chng:
closes #93