crosstyan/zed-playground
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

refactor: things

Browse Source
This commit is contained in:
crosstyan
2026-03-06 17:17:59 +08:00
parent 8c6087683f
commit 33ab1a5d9d
171 changed files with 293 additions and 29894 deletions
Download Patch File Download Diff File Expand all files Collapse all files
workspaces/py_workspace/.sisyphus/notepads/depth-unit-audit/learnings.md
+13
View File
@@ -0,0 +1,13 @@
# Depth Unit Scaling Patterns
## Findings
- **Native SDK Scaling**: `depth_sensing.py` uses `init_params.coordinate_units = sl.UNIT.METER`.
- **Manual Scaling**: `aruco/svo_sync.py` uses `depth_data / 1000.0` because it leaves `coordinate_units` at the default (`MILLIMETER`).
## Risks
- **Double-Scaling**: If `svo_sync.py` is updated to use `sl.UNIT.METER` in `InitParameters`, the manual `/ 1000.0` MUST be removed, otherwise depth values will be 1000x smaller than intended.
- **Inconsistency**: Different parts of the codebase handle unit conversion differently (SDK-level vs. Application-level).
## Recommendations
- Standardize on `sl.UNIT.METER` in `InitParameters` across all ZED camera initializations.
- Remove manual `/ 1000.0` scaling once SDK-level units are set to meters.