Skip to content
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

Develop Automated Process for Identifying Bad Count Data #23

Closed
aharpalaniTO opened this issue Mar 14, 2017 · 5 comments
Closed

Develop Automated Process for Identifying Bad Count Data #23

aharpalaniTO opened this issue Mar 14, 2017 · 5 comments
Assignees

Comments

@aharpalaniTO
Copy link

Script written in Postgres for identifying counts (unique combination of arterycode, count_date) for investigation. Unclear whether this will be also involve removal of records from centreline_volumes or whether we pass on to Trevor's team (contingent on implementation of #22).

@aharpalaniTO
Copy link
Author

@aharpalaniTO to review README, @sunnyqywang to continue working through identifying bad data

@aharpalaniTO
Copy link
Author

@aharpalaniTO to provide @sunnyqywang with a list of wavetronics unit artery codes for removal (for now).

@aharpalaniTO
Copy link
Author

@sunnyqywang to create process for determining bad TMC counts and throwing htem out.

sunnyqywang added a commit that referenced this issue Apr 24, 2017
@aharpalaniTO
Copy link
Author

@sunnyqywang developed a process for flagging and removing anomalous TMC count data.

@aharpalaniTO
Copy link
Author

Will continue to improve when anomalies are detected; but issue is effectively closed.

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

2 participants