Papers › DailyDVS-200: A Comprehensive Benchmark Dataset for Event-Based Action Recognition

DailyDVS-200: A Comprehensive Benchmark Dataset for Event-Based Action Recognition

6 Jul 2024arXiv:2407.05106archive 2025-07-28

Qi Wang, Zhou Xu, Yuming Lin, Jingtao Ye, Hongsheng Li, Guangming Zhu, Syed Afaq Ali Shah, Mohammed Bennamoun, Liang Zhang

Neuromorphic sensors, specifically event cameras, revolutionize visual data acquisition by capturing pixel intensity changes with exceptional dynamic range, minimal latency, and energy efficiency, setting them apart from conventional frame-based cameras. The distinctive capabilities of event cameras have ignited significant interest in the domain of event-based action recognition, recognizing their vast potential for advancement. However, the development in this field is currently slowed by the lack of comprehensive, large-scale datasets, which are critical for developing robust recognition frameworks. To bridge this gap, we introduces DailyDVS-200, a meticulously curated benchmark dataset tailored for the event-based action recognition community. DailyDVS-200 is extensive, covering 200 action categories across real-world scenarios, recorded by 47 participants, and comprises more than 22,000 event sequences. This dataset is designed to reflect a broad spectrum of action types, scene complexities, and data acquisition diversity. Each sequence in the dataset is annotated with 14 attributes, ensuring a detailed characterization of the recorded actions. Moreover, DailyDVS-200 is structured to facilitate a wide range of research paths, offering a solid foundation for both validating existing approaches and inspiring novel methodologies. By setting a new benchmark in the field, we challenge the current limitations of neuromorphic data processing and invite a surge of new approaches in event-based action recognition techniques, which paves the way for future explorations in neuromorphic computing and beyond. The dataset and source code are available at https://github.com/QiWang233/DailyDVS-200.

PaperPDFCodeCode Syntology ran

In Syntology View this paper on Syntology, its page in Syntology's graph. That page adds which of its functions are also present in other papers' code Syntology holds, with dates, and its dated run record as JSON and a README badge. It also lists the repositories linked to the paper, the abstract and the calls for agents.

Open this paper in Syntology's Atlas, the map of the papers in Syntology's graph and their citations.

For agents, on Syntology's MCP service (how to connect):

Code

Syntology 15 code samples harvested from 1 repository linked to this paper: 9 ran (of which 0 constructed an object rather than computing a result; 7 with no instrument failure: 0 honoured, 0 violated, 7 with no contract checked; 2 where Syntology's instrument failed) · 6 unverified. Where Syntology's instrument failed: 1 where our contract draft was wrong; 1 where the contract check could not run; failures of Syntology's instrument, not of the code.

By repository: official repository: 15 samples from 1 repository, 9 ran (7 with no instrument failure; 2 where Syntology's instrument failed). The run record, sample by sample. “Ran” means executed on a synthesized input, not that the code is correct or reproduces the paper.

Levels written on 2026-09-24 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

qiwang233/dailydvs-200 officialmentioned in papermentioned on GitHubpytorchSyntology: 15 samples, 9 ran (2 instrument-failed) · 6 unverified report

Repository list and official/mentioned flags are the archive's, frozen 2025-07-28. Reachability, where shown, is from one Syntology probe window (2026-09-16 to 2026-09-18); repositories not probed show nothing. GitHub stars are not tracked.

Code Syntology ran Syntology

15 samples harvested: 9 ran (of which 0 constructed an object rather than computing a result; 7 with no instrument failure: 0 honoured, 0 violated, 7 with no contract checked; 2 where Syntology's instrument failed) · 6 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Syntology's record for this page last changed ; when this build read Syntology's graph is in the build record. That date is not when the samples ran.

1ran · our draft was wrong
1ran; the contract check could not run
7ran
6unverified

Licence: 15 of the 15 samples are pointer only, meaning Syntology does not serve that copy's text. This page shows no code text for any sample; each one links to its file in the repository.

Harvested from qiwang233/dailydvs-200. “Ran” means the sample executed on a synthesized input. It does not mean the output is correct, and nothing here reproduces the paper's results. A line beginning “fixture:” under a sample that ran gives the arguments Syntology's fixture called the sample with, each as name:type/rank/element kind (? where none was recorded), and the type of what the fixture's run returned, exactly as the harness recorded them; the arguments and the returned type were recorded by two separate runs of the same fixture. No output value is shown, and a returned type says nothing about whether the output was right. “Level recorded” gives the UTC date when Syntology's graph wrote the sample's verification level, not when the code executed; where the level was written before Syntology's graph kept that date, the row says “level recorded, date not recorded”. “Honoured” and “violated” refer to a contract Syntology drafted from the code itself. “Our draft was wrong” and “the contract check could not run” are failures of Syntology's instrument, not of the code: the sample ran on Syntology's synthesized input, and then the drafted contract did not describe it, or the check itself raised an error (RAISES), lacked a dependency (DEP_MISSING) or ran out of time (TIMEOUT); hover the label for which. A metamorphic tier, where shown, is evidence of the output's shape, not that the sample implements the method.

Each sample ends with its code_sha256. A sample's code_sha256 is Syntology's identity for that exact code. It is printed in full (16 hexadecimal characters for every sample in this build), and get_code(code_sha256="…") takes it exactly as printed. An agent calls it on Syntology's MCP service (how to connect); click an identity to copy that call.

Repository labels, per sample. official repository: The archive marks this repository official for the paper. named in the paper: The archive records that the paper mentions this repository; it is not marked official. community (archive-listed): In the archive's code links for this paper, not marked official and not recorded as mentioned in the paper. found in paper text by Syntology: Syntology found this repository in the paper's own text; whether it is the authors' implementation is not asserted. community: Not in the archive's code links for this paper; a community repository Syntology harvested. Samples are grouped by repository: a repository marked official first, then by how directly the repository is tied to the paper, then in the archive's order; never by how many ran. Licence labels name the repository's licence as recorded at harvest. “Pointer only” means Syntology does not serve that copy's text, for one of six reasons: no licence file was found; the licence was not identified; the licence is recorded as permissive but that copy's record is not marked cleared; the licence is outside the permissive list Syntology serves text under (MIT, Apache-2.0, BSD and similar); this paper's copy was not located, so its licence is not recorded; or this paper's copy is cleared, but the stored copy of the same code that Syntology serves is not. Some licences outside that list permit redistribution, such as WTFPL, and GPL-3.0 under its conditions; they are simply not on the list. Hover a licence label for the reason. File links open the file on GitHub at the default branch, which may have changed since the harvest.

A function or class name links to its page when the name occurs in the harvested code of at least 5 papers; the name is a string, not an identity.

qiwang233/dailydvs-200 official repository 15 samples, 9 ran (2 instrument-failed) · 6 unverified
TET_loss in 7 papers models/SDT/criterion.py ran no licence file found · pointer only · a71accca7675fc44 · report fixture: signature outputs:Tensor/3/float, labels:Tensor/2/float, criterion:callable/0/?, means:float/0/float, lamb:float/0/float · returned Tensor · level recorded 2026-09-24
collate_events models/EST/utils/loader.py ran · our draft was wrong no licence file found · pointer only · 43484ad381200691 · report fixture: signature data:list/1/tuple · returned tuple · level recorded 2026-09-24
events_to_image_torch models/GET/event_based/image.py ran no licence file found · pointer only · a52cf74a4677906b · report fixture: signature xs:Tensor/1/float, ys:Tensor/1/float, ps:Tensor/1/float, device:NoneType/0/?, sensor_size:tuple/1/int, clip_out_of_range:bool/0/bool, interpolation:str/0/str, padding:bool/0/bool, default:int/0/int · returned Tensor · level recorded 2026-09-24
get_repr models/GET/event_based/event_token.py ran no licence file found · pointer only · 0a60fb3aaf20ac90 · report fixture: signature l:Tensor/1/int, index:list/1/int, bins:list/1/int, weights:list/1/Tensor · returned tuple · level recorded 2026-09-24
get_voxel_grid_as_image models/GET/event_based/voxel_grid.py ran; the contract check could not run (RAISES) fingerprinted no licence file found · pointer only · 0dfe1554721fd4a4 · report fixture: signature voxelgrid:ndarray/3/float · returned ndarray · level recorded 2026-09-24
interpolate_to_image models/GET/event_based/image.py ran no licence file found · pointer only · 93dac52d89e6e10f · report fixture: signature pxs:Tensor/1/int, pys:Tensor/1/int, dxs:Tensor/1/float, dys:Tensor/1/float, weights:Tensor/1/float, img:Tensor/2/float · returned Tensor · level recorded 2026-09-24
random_flip_events_along_x models/EST/utils/dataset.py ran no licence file found · pointer only · 3ee788e2aa3f6880 · report fixture: signature events:ndarray/2/float, resolution:tuple/1/int, p:float/0/float · returned ndarray · level recorded 2026-09-24
random_shift_events models/EST/utils/dataset.py ran no licence file found · pointer only · 5bc6f2b995cb6e5b · report fixture: signature events:ndarray/2/int, max_shift:int/0/int, resolution:tuple/1/int · returned ndarray · level recorded 2026-09-24
top_k_classes models/EST/utils/loss.py ran no licence file found · pointer only · 0e95a53931beb47f · report fixture: signature pred:list/1/int, target:list/1/int · returned list · level recorded 2026-09-24
cross_entropy_loss_and_accuracy models/EST/utils/loss.py unverified no licence file found · pointer only · 59fec32183146f26 · report
events_to_image models/GET/event_based/image.py unverified no licence file found · pointer only · f57431e81eea611b · report
index_mapping models/GET/event_based/event_token.py unverified no licence file found · pointer only · a8eef4af724658bf · report
topk_accuracy in 14 papers models/EST/utils/loss.py unverified no licence file found · pointer only · 6fe8d2de1a126084 · report
voxel_grids_fixed_n_torch models/GET/event_based/voxel_grid.py unverified no licence file found · pointer only · d114e71e8dd88b4c · report
voxel_grids_fixed_t_torch models/GET/event_based/voxel_grid.py unverified no licence file found · pointer only · 25f403aa8aa20268 · report

Tasks

Action Recognition

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

Report a problem or propose a change · a person checks every report against the paper or source before anything changes; decisions are listed on /corrections