Powered by OpenAIRE graph
Found an issue? Give us feedback
ZENODOarrow_drop_down
ZENODO
Dataset . 2025
License: CC BY NC SA
Data sources: Datacite
ZENODO
Dataset . 2025
License: CC BY NC SA
Data sources: Datacite
versions View all 2 versions
addClaim

DCASE 2025 Challenge Task 2 Evaluation Dataset

Authors: Nishida, Tomoya; Harada, Noboru; Niizumi, Daisuke; Albertini, Davide; Sannino, Roberto; Pradolini, Simone; Augusti, Filippo; +5 Authors

DCASE 2025 Challenge Task 2 Evaluation Dataset

Abstract

Description This dataset is the "evaluation dataset" for the DCASE 2025 Challenge Task 2. The data consists of the normal/anomalous operating sounds of seven types of real/toy machines. Each recording is a single-channel 10-sec or 12-sec audio that includes both a machine's operating sound and environmental noise. The following eight types of real/toy machines are used in this task: AutoTrash HomeCamera ToyPet ToyRCCar BandSealer Polisher ScrewFeeder CoffeeGrinder Overview of the task Anomalous sound detection (ASD) is the task of identifying whether the sound emitted from a target machine is normal or anomalous. Automatic detection of mechanical failure is an essential technology in the fourth industrial revolution, which involves artificial-intelligence-based factory automation. Prompt detection of machine anomalies by observing sounds is useful for monitoring the condition of machines. This task is the follow-up from DCASE 2020 Task 2 to DCASE 2024 Task 2. The task this year is to develop an ASD system that meets the following five requirements. 1. Train a model using only normal sound (unsupervised learning scenario) Because anomalies rarely occur and are highly diverse in real-world factories, it can be difficult to collect exhaustive patterns of anomalous sounds. Therefore, the system must detect unknown types of anomalous sounds that are not provided in the training data, which is called UASD (unsupervised ASD). This is the same requirement as in the previous tasks.2. Detect anomalies regardless of domain shifts (domain generalization task) In real-world cases, the operational states of a machine or the environmental noise can change to cause domain shifts. Domain-generalization techniques can be useful for handling domain shifts that occur frequently or are hard-to-notice. In this task, the system is required to use domain-generalization techniques for handling these domain shifts. This requirement is the same since DCASE 2022 Task 2.3. Train a model for a completely new machine type For a completely new machine type, hyperparameters of the trained model cannot be tuned. Therefore, the system should have the ability to train models without additional hyperparameter tuning. This requirement is the same since DCASE 2023 Task 2.4. Train a model both with or without attribute information While additional attribute information can help enhance the detection performance, we cannot always obtain such information. Therefore, the system must work well both when attribute information is available and when it is not.5. Train a model with additional clean machine data or noise-only data (optional) Although the primary training data consists of machine sounds recorded under noisy conditions, in some situations it may be possible to collect clean machine data when the factory is idle or gather noise recordings when the machine itself is not running. Participants are free to incorporate these additional data sources to enhance the accuracy of their models. The last optional requirement is newly introduced in DCASE 2025 Task2. Definition We first define key terms in this task: "machine type," "section," "source domain," "target domain," and "attributes.". "Machine type" indicates the type of machine, which in the additional training dataset is one of eight: auto trash, home camera, Toy pet, Toy RC car, band sealer, polisher, screw feeder. A section is defined as a subset of the dataset for calculating performance metrics. The source domain is the domain under which most of the training data and some of the test data were recorded, and the target domain is a different set of domains under which some of the training data and some of the test data were recorded. There are differences between the source and target domains in terms of operating speed, machine load, viscosity, heating temperature, type of environmental noise, signal-to-noise ratio, etc. Attributes are parameters that define states of machines or types of noise. For several machine types, the attributes are hidden. Dataset This dataset consists of eight machine types. For each machine type, one section is provided, and the section is a complete set of test data. A set of training data corresponding to this test data is provided in another seperate zenodo page as an "additional training dataset" for the DCASE 2025 Challenge task 2 (DCASE 2025 Challenge Task 2 Additional Training Dataset). For each section, this dataset provides 200 clips of test data. File names and attribute csv files File names and attribute csv files provide reference labels for each clip. The given reference labels for each training/test clip include machine type, section index, normal/anomaly information, and attributes regarding the condition other than normal/anomaly. The machine type is given by the directory name. The section index is given by their respective file names. For the datasets other than the evaluation dataset, the normal/anomaly information and the attributes are given by their respective file names. Note that for machine types that has its attribute information hidden, the attribute information in each file names are only labeled as "noAttributes". Attribute csv files are for easy access to attributes that cause domain shifts. In these files, the file names, name of parameters that cause domain shifts (domain shift parameter, dp), and the value or type of these parameters (domain shift value, dv) are listed. Each row takes the following format: [filename (string)], [d1p (string)], [d1v (int | float | string)], [d2p], [d2v]... For machine types that have their attribute information hidden, all columns except the filename column are left blank for each row. Recording procedure Normal/anomalous operating sounds of machines and its related equipment are recorded. Anomalous sounds were collected by deliberately damaging target machines. For simplifying the task, we use only the first channel of multi-channel recordings; all recordings are regarded as single-channel recordings of a fixed microphone. We mixed a target machine sound with environmental noise, and only noisy recordings are provided as training/test data. The environmental noise samples were recorded in several real factory environments. We will publish papers on the dataset to explain the details of the recording procedure by the submission deadline. Directory structure - /eval_data - /raw - /AutoTrash - /test - /section_00_0001.wav - ... - /section_00_0200.wav - /HomeCamera - /ToyPet - /ToyRCCar - /BandSealer - /Polisher - /ScrewFeeder - /CoffeeGrinder Baseline system The baseline system is available on the Github repository https://github.com/nttcslab/dcase2023_task2_baseline_ae. The baseline systems provide a simple entry-level approach that gives a reasonable performance in the dataset of Task 2. They are good starting points, especially for entry-level researchers who want to get familiar with the anomalous-sound-detection task. Condition of use This dataset was created jointly by Hitachi, Ltd., NTT Corporation, and STMicroelectronics and is available under a Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International (CC BY-NC-SA 4.0) license. Citation Contact If there is any problem, please contact us: Tomoya Nishida, tomoya.nishida.ax@hitachi.com Keisuke Imoto, keisuke.imoto@ieee.org Noboru Harada, noboru@ieee.org Daisuke Niizumi, daisuke.niizumi.dt@hco.ntt.co.jp Yohei Kawaguchi, yohei.kawaguchi.xk@hitachi.com

Related Organizations
Keywords

DCASE, acoustic condition monitoring, acoustic signal processing, machine fault diagnosis, acoustic event detection, unsupervised learning, anomaly detection, sound, machine learning, domain shift, computational auditory scene analysis, audio, acoustic scene classification, domain generalization, anomalous sound detection

  • BIP!
    Impact byBIP!
    selected citations
    These citations are derived from selected sources.
    This is an alternative to the "Influence" indicator, which also reflects the overall/total impact of an article in the research community at large, based on the underlying citation network (diachronically).
    0
    popularity
    This indicator reflects the "current" impact/attention (the "hype") of an article in the research community at large, based on the underlying citation network.
    Average
    influence
    This indicator reflects the overall/total impact of an article in the research community at large, based on the underlying citation network (diachronically).
    Average
    impulse
    This indicator reflects the initial momentum of an article directly after its publication, based on the underlying citation network.
    Average
Powered by OpenAIRE graph
Found an issue? Give us feedback
selected citations
These citations are derived from selected sources.
This is an alternative to the "Influence" indicator, which also reflects the overall/total impact of an article in the research community at large, based on the underlying citation network (diachronically).
BIP!Citations provided by BIP!
popularity
This indicator reflects the "current" impact/attention (the "hype") of an article in the research community at large, based on the underlying citation network.
BIP!Popularity provided by BIP!
influence
This indicator reflects the overall/total impact of an article in the research community at large, based on the underlying citation network (diachronically).
BIP!Influence provided by BIP!
impulse
This indicator reflects the initial momentum of an article directly after its publication, based on the underlying citation network.
BIP!Impulse provided by BIP!
0
Average
Average
Average