Create README.md
Browse files
README.md
ADDED
|
@@ -0,0 +1,38 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
*Important.* This dataset is part of the [**torchmil** library](http://torchmil.readthedocs.io/).
|
| 2 |
+
|
| 3 |
+
|
| 4 |
+
Traffic Anomaly Detection (TAD) dataset adapted for Multiple Instance Learning (MIL).
|
| 5 |
+
|
| 6 |
+
|
| 7 |
+
### About the Original Traffic Anomaly Detection (TAD) Dataset
|
| 8 |
+
|
| 9 |
+
The original [Traffic Anomaly Detection (TAD) dataset](https://www.kaggle.com/datasets/nikanvasei/traffic-anomaly-dataset-tad) contains video clips. Each clip is labeled to indicate whether it contains an anomaly or not; however, frame-level labels are not available
|
| 10 |
+
|
| 11 |
+
### Dataset Description
|
| 12 |
+
|
| 13 |
+
We have preprocessed the videos by computing features for each frame using various feature extractors.
|
| 14 |
+
|
| 15 |
+
- A **video** is labeled as positive (`label=1`) if it contains evidence of traffic anomaly.
|
| 16 |
+
- A **video** is labeled as positive (`label=1`) if it contains at least one positive frame.
|
| 17 |
+
|
| 18 |
+
This means a video is considered positive if there is any evidence of traffic anomaly.
|
| 19 |
+
|
| 20 |
+
### Directory structure
|
| 21 |
+
|
| 22 |
+
The following directory structure is expected:
|
| 23 |
+
|
| 24 |
+
```
|
| 25 |
+
root
|
| 26 |
+
├── features
|
| 27 |
+
│ ├── features_{features}
|
| 28 |
+
│ │ ├── video1.npy
|
| 29 |
+
│ │ ├── video2.npy
|
| 30 |
+
│ │ └── ...
|
| 31 |
+
├── labels
|
| 32 |
+
│ ├── video1.npy
|
| 33 |
+
│ ├── video2.npy
|
| 34 |
+
│ └── ...
|
| 35 |
+
└── splits.csv
|
| 36 |
+
```
|
| 37 |
+
|
| 38 |
+
Each `.npy` file corresponds to a video. The `splits.csv` file defines train/test splits for standardized experimentation.
|