-
Notifications
You must be signed in to change notification settings - Fork 17
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
Improve smoothed Facebook signal in locations that only occasionally meet sample size thresholds #36
Comments
It looks like we're actually dropping counties below the sample size threshold, not reporting NA. In
We do this after smoothing though, so I'm not sure how that affects the weird spike behavior. Forex
|
@nloliveira It's also worth investigating whether the effect seen here in the facebook household cli signals occurs in other sources -- ght comes to mind -- and whether they can/should share a similar solution. |
The new fb pipeline may not have this problem, since smoothing happens before the sample size filters. |
Woops, misclick. |
In the new pipeline, this should only happen to a county that gets nearly 100 observations per 7 days. Some 7-day periods will be reported and some will be omitted. This should not cause jumps or drops in the signal, though. Closing for now; we can open a new issue if there's a more specific problem with the new behavior. |
If a county only has one observation over two weeks, the raw signal will have a spike in it; the smoothed signal will spike and then drop later, since it takes the last 7 days of data.
If a county consistently has observations, but most days they're under the sample size threshold, the raw signal will report NAs on most days and signals on others. That's fine, but the smoothing uses the past 7 days, and will smooth over the NAs and possibly create strange visual artifacts.
Is there a better smoothing or filtering method to avoid this?
The text was updated successfully, but these errors were encountered: