-
Notifications
You must be signed in to change notification settings - Fork 16
FB-survey validation with a generic design to include other pipelines #155
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
Conversation
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.
I haven't run this yet, but it looks like it's not quite ready to go.
This doesn't seem to run, and is full of temp code -- converting to draft to revise |
773d279
to
cd8541f
Compare
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.
Just based on a read-through, not running or testing
…amlined daily dataframe fetch
…unused vars. Simplify API thread methods. Update plans
Code to validate that all geo_id values are valid, by comparing against a list of known values.
- Clarify format vs. value checks - move files from csv/ -> static/
Renamed directory and file (unique_geoids.R) is now expected to be run from within the directory instead of from one level up.
Co-authored-by: nmdefries <[email protected]>
Find Unexpected Values for geo_id compared to historical geo_ids seen
Automatically determine signals and data sources to use for retrieving geo_values. This adds robustness at the cost of efficiency.
Make geo_id list creation robust
Closes #59