LuMonDepth commited on
Commit
47228e5
·
verified ·
1 Parent(s): e86cbab

Update README.md

Browse files
Files changed (1) hide show
  1. README.md +2 -0
README.md CHANGED
@@ -33,6 +33,8 @@ The dataset contains approximately 3,228 synchronized image pairs (totaling ~1.9
33
 
34
  ### Technical Specifications
35
  * **Resolution:** All images (both RGB and Depth) are `1280x720` pixels.
 
 
36
  * **Synchronization:** Input images and their corresponding depth maps are perfectly paired using matching UNIX timestamps in their filenames (e.g., `left_1736612498.png` corresponds directly to `depth_1736612498.png`).
37
  * **Depth Format (Important):** The depth maps are saved as **8-bit Grayscale PNGs** (`mode="L"` in PIL/OpenCV). Pixel values are integers ranging from `0` to `255`. Note that because this specific simulation split lacks an absolute metric scale, these 8-bit values represent **relative (normalized) depth** rather than absolute metric distances in meters.
38
 
 
33
 
34
  ### Technical Specifications
35
  * **Resolution:** All images (both RGB and Depth) are `1280x720` pixels.
36
+ * **Stereo Baseline:** The simulated stereo camera setup has a baseline of 12 cm.
37
+ * **Sequence Type:** The dataset represents a custom continuous trajectory sequence captured within the simulator.
38
  * **Synchronization:** Input images and their corresponding depth maps are perfectly paired using matching UNIX timestamps in their filenames (e.g., `left_1736612498.png` corresponds directly to `depth_1736612498.png`).
39
  * **Depth Format (Important):** The depth maps are saved as **8-bit Grayscale PNGs** (`mode="L"` in PIL/OpenCV). Pixel values are integers ranging from `0` to `255`. Note that because this specific simulation split lacks an absolute metric scale, these 8-bit values represent **relative (normalized) depth** rather than absolute metric distances in meters.
40