Datasets:
Update README.md
Browse files
README.md
CHANGED
|
@@ -36,7 +36,30 @@ masks, segmentation images, and image-level JSON metadata.
|
|
| 36 |
|
| 37 |
## Description
|
| 38 |
|
| 39 |
-
The <em>Synset Signset Sensitivity Analysis Dataset</em>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 40 |
|
| 41 |
## Citation and Reference
|
| 42 |
|
|
@@ -72,6 +95,9 @@ For example, as follows:
|
|
| 72 |
|
| 73 |
## Uses
|
| 74 |
|
|
|
|
|
|
|
|
|
|
| 75 |
### Direct Use
|
| 76 |
|
| 77 |
<!-- This section describes suitable use cases for the dataset. -->
|
|
@@ -85,6 +111,14 @@ one trade-off is more favorable for specific traffic sign classes or model archi
|
|
| 85 |
|
| 86 |
<!-- This section addresses misuse, malicious use, and uses that the dataset will not work well for. -->
|
| 87 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 88 |
## Dataset Structure
|
| 89 |
|
| 90 |
<!-- This section provides a description of the dataset fields, and additional information about the dataset structure such as criteria used to create the splits, relationships between data points, etc. -->
|
|
@@ -107,11 +141,36 @@ one trade-off is more favorable for specific traffic sign classes or model archi
|
|
| 107 |
### Curation Rationale
|
| 108 |
|
| 109 |
<!-- Motivation for the creation of this dataset. -->
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 110 |
|
| 111 |
### Source Data
|
| 112 |
|
| 113 |
<!-- This section describes the source data (e.g. news text and headlines, social media posts, translated sentences, ...). -->
|
| 114 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 115 |
#### Who are the source data producers?
|
| 116 |
|
| 117 |
<!-- This section describes the people or systems who originally created the data. It should also include self-reported demographic or identity information for the source data creators if this information is available. -->
|
|
@@ -132,7 +191,7 @@ one trade-off is more favorable for specific traffic sign classes or model archi
|
|
| 132 |
|
| 133 |
The major part of the annotations, including masks, segmentation images, camera parameters and artifacts, and environmental conditions,
|
| 134 |
is based on ground truth data created as part of the scene generation / rendering process. Semantic segmentation images were rendered
|
| 135 |
-
using the [
|
| 136 |
which provides rasterization / shading-based image generation.
|
| 137 |
|
| 138 |
The only manual annotation performed in the creation of the particular dataset is the labeling of permissible upper and lower signs taking
|
|
|
|
| 36 |
|
| 37 |
## Description
|
| 38 |
|
| 39 |
+
The <em>Synset Signset Sensitivity Analysis Dataset</em> is a large-scale, physically based synthetic test dataset designed to
|
| 40 |
+
systematically analyze the sensitivity of deep-learning perception models to sensing parameters. The dataset focuses on the task
|
| 41 |
+
of traffic sign recognition and was generated using the [OCTAS®](https://octas.org/) simulation platform, based on the
|
| 42 |
+
[Synset Signset Germany](https://synset.de/datasets/synset-signset-ger/) (SSG) data-generation pipeline. Rather than applying purely
|
| 43 |
+
artificial image corruptions trough image augmentations, the dataset represents degradations through physically meaningful parameters.
|
| 44 |
+
|
| 45 |
+
The dataset investigates the trade-off between exposure time and camera gain, or ISO, under low-light conditions. Increasing the exposure
|
| 46 |
+
time can compensate for reduced irradiance but introduces motion blur, whereas increasing the camera gain enables shorter exposure times
|
| 47 |
+
at the cost of increased additive image noise. This trade-off is represented by systematically varying motion blur and noise across
|
| 48 |
+
combinations of sensing parameters. The parameter space comprises 36 motion-blur levels, ranging from 0 to 35 pixels, and 61 additive-noise
|
| 49 |
+
levels, ranging from 0.00 to 0.60, resulting in 2,196 subdatasets. The parameter combinations enable the analysis of model sensitivity
|
| 50 |
+
not only to individual sensing parameters but also to their interactions under comparable effective illumination conditions.
|
| 51 |
+
|
| 52 |
+
Each subdataset contains 43 traffic sign classes from the
|
| 53 |
+
[German Traffic Sign Recognition Benchmark](https://ieeexplore.ieee.org/abstract/document/6033395) (GTSRB), with 100 images per class.
|
| 54 |
+
In total, the dataset comprises 9,442,800 test images rendered at a resolution of 48 × 48 pixels (approximately mean image size of GTSRB).
|
| 55 |
+
The images include stochastic variations in viewing angle, environmental illumination, and traffic sign surface appearance.
|
| 56 |
+
In addition to the RGB images, traffic sign masks, segmentation images, and image-level JSON metadata describing the selected
|
| 57 |
+
environmental and imaging parameters are provided.
|
| 58 |
+
|
| 59 |
+
The dataset is intended to support reproducible sensitivity and robustness analyses of deep-learning models under challenging sensing
|
| 60 |
+
conditions. It can be used to examine performance changes across the blur–noise parameter space, compare model architectures and training
|
| 61 |
+
datasets, and characterize class-specific robustness. As a synthetic test dataset with a defined parameter scope, it does not represent
|
| 62 |
+
the full variability of real-world driving environments and should be complemented by evaluations on suitable real-world data.
|
| 63 |
|
| 64 |
## Citation and Reference
|
| 65 |
|
|
|
|
| 95 |
|
| 96 |
## Uses
|
| 97 |
|
| 98 |
+
The dataset was intended to be used as an evaluation benchmark for machine-learning applications for the task of
|
| 99 |
+
German traffic sign recognition, with the aim of assessing their robustness regarding noise and motion blur.
|
| 100 |
+
|
| 101 |
### Direct Use
|
| 102 |
|
| 103 |
<!-- This section describes suitable use cases for the dataset. -->
|
|
|
|
| 111 |
|
| 112 |
<!-- This section addresses misuse, malicious use, and uses that the dataset will not work well for. -->
|
| 113 |
|
| 114 |
+
The dataset should not be used for critical applications, particularly high-risk applications as named by the European AI Act
|
| 115 |
+
under Annex III (which includes "AI systems intended to be used for the ‘real-time’ and ‘post’ remote biometric identification
|
| 116 |
+
of natural persons" and "AI systems intended to be used as safety components in the management and operation of road traffic"),
|
| 117 |
+
without exhaustive research into the fitness of the dataset, to evaluate whether it is "relevant, sufficiently representative,
|
| 118 |
+
and to the best extent possible free of errors and complete in view of the intended purpose of the system."
|
| 119 |
+
No such claim is not made with the publication of this dataset.
|
| 120 |
+
|
| 121 |
+
|
| 122 |
## Dataset Structure
|
| 123 |
|
| 124 |
<!-- This section provides a description of the dataset fields, and additional information about the dataset structure such as criteria used to create the splits, relationships between data points, etc. -->
|
|
|
|
| 141 |
### Curation Rationale
|
| 142 |
|
| 143 |
<!-- Motivation for the creation of this dataset. -->
|
| 144 |
+
The prediction of model performance during operation and the early identification of system limits are pivotal challenges in
|
| 145 |
+
the development of machine-learning systems for safety-critical applications such as automated driving. In particular,
|
| 146 |
+
the robustness of perception models to variations within the operational design domain (ODD) is difficult to quantify,
|
| 147 |
+
as the influence of environmental conditions and sensing parameters can not readily be derived from the system design.
|
| 148 |
+
|
| 149 |
+
Existing approaches often augment real-world datasets with artificially introduced degradations. However, these
|
| 150 |
+
degradations cannot be directly related to physically meaningful properties of the target operational design domain (ODD).
|
| 151 |
+
This dataset was therefore created to demonstrate how physically based synthetic data can be leveraged to systematically
|
| 152 |
+
evaluate not only individual corruptions but also trade-offs and interactions between multiple sensing parameters.
|
| 153 |
+
Specifically, this work focuses on the trade-off between longer exposure times, which introduce motion blur,
|
| 154 |
+
and increased camera gain or ISO, which amplifies image noise.
|
| 155 |
+
|
| 156 |
+
The dataset was designed to be comparable to the [GTSRB](https://ieeexplore.ieee.org/abstract/document/6033395) dataset,
|
| 157 |
+
one of the best known available traffic sign recognition benchmark datasets.
|
| 158 |
|
| 159 |
### Source Data
|
| 160 |
|
| 161 |
<!-- This section describes the source data (e.g. news text and headlines, social media posts, translated sentences, ...). -->
|
| 162 |
|
| 163 |
+
- The dataset was generated in the [OCTAS®](https://octas.org/) simulation framework,
|
| 164 |
+
by using rasterization trough the [OGRE](https://ogre3d.org) engine.
|
| 165 |
+
|
| 166 |
+
- The traffic sign template images, which are used as input to the GAN-based texture synthesis,
|
| 167 |
+
stem from the
|
| 168 |
+
[Wikipedia overview of German traffic signs](https://de.wikipedia.org/wiki/Bildtafel_der_Verkehrszeichen_in_der_Bundesrepublik_Deutschland_seit_2017).
|
| 169 |
+
|
| 170 |
+
- Image-based lighting (IBL) uses environment maps from [PolyHaven](https://polyhaven.com/).
|
| 171 |
+
|
| 172 |
+
- The 3D geometry of the tree that serves as an occlusion object originates from [PolyHaven](https://polyhaven.com/).
|
| 173 |
+
|
| 174 |
#### Who are the source data producers?
|
| 175 |
|
| 176 |
<!-- This section describes the people or systems who originally created the data. It should also include self-reported demographic or identity information for the source data creators if this information is available. -->
|
|
|
|
| 191 |
|
| 192 |
The major part of the annotations, including masks, segmentation images, camera parameters and artifacts, and environmental conditions,
|
| 193 |
is based on ground truth data created as part of the scene generation / rendering process. Semantic segmentation images were rendered
|
| 194 |
+
using the [OGRE](https://www.ogre3d.org/) rendering engine plugin for [OCTAS®](https://octas.org/),
|
| 195 |
which provides rasterization / shading-based image generation.
|
| 196 |
|
| 197 |
The only manual annotation performed in the creation of the particular dataset is the labeling of permissible upper and lower signs taking
|