Keyboard shortcuts

Press ← or → to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

Event-Camera Fixture Mirrors

A Gen4 reference fixture is a small Prophesee Gen4-HD recording in the frozen EVENT_HDF5 schema v1. The registered active-marker recording supports import and smoke checks; it is not a downstream-fidelity target. See the Status Matrix for fixture and validation readiness.

SRB ships no captures. Capture owners control publication and redistribution. The default fixture is an unpinned placeholder, so fetching it fails until you provide a mirror or explicit URL and SHA256.

How users fetch fixtures today

Use a registered mirror or provide a one-off URL and digest:

srb event-camera list-fixtures
srb event-camera fetch-fixture --mirror hf-andrejorsula-active-marker-gen4

srb event-camera fetch-fixture \
  --url https://your-host.example/gen4_reference.h5 \
  --sha256 <hex digest> \
  --name gen4_reference.h5

The short-name path supplies the maintainer-verified digest and schema version.

Fixture mirror requirements

Register fixtures in KNOWN_FIXTURES in srb/core/sensor/event_camera/fixtures.py only when they meet these conditions:

  • The URL is stable and fetchable with the SRB fetcher. Permissioned Hugging Face mirrors may use its configured token; do not use expiring signed URLs or consent interstitials.
  • The file follows EVENT_HDF5 schema v1: /events/t is int64 nanoseconds, /events/x and /events/y are uint16, /events/p is int8, and /metadata contains schema_version=1, resolution, and the reproducibility attributes from EventEpisodeMetadata. Blosc:zstd-3 and gzip-6 are supported.
  • The entry pins sensor_model, a verified SHA256, and license and attribution in FixtureMirror.license_note. Do not claim rights beyond the capture’s redistribution terms.
  • Modified or resampled captures use a distinct name and short name. Bump the schema version only alongside a compatible migration and republished fixtures.

PR template for adding a fixture mirror

Add the registry entry, a CLI test for get_known_fixture, and an end-to-end fetch check. Include the fetch JSON with schema_version and sensor_model, and document the license and redistribution authority in the PR description. Use a sensor suffix such as -gen4, -davis346, or -evk3 in the short name.

run_downstream_evaluation remains a NotImplementedError stub. The CLI preflight also rejects downstream evaluation until a verified, labelled, task-specific real fixture and the real training and evaluation harness are available.

Removing a fixture mirror

Remove its registry entry, update the registry test, and record the reason in the change description when a mirror is unavailable, corrupted, or its license is retracted.

Why this is a registry and not a single canonical URL

SRB does not own capture data. Multiple institutional and community mirrors can serve independent captures without making SRB or one storage bucket the single point of failure. See event-camera weight mirrors for the corresponding checkpoint registry.