-
Notifications
You must be signed in to change notification settings - Fork 867
Home
Welcome to the Numenta Anomaly Benchmark (NAB) wiki! Below are some documents to help you dive into NAB. Please also take a look at our ICMLA publication on NAB.
An in-depth guide to everything NAB:
- NAB scoring details -- scoring metrics, function, profiles, etc.
- NAB phases/process
- Ground truth anomaly labels
- Glossary of NAB terms
Guidelines on how to report your NAB results
How to enter a custom detector to run NAB
- [Example with Twitter algorithm](Twitter Anomaly Detector)
- Diagram
In order for a researcher to report NAB results on an algorithm, it must meet the following additional criteria:
-
Any sort of look ahead is not allowed. Detections by the algorithm must be made on the fly, one record at a time.
-
There must be no batch, or per dataset, parameter tuning. The algorithm must be fully automated with a single set of parameters across all data files. Any further parameter tuning required by the algorithm must be done on the fly. (One exception to this rule is that it is ok for the algorithm to know the range of data values for each data file. In the NAB detector code, this is passed in automatically as each algorithm is initialized.)
-
Each file is treated independently. The algorithm is initialized from scratch for each stream using a single constant set of parameters.
These rules are designed to simulate real-world streaming scenarios. It is very easy to "game" the system without following the above rules. Anyone reporting NAB results should convince the reader that the above criteria are met. A great way is to release all your code as open source, or by documenting your process sufficiently so that someone else can replicate it.
Details on contributing data, algorithms, code, or suggestions to NAB.
How to hand label raw time-series data for anomalies