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

Set anomaly period's value in days, irrespective of frequency #336

Closed
Fletchersan opened this issue Oct 25, 2021 · 0 comments
Closed

Set anomaly period's value in days, irrespective of frequency #336

Fletchersan opened this issue Oct 25, 2021 · 0 comments
Assignees

Comments

@Fletchersan
Copy link
Contributor

Currently anomaly period is measured in hours if the frequency of the data is hours and it is measured in days if the frequency of the data is days.
This causes confusion to the users in setting up the period.

Suggested Change:
To set anomaly period's value to be only measured in days.

@Fletchersan Fletchersan self-assigned this Oct 25, 2021
manassolanki added a commit that referenced this issue Oct 27, 2021
fix(anomaly): Closes #336. fix period value measurement wrt frequency
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant