Upload README.md
Browse files
README.md
CHANGED
|
@@ -193,6 +193,9 @@ homepage: https://vlar-group.github.io/PhysInOne.html
|
|
| 193 |
• <a href="#segmentation">Segmentation</a><br>
|
| 194 |
• <a href="#captions">Captions</a><br>
|
| 195 |
• <a href="#trajectories">Trajectories</a><br>
|
|
|
|
|
|
|
|
|
|
| 196 |
• <a href="#cameras">Cameras</a><br>
|
| 197 |
◦ <a href="#camera-json-structure">Camera JSON structure</a><br>
|
| 198 |
◦ <a href="#dynamic-camera-behavior">Dynamic camera behavior</a><br>
|
|
@@ -537,7 +540,7 @@ Each scene includes a `caption.txt` file containing an English paragraph that de
|
|
| 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 |
|
|
@@ -547,7 +550,7 @@ The JSON file contains two main parts:
|
|
| 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 |
|
|
@@ -557,7 +560,7 @@ For each actor, the storage format depends on its `actor_type`:
|
|
| 557 |
</details>
|
| 558 |
|
| 559 |
<details>
|
| 560 |
-
<summary><strong>Pose entry format in <code>transform_data</code></strong></summary>
|
| 561 |
|
| 562 |
Each entry in `transform_data` describes the pose of the object or component at a specific frame:
|
| 563 |
|
|
|
|
| 193 |
• <a href="#segmentation">Segmentation</a><br>
|
| 194 |
• <a href="#captions">Captions</a><br>
|
| 195 |
• <a href="#trajectories">Trajectories</a><br>
|
| 196 |
+
◦ <a href="#trajectory-json-file-structure">JSON file structure</a><br>
|
| 197 |
+
◦ <a href="#trajectory-actor-level-pose-storage">Actor-level pose storage</a><br>
|
| 198 |
+
◦ <a href="#trajectory-pose-entry-format">Pose entry format</a><br>
|
| 199 |
• <a href="#cameras">Cameras</a><br>
|
| 200 |
◦ <a href="#camera-json-structure">Camera JSON structure</a><br>
|
| 201 |
◦ <a href="#dynamic-camera-behavior">Dynamic camera behavior</a><br>
|
|
|
|
| 540 |
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.
|
| 541 |
|
| 542 |
<details>
|
| 543 |
+
<summary id="trajectory-json-file-structure"><strong>JSON file structure</strong></summary>
|
| 544 |
|
| 545 |
The JSON file contains two main parts:
|
| 546 |
|
|
|
|
| 550 |
</details>
|
| 551 |
|
| 552 |
<details>
|
| 553 |
+
<summary id="trajectory-actor-level-pose-storage"><strong>Actor-level pose storage</strong></summary>
|
| 554 |
|
| 555 |
For each actor, the storage format depends on its `actor_type`:
|
| 556 |
|
|
|
|
| 560 |
</details>
|
| 561 |
|
| 562 |
<details>
|
| 563 |
+
<summary id="trajectory-pose-entry-format"><strong>Pose entry format in <code>transform_data</code></strong></summary>
|
| 564 |
|
| 565 |
Each entry in `transform_data` describes the pose of the object or component at a specific frame:
|
| 566 |
|