-
Notifications
You must be signed in to change notification settings - Fork 779
period problem with AnomalyDetectionTs #45
Comments
Hi Conny, I would suggest trying the AnomalyDetectionVec function instead of the TS function. At the moment, the TS function aggregates secondly data into minutely data. The Vec function simply takes a list of values, and then treats them as a time series without the timestamp column. A few things might help when using the Vec function:
Hope that helps. |
Hi Owenvallis, thanks very much for the answer! But I still have another stupid question, what is ESD? |
@blatoo ESD stands for Seasonal Hybrid ESD (S-H-ESD), which is the primary algorithm of this package. |
Hi @terrytangyuan , Thanks very much!!! |
Could anyone close this? Thanks. |
Hey I also ran into the same issue even though my input time series is having a regular interval. Please note I haven't used any NA values. Looks like this issue is still open. |
Hello, I am experiencing a similar error with 1 Hz data. Have there been any developments on this issue since feb? `> str(data)
|
This worked for me. res = AnomalyDetectionVec(group_prof_10252016[,2], max_anoms=0.02, On Sat, Oct 29, 2016 at 3:38 PM, Evan Henry notifications@github.com
|
Hi all, I am quite new to this package and would like to use it for some analysis i am doing. I have data that is not regular ie. trading. Would i be able to use the AnomalyDetection to identify say irregular rices charged? If so, what would i set the "period" to, as on some days there might be a trade every second, or hour, and on some days none? i have data for roughly a year. Any help will be greatly appreciated! |
hi jj7353, thx. |
In the example of raw_data, it is by minute. |
Hi everybody,
After successfully running the example, I created an own data set, which has the same format like
raw_data
, I create anmyData
, which has the same structure as theraw_data
. But there still two places are a little differentIt looks like:
1 1970-01-01 01:00:55 NA
2 1970-01-01 01:00:10 NA
3 1970-01-01 01:00:25 2.871
4 1970-01-01 01:00:40 2.654
5 1970-01-01 01:00:55 3.060
6 1970-01-01 01:00:10 9.074
after I run the same command like the example:
I got the error message:
How can I fix this problem?
If I don't know the period, can I still find the anomalies?
Thanks very much for the great work!
Best Regards
Conny
The text was updated successfully, but these errors were encountered: