Upload README.md
Browse files
README.md
CHANGED
|
@@ -536,16 +536,26 @@ Each scene includes a `caption.txt` file containing an English paragraph that de
|
|
| 536 |
|
| 537 |
Each sequence includes a JSON file with the same name as the sequence. This file records the per-frame poses of selected dynamic objects, including their rotations and translations in the world coordinate system.
|
| 538 |
|
|
|
|
|
|
|
|
|
|
| 539 |
The JSON file contains two main parts:
|
| 540 |
|
| 541 |
- `sequence_info`: basic information about the sequence, such as the total number of frames and the frame rate (`fps`).
|
| 542 |
- `actors`: pose and metadata for dynamic objects, including object category, asset index path, actor type, and transformation data.
|
| 543 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 544 |
For each actor, the storage format depends on its `actor_type`:
|
| 545 |
|
| 546 |
- If `actor_type` is `solid`, the object is treated as a single rigid body. Its per-frame pose is stored in the actor-level `transform_data` field, while the `components` field is empty.
|
| 547 |
- If `actor_type` is `interactable`, the object is represented by multiple components. The actor-level `transform_data` field is empty, and the per-component poses are stored under `components[component_name].transform_data`.
|
| 548 |
|
|
|
|
|
|
|
| 549 |
<details>
|
| 550 |
<summary><strong>Pose entry format in <code>transform_data</code></strong></summary>
|
| 551 |
|
|
|
|
| 536 |
|
| 537 |
Each sequence includes a JSON file with the same name as the sequence. This file records the per-frame poses of selected dynamic objects, including their rotations and translations in the world coordinate system.
|
| 538 |
|
| 539 |
+
<details>
|
| 540 |
+
<summary><strong>JSON file structure</strong></summary>
|
| 541 |
+
|
| 542 |
The JSON file contains two main parts:
|
| 543 |
|
| 544 |
- `sequence_info`: basic information about the sequence, such as the total number of frames and the frame rate (`fps`).
|
| 545 |
- `actors`: pose and metadata for dynamic objects, including object category, asset index path, actor type, and transformation data.
|
| 546 |
|
| 547 |
+
</details>
|
| 548 |
+
|
| 549 |
+
<details>
|
| 550 |
+
<summary><strong>Actor-level pose storage</strong></summary>
|
| 551 |
+
|
| 552 |
For each actor, the storage format depends on its `actor_type`:
|
| 553 |
|
| 554 |
- If `actor_type` is `solid`, the object is treated as a single rigid body. Its per-frame pose is stored in the actor-level `transform_data` field, while the `components` field is empty.
|
| 555 |
- If `actor_type` is `interactable`, the object is represented by multiple components. The actor-level `transform_data` field is empty, and the per-component poses are stored under `components[component_name].transform_data`.
|
| 556 |
|
| 557 |
+
</details>
|
| 558 |
+
|
| 559 |
<details>
|
| 560 |
<summary><strong>Pose entry format in <code>transform_data</code></strong></summary>
|
| 561 |
|