Datasets › Spike-X4K

Spike-X4K (Spike-X4K Dataset)

Introduced by Liangyan Jiang et al. in SwinSF: Image Reconstruction from Spatial-Temporal Spike Streams22 Jul 2024 archive 2025-07-28

Overview

The Spike-X4K Dataset is a high-resolution image reconstruction resource tailored for the latest advancements in spike camera technology. It is designed to meet the demands of modern spike cameras with a resolution of 1000×1000 pixels, surpassing the capabilities of previous datasets like spike-REDS, which was limited to a resolution of 250×400 pixels.

Dataset Characteristics

  • Resolution: 1000×1000 pixels, aligning with state-of-the-art spike camera imaging standards.
  • Temporal Depth: The dataset captures the temporal dynamics of scenes with high-speed motion, providing a temporal sequence of spike frames.
  • Content: It includes both synthetic and real-world datasets, offering a diverse range of high-speed motion scenarios for training and testing image reconstruction models.
  • Pairs: The dataset comprises 1200 spike stream-ground truth image pairs for training and 45 pairs for testing, ensuring robust model evaluation.

Motivation and Content Summary

The development of the Spike-X4K Dataset was motivated by the need for a more representative and higher resolution dataset that could effectively train and evaluate image reconstruction models for spike cameras. Spike cameras, with their unique ability to capture photons independently at each pixel and generate binary spike streams, offer high temporal resolution and low latency, which are crucial for high-speed imaging. However, converting these spike streams into high-quality images requires sophisticated algorithms, and the Spike-X4K Dataset provides the necessary data to develop and refine these algorithms.

Potential Use Cases

  1. Algorithm Development: For researchers and engineers working on spike image reconstruction algorithms specific to spike camera data.
  2. Benchmarking: As a standard for benchmarking the performance of various image reconstruction models against state-of-the-art techniques.
  3. Training and Testing: Providing a large and diverse set of data for training deep learning models to handle high-speed motion imaging.
  4. Feature Extraction: Enabling the study and improvement of feature extraction techniques from spike streams, including spatial and temporal features.
  5. Spike Image Reconstruction Tasks: Supporting a wide range of computer vision tasks that can benefit from high-resolution, high-speed imaging, such as motion analysis, object tracking, and event detection.

Benchmarks archive 2025-07-28

All 1 leaderboard whose dataset resolves to this page shown (sort by any header). "First row" is the archive's own first row at snapshot, in the archive's row order; nothing here re-ranks and metric direction is not asserted.

First row (archive order)PaperCode
Image Reconstruction Spike-X4K SwinSF Average PSNR 39.61 SwinSF: Image Reconstruction from Spatial-Temporal Spike Streams bupt-ai-cz/SwinSF 1 Compare

Papers archive 2025-07-28

papers with a benchmark row: 1 · with a code link: 1 · where Syntology ran a sample: 0 (0 with a run with no instrument failure, 0 where every run was a failure of Syntology's instrument) Syntology

Show: all papers with a benchmark rowonly where code ran: none of the 1 papers with a benchmark row has a Syntology run on record

Page 1 of 1: paper 1 of 1 with a leaderboard row on this dataset's benchmarks, newest first by the archive's date (ties by slug; undated papers last).

The archive's own "papers using this dataset" list was never published, so this is the benchmark-backed subset, not that list; the archive's count for this dataset is 1. The Syntology column is from Syntology's graph, stated per sample; it is not part of any archive number. A line reads “N ran (of which C constructed an object rather than computing a result; K with no instrument failure: H honoured, V violated, P with no contract checked; I where Syntology's instrument failed) · U unverified” (C is a part of N, never taken away from it); the figure “where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. “Ran” means the sample executed on a synthesized fixture, not that the paper's result was reproduced. When the archive marks a repository official for the paper, the cell starts with that repository's state (the archive's flag, not a verdict on who wrote the code; “community repositories only” when every sample that ran came from a community repository, “official: no sample here; runs from other or unrecorded repositories” when some came from a repository the paper names or has in its text, or from none recorded); hover it for the repositories the samples that ran came from. Syntology's record for this page last changed ; when this build read Syntology's graph is in the build record.

PaperCodeResultsDateSamples run Syntology
SwinSF: Image Reconstruction from Spatial-Temporal Spike Streams 1 1 22 Jul 2024 not harvested

Dataset loaders archive 2025-07-28

1 loader as listed in the archive; links are outbound and not re-checked here.

Tasks archive 2025-07-28

License archive 2025-07-28

No licence recorded in the archive. Absence here is not a statement about the dataset's terms.

Modalities archive 2025-07-28

No modality tagged.

Languages archive 2025-07-28

Variants archive 2025-07-28

  • Spike-X4K

1 variant name, as the archive lists them.

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