Ram
11/23/2023, 2:01 AMNot enough data to calculate anomaly score
I tried different anomaly_sensitivity from 1.5 to 2
Nothing is working out
models:
- name: metric_cal
config:
elementary:
timestamp_column: 'metric_date'
columns:
- name: metric_value
tests:
- elementary.column_anomalies:
column_anomalies:
- sum
time_bucket:
period: month
count: 1
days_back: 426
config:
severity: ERROR
anomaly_sensitivity: 2
where_expression: "product_name = 'Transactions' "Daniel Pollak
11/23/2023, 10:04 AMRam
11/23/2023, 2:18 PMRam
11/23/2023, 2:19 PMRam
11/24/2023, 3:47 PMRam
11/28/2023, 2:41 PMMaayan Salom
12/05/2023, 1:17 PMmin_training_set_size is by default 14. As we truncate to full months, 426 days probably result in 13 buckets.
you can change the default, see here how:
https://docs.elementary-data.com/data-tests/anomaly-detection-configuration/min-training-set-sizeRam
12/06/2023, 3:35 PMmin_training_set_size:13 Still i see Not enough data to calculate anomaly score.Ram
12/06/2023, 3:36 PMRam
12/06/2023, 3:36 PMmodels:
- name: metric_cal
config:
elementary:
timestamp_column: 'metric_date'
columns:
- name: metric_value
tests:
- elementary.column_anomalies:
min_training_set_size: 13
column_anomalies:
- sum
time_bucket:
period: month
count: 1
days_back: 426
config:
severity: ERROR
anomaly_sensitivity: 2
where_expression: "product_name = 'Transactions' "Ram
12/06/2023, 3:44 PMMaayan Salom
12/06/2023, 3:46 PMRam
12/06/2023, 4:42 PMRam
12/06/2023, 4:42 PMRam
12/06/2023, 4:58 PMRam
12/06/2023, 4:58 PM