i/OrbbecSDK_ROS2
1
0
Fork 0
mirror of https://github.com/orbbec/OrbbecSDK_ROS2.git synced 2026-10-09 06:17:46 +08:00
Code Issues Packages Projects Releases Wiki Activity

docs: document ROS2 timestamp CSV outputs

Browse Source
This commit is contained in:
ob-yalian
2026-08-26 15:08:04 +08:00
parent bc029432b9
commit 8d92bb589e
2 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/en/source/camera_devices/6_benchmark/diagnostic_tools.md
+1 -1
View File
@@ -4,7 +4,7 @@ This section describes frame continuity, timestamp, topic statistics, end-to-end
## Frame Drop Log and Timestamp CSV Recording
After `enable_frame_drop_log` is enabled, the camera node prints color and depth frame drop statistics in the log. This helps locate frame drops at the SDK receive stage and ROS publish stage. When `frame_timestamp_csv_file` is set, the camera node also records color and depth frame timestamp data to a CSV file for analyzing frame continuity, publish latency, and timestamp anomalies.
After `enable_frame_drop_log` is enabled, the camera node prints color and depth frame drop statistics in the log. This helps locate frame drops at the SDK receive stage and ROS publish stage. When `frame_timestamp_csv_file` is set, the camera node records timestamp data for color, depth, and enabled IMU streams to CSV files for analyzing frame continuity, publish latency, and timestamp anomalies. When frame synchronization (`enable_frame_sync:=true`) is enabled, color and depth timestamps are combined into one CSV file; otherwise, they are written to separate `<stem>_color.csv` and `<stem>_depth.csv` files. Synchronized accelerometer and gyroscope data are written to `<stem>_imu.csv`, while standalone accelerometer and gyroscope data are written to `<stem>_accel.csv` and `<stem>_gyro.csv`. All CSV files follow the same rotation rule.
```bash
ros2 launch orbbec_camera gemini_330_series.launch.py \
docs/zh/source/camera_devices/6_benchmark/diagnostic_tools.md
+1 -1
View File
@@ -4,7 +4,7 @@
## 帧丢失日志与时间戳 CSV 记录
开启 `enable_frame_drop_log` 后，相机节点会在日志中输出彩色和深度帧丢失统计，用于定位 SDK 接收阶段和 ROS 发布阶段的丢帧。设置 `frame_timestamp_csv_file` 后，相机节点会额外记录彩色和深度帧的时间戳数据到 CSV 文件，用于分析帧连续性、发布延迟和时间戳异常。
开启 `enable_frame_drop_log` 后，相机节点会在日志中输出彩色和深度帧丢失统计，用于定位 SDK 接收阶段和 ROS 发布阶段的丢帧。设置 `frame_timestamp_csv_file` 后，节点会将彩色、深度以及已启用 IMU 流的时间戳记录到 CSV 文件，用于分析帧连续性、发布延迟和时间戳异常。启用帧同步（`enable_frame_sync:=true`）时，彩色和深度时间戳会汇聚到同一个 CSV 文件中；未启用时分别写入 `<stem>_color.csv` 和 `<stem>_depth.csv`。同步加速度计和陀螺仪数据写入 `<stem>_imu.csv`，独立加速度计和陀螺仪数据分别写入 `<stem>_accel.csv` 和 `<stem>_gyro.csv`。所有 CSV 文件遵循相同的分片规则。
```bash
ros2 launch orbbec_camera gemini_330_series.launch.py \