vLAR commited on
Commit
068cb9a
·
verified ·
1 Parent(s): f5237c5

Upload README.md

Browse files
Files changed (1) hide show
  1. README.md +4 -10
README.md CHANGED
@@ -546,6 +546,9 @@ For each actor, the storage format depends on its `actor_type`:
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
  Each entry in `transform_data` describes the pose of the object or component at a specific frame:
550
 
551
  - `frame`: frame index in the sequence
@@ -555,16 +558,7 @@ Each entry in `transform_data` describes the pose of the object or component at
555
  - `rotation`: rotation quaternion
556
  - `scale`: 3D scale
557
 
558
- </div>
559
-
560
- <h3 id="trajectories" style="font-size: 1.35em; margin-top: 0.75em; margin-bottom: 0.22em; line-height: 1.2; margin-left: 0;"><span style="display: inline-block; width: 1.08em;">•</span>Trajectories</h3>
561
- <div style="margin-left: 16px;">
562
-
563
- Each sequence includes a same-named JSON file that records per-frame poses for selected dynamic objects in the world coordinate system. The file contains `sequence_info`, which stores basic sequence metadata such as frame count and `fps`, and `actors`, which stores object categories, asset index paths, actor types, and transformation data.
564
-
565
- For `solid` actors, the object is treated as a single rigid body, and its pose sequence is stored in the actor-level `transform_data` field. For `interactable` actors, poses are computed separately for each component; therefore, the actor-level `transform_data` is empty, while each component stores its own poses under `components[component_name].transform_data`.
566
-
567
- Each pose entry contains the frame index, timestamp, and transformation, including `location`, quaternion `rotation`, and `scale`.
568
 
569
  </div>
570
 
 
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
+
552
  Each entry in `transform_data` describes the pose of the object or component at a specific frame:
553
 
554
  - `frame`: frame index in the sequence
 
558
  - `rotation`: rotation quaternion
559
  - `scale`: 3D scale
560
 
561
+ </details>
 
 
 
 
 
 
 
 
 
562
 
563
  </div>
564