# HM3D adapter — CM-EVS

This package regenerates the HM3D portion of CM-EVS (401 rooms; paper reports 14,475 frames after local regeneration). **No HM3D-derived RGB-D frames are redistributed here**; users must independently accept the [HM3D EULA](https://aihabitat.org/datasets/hm3d/) and obtain the source data.

## Files

- `config.yaml` — curator parameters (input source, output root, resolution, grid spacing, K, conflict weight λ, early-stop thresholds, etc.). Same values as used in the paper.
- `pipeline.py` — adapter entry point (CM-EVS curator + HM3D-specific NavMesh / cluster / label-based room proposal).
- `metadata/source_manifest.json` — list of 401 HM3D scene IDs the paper's evaluation runs over.

## Reproducing the paper's HM3D frames

1. Obtain HM3D from <https://aihabitat.org/datasets/hm3d/> after accepting the EULA.
2. Place HM3D `.glb` files under `data/hm3d/<scene_id>/<scene_id>.glb` (matching `config.yaml`'s `pipeline.input_dir`).
3. Install the curator code from `../../code/`:
   ```bash
   conda env create -f ../../code/environment.yml
   conda activate cmevs
   ```
4. Run the pipeline:
   ```bash
   cd ../../code
   python pipelines/run_hm3d_pipeline.py --config ../adapters/hm3d/config.yaml
   ```
5. Outputs land in `outputs/hm3d/<scene_id>/{rgb, depth, pose, metadata}/...` under the unified CM-EVS schema (see `../../blender_indoor/README.md` for the schema).

The 401-room evaluation set is determined by `metadata/source_manifest.json`; the paper's reported HM3D numbers (§4.3 Table 4 and §5.4) are reproduced by running this exact set with the shipped config.

## What the adapter does

HM3D scenes contain multiple rooms in a single mesh, which would unfairly weight the curator toward whichever room dominates the AABB. This adapter solves it by:

1. **Space-unit proposal** (before the standard Phase 1): NavMesh / cluster / room-label segmentation of the HM3D scene into per-room "space units"; each unit is curated independently.
2. **Per-room Gini reporting** for transparency on frame allocation across rooms.
3. **Standard Phase 1–2** (candidate grid + 26-direction filter + conflict-aware greedy) is then applied per space unit.

See paper §3.4 (Table 2 row "HM3D") and `pipeline.py` for details.

## License

- This adapter code: **MIT** (see top-level `LICENSE.md`).
- HM3D-derived metadata (scene IDs, candidate metadata): bound by the **HM3D EULA**.
- Frames you produce by running this adapter on HM3D source data: bound by the HM3D EULA. The MIT license on the adapter does **not** override upstream terms for those frames.