Skip to content

Fb survey fix changelog #296

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.

Sign up for GitHub

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

Merged
merged 3 commits into from
Nov 30, 2020
Merged

Fb survey fix changelog #296

Changes from 2 commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
80194c6
Fb-survey Changlog update
Akvannortwick Nov 20, 2020
62791ea
Update covidcast_changelog.md
Akvannortwick Nov 20, 2020
edc2547
Minor fixes
Akvannortwick Nov 20, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 9 additions & 1 deletion docs/api/covidcast_changelog.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
---
---
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This change is probably unintentional and should be un-done, since I think it'll mess up the Markdown formatting

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oops sorry about that, will do.

title: Signal Changelog
parent: COVIDcast API
nav_order: 3
Expand Down Expand Up @@ -40,6 +40,14 @@ Duplicate survey weights had corrupted historical figures for the following sign
* `hrr`: 20200406-20200415, 20200430-20200506
* `msa`: 20200408-20200414, 20200430-20200506
* `state`: 20200408-20200416, 20200430-20200506

#### 20 November 2020

Due to a bug in our data processing system, estimates of the percentage of people reporting that they have been tested for COVID-19 calculated before October 8th were incorrect.
We incorrectly treated an answer of “no” as a missing response, which affected the smoothed_tested_14d and smoothed_wtested_14d signals from the fb-survey source.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
We incorrectly treated an answer of “no” as a missing response, which affected the smoothed_tested_14d and smoothed_wtested_14d signals from the fb-survey source.
We incorrectly treated an answer of “no” as a missing response, which affected the `smoothed_tested_14d` and `smoothed_wtested_14d` signals from the `fb-survey` source.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We typically put source and signal names in monospace font, which the backticks do


As of Nov. 20th, the error has been corrected and all affected data reissued.


### `google-survey`
### `ght`
Expand Down