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

Identify no change in time series #140

Open
guidocioni opened this issue Aug 9, 2022 · 1 comment
Open

Identify no change in time series #140

guidocioni opened this issue Aug 9, 2022 · 1 comment

Comments

@guidocioni
Copy link

Sometimes an anomaly could lie in the fact that the timeseries value is not changing at all, that is the previous value is exactly the same as the next one.

Is it possible to adapt the PersistAD detector to identify these points as anomalies?

I was looking into the underlying Pipenet implementation but unfortunately it seems that the only way to identify the anomaly is to find something exceeding a certain threshold and not just staying the same.

@danendral
Copy link

Have you tried using VolatilityShiftAD?

It compares the volatility (e.g. standard deviation) between two rolling windows. You can also set if you want to detect positive or negative value change in the selected aggregation method.

In your case, you may set side = "negative" as you want to see the huge drop in volatility (right window volatility will be zero when there are constant values)

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