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.

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

Jump to bottom

Create separate tables with anomalies #38

Open
chintanp opened this issue May 2, 2019 · 2 comments
Open

Create separate tables with anomalies #38

chintanp opened this issue May 2, 2019 · 2 comments
Assignees
@chintanp
Labels
usecase-1 issues related to data pipeline
Milestone
Anomaly Detection...

Comments

@chintanp
Copy link
Contributor

chintanp commented May 2, 2019

No description provided.

@chintanp chintanp added the usecase-1 issues related to data pipeline label May 2, 2019
@chintanp chintanp added this to the Anomaly Detection end milestone May 2, 2019
@chintanp chintanp self-assigned this May 2, 2019
@reconjohn
Copy link
Contributor

Here every day should have 190 files for the 4 meters. Below plots indicating days abnormal with the number of files. More detail csv files are here - https://github.com/demand-consults/demand_acep/tree/master/doc/abnormal

image

image

image

@chintanp
Copy link
Contributor Author

No need for separate tables as yet, since this "anomalies" were due to extra files in the day folder, which was due to double download of data during a day. This has been handled in the this else clause. The code can now handle days with multiple data downloads.

@chintanp chintanp reopened this Jun 22, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@chintanp chintanp

Labels
usecase-1 issues related to data pipeline
Projects
None yet
Milestone
Anomaly Detection end
Development

No branches or pull requests
2 participants
@chintanp @reconjohn