Physical EVK4 Intake

Runbook for converting a physical Prophesee EVK4 capture into the SRB event-camera validation layout.

This page is for contributors running a physical EVK4 hardware capture. If you only work with synthetic event data, you can safely skip it.

Target Layout

event_camera_physical/
  events_manifest.jsonl
  episodes/
    evk4_reference.h5
    evk4_reference.flow.npz          # event_flow labels
    evk4_reference.detections.jsonl  # detection labels
  README.md

See the downstream validation sidecar contract for the event schema and task-specific label fields.

Capture Stub

The unavailable reservation command is srb dataset capture-real-evk4:

Unavailable: This build has no validated hardware capture backend or device contract. CLI preflight rejects the command before it creates output. Create the layout by hand.

Label Template

Unavailable: downstream validation currently supports only --synthetic-smoke. Preflight rejects the template and target-check forms below before writing output. The documented label shapes are contract skeletons; downstream harness and model adapter are not available.

Intended template form (preflight rejects it in this build):

srb dataset validate-events downstream \
  --synth-events /data/srb/synth/events.h5 \
  --real-events /data/srb/event_camera_physical/episodes/evk4_reference.h5 \
  --task event_flow \
  --output /tmp/downstream_stub.json \
  --write-label-template

For event_flow, the template contains one zero-flow frame with valid_mask=False everywhere. For detection, the template contains one timestamped record with no boxes. These files are valid contract skeletons, not finished labels.

Validate once labels have been filled:

srb dataset validate-events downstream \
  --synth-events /data/srb/synth/events.h5 \
  --real-events /data/srb/event_camera_physical/episodes/evk4_reference.h5 \
  --task event_flow \
  --output /tmp/downstream_stub.json \
  --check-real-target

Before sharing captures, confirm redistribution terms, attribution, and curation. Record SHA256, byte size, event count, resolution, task, policy ID, and capture date in the dataset card or adjacent README.

Fetch a registered fixture with srb event-camera fetch-fixture.