You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 1deec9e
Browse filesBrowse the repository at this point in the historyBrowse files
refactor!: remove deprecated t_us field from xyzit and en_xyzit point types (#95)
* refactor!: remove deprecated t_us field from xyzit and en_xyzit point types
Drop the `t_us` field from `PointXYZIT` and `PointEnXYZIT` (struct
definitions and PCL registrations), stop populating it in the Seyond
decoder, and remove README / script references to it. `time_stamp`
(uint32, nanoseconds from scan start) is now the sole per-point
relative timestamp.
BREAKING CHANGE: output PointCloud2 messages for `xyzit` and
`en_xyzit` no longer contain a `t_us` field. Downstream consumers must
read `time_stamp` (uint32 ns) instead. This was previously announced
as "Will be removed in v1.0.0".
* style: reformat PCL_REGISTER_POINT_STRUCT layout for PointXYZIT and PointEnXYZIT
Copy file name to clipboardExpand all lines: README.md
-8Lines changed: 0 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -193,7 +193,6 @@ The output bag file contains `sensor_msgs::msg::PointCloud2` messages on topics
193
193
-`y` (float32): Y coordinate in meters
194
194
-`z` (float32): Z coordinate in meters
195
195
-`intensity` (float32): Intensity value in [0, 255]. Robin W uses packet-version-dependent scaling; see [docs/seyond_intensity_scaling.md](docs/seyond_intensity_scaling.md).
196
-
-`t_us` (uint32): Relative timestamp in microseconds from the scan start time (xyzit, en_xyzit only). **Will be removed in v1.0.0**; use `time_stamp` instead.
197
196
-`time_stamp` (uint32): Relative timestamp in nanoseconds from the scan start time (xyzit, en_xyzit only)
198
197
199
198
**Extended fields** (en_xyzit only): availability mask, refl_type, elongation, lidar_status, lidar_mode, packet version, lidar_type, is_2nd_return, multi_return_mode, and use_reflectance. Full layout, flag semantics, and value tables are in [docs/en_xyzit.md](docs/en_xyzit.md).
@@ -203,7 +202,6 @@ The output bag file contains `sensor_msgs::msg::PointCloud2` messages on topics
203
202
All timestamps in PointCloud2 messages are based on UTC (Coordinated Universal Time).
204
203
205
204
-**`header.stamp`**: Absolute timestamp representing the scan start time in UTC. This timestamp is generated by the LiDAR and represents when the scan began.
206
-
-**`t_us` field**: Relative timestamp in microseconds from the scan start time (`header.stamp`). **Will be removed in v1.0.0**; use `time_stamp` instead.
207
205
-**`time_stamp` field**: Relative timestamp in nanoseconds from the scan start time (`header.stamp`)
208
206
209
207
The absolute timestamp for each point (in nanoseconds, UTC) can be calculated as:
@@ -212,12 +210,6 @@ The absolute timestamp for each point (in nanoseconds, UTC) can be calculated as
0 commit comments