example_data / README.md
syhsyhsyh's picture
Reorganize examples by material, scenario and sample
65371f8 verified
|
Raw History Blame Contribute Delete
4.19 kB

Twelve-scenario examples

One source instance from each of the twelve scenario families is included. Seven examples have a paired, officially retained appearance-transfer video; the remaining five contain raw data only. No experimental gas transfers are included. These are illustrative examples, not the official benchmark split.

Material Scenario Sample ID Transfer
rigid rigid-falling_objects falling_objects_0098 Included
rigid rigid-rolling_objects rolling_objects_0037 Included
rigid rigid-dominoes dominoes_0000 Included
soft soft-falling_objects_on_soft_pad falling_objects_on_soft_pad_0029 Included
soft soft-gravity_draping_flag gravity_draping_flag_0033 Included
soft soft-gravity_tightening_soft_rope gravity_tightening_soft_rope_0041 Included
liquid fluid-rigid_objects_in_water_tank rigid_objects_in_water_tank_0012 Not available
liquid fluid-draining_tank draining_tank_0010 Included
liquid fluid-u_connector u_connector_0012 Not available
gas gas-gas_smoke_stack gas_smoke_stack_0012 Not available
gas gas-impact_smoke_dispersion impact_smoke_dispersion_0012 Not available
gas gas-gas_flame_heating gas_flame_heating_0012 Not available

Each sample keeps reference/render.mp4, source scene JSON files, reference/frames/, and reference/render_assets/. When available, the paired appearance variant is stored under transfer/ next to reference/, using its variant name (such as appearance_00.mp4 or black_disc.mp4). Videos and annotations are copied without resizing or re-encoding. Existing source directory and filename conventions are preserved.

Solid/liquid examples contain RGB, ID-mask, depth, and normal frames as supplied by their source. Gas examples contain RGB and per-object opacity channels under frames/mask/<object_id>/frame_XXXX.png; consult render_assets/pass_metadata.json for encoding and object identities. These are not ordinary binary masks. Data presence does not certify compatibility with every evaluator mode; full rigid scoring still requires the evaluator's complete reference contract and reviewed actor semantics.

manifest.json records relative reference/transfer paths, the original transfer filename, frame-file counts, and video SHA-256 hashes. A paired transfer is an appearance variant of the same source instance, not a model prediction or a replacement for raw simulation annotations.

The generation example manifest covers all twelve cases, using transfer frame 0 where available and raw frame 0 otherwise. Its prompts and seed 42 are demonstrations, not the official paper configuration. See Usage and the generation protocol.

Source scene files may retain environment-specific asset paths. Adapt those before rerendering. Source masks and meshes remain unchanged and should be interpreted with their accompanying metadata.

Local directory layout

The current local example root is data/. A separate example_data/ download uses the same internal layout.

data/
├── manifest.json
├── rigid/
│   └── dominoes/
│       └── dominoes_0000/
│           ├── reference/
│           │   ├── render.mp4
│           │   ├── frames/
│           │   └── render_assets/
│           └── transfer/
│               └── appearance_00.mp4
├── soft/gravity_draping_flag/gravity_draping_flag_0033/
│   ├── reference/
│   └── transfer/black_disc.mp4
├── liquid/u_connector/u_connector_0012/reference/
└── gas/smoke_stack/gas_smoke_stack_0012/reference/

Directory names for gas are smoke_stack, impact_smoke_dispersion, and flame_heating; original source IDs retain their gas_ prefixes where present. CLI identifiers remain gas_smoke_stack, impact_smoke_dispersion, and gas_flame_heating, as recorded in the manifest. Raw-only cases have no transfer/ directory. All manifest paths are relative to this root.