# EventActivityNet v1.0 Release Notes

## Release Status

EventActivityNet v1.0 has completed technical validation and is suitable for public release as documented HDF5 files and scale manifests.

## Highlights

- 3,263 validated HDF5 files.
- Approximately 4.36 TB total size.
- 5-bin event voxel representation.
- 200 verified action classes.
- Large train/validation split: 2,316 / 947.
- Three nested scales: Large, Medium, Small.
- Final production integrity audit: PASS.

## Scale Summary

| Scale | Videos | Hours | Train | Validation | Classes | Event-friendly |
|---|---:|---:|---:|---:|---:|---:|
| Large | 3,263 | 106.94 | 2,316 | 947 | 200 | 65.31% |
| Medium | 1,537 | 50.00 | 1,074 | 463 | 200 | 64.80% |
| Small | 667 | 20.00 | 473 | 194 | 200 | 64.62% |

Small is a strict subset of Medium, and Medium is a strict subset of Large.

## Integrity

The final read-only production audit confirmed:

- exactly 3,263 production HDF5 files;
- all files open successfully;
- zero truncated or unreadable files;
- zero structural warnings;
- every file contains `events`, `voxel_event_start`, and `voxel_event_count`;
- all files use `num_bins=5`;
- no temporary files remain in the production dataset.

Exact reproducibility values:

- total size: 4,355,745,895,245 bytes;
- Large duration: 106.941600381 hours;
- Medium duration: 50.000000128 hours;
- Small duration: 20.000000374 hours.

## Caveats

- EventActivityNet v1.0 covers 200 verified action classes. Do not claim 203 classes for this release.
- The historical/paper Large duration of 107.3 hours is approximate relative to recovered release metadata. The verified Large duration is 106.94 hours.
- Medium and Small are newly generated deterministic nested v1.0 release scales, not historical original subsets.
- Durations in the release manifests use `src_fmt_dur` from verification metadata.
- Original subset generation merged train and validation before sampling. Train/validation assignments remain recoverable from ActivityNet Captions split membership.

## Recommended Hugging Face Packaging

Preserve per-video HDF5 identity in manifests. For payload upload, tar shards around 20 GB are recommended to balance repository object count, resumability, and user access.

Estimated shard counts from the publication audit:

- 10 GB target: about 435 shards.
- 20 GB target: about 218 shards.
- 50 GB target: about 87 shards.