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
|`topic_time_stamp`| the time stamp of input topic | none | none | no |
268
268
|`sensor_points_size`| the size of sensor points | the size is 0 | none | yes |
269
-
|`sensor_points_delay_time_sec`| the delay time of sensor points | the time is **longer** than `validation.lidar_topic_timeout_sec`| none | yes |
269
+
|`sensor_points_delay_time_sec`| the delay time of sensor points | the time is **longer** than `sensor_points.timeout_sec`| none | yes |
270
270
|`is_succeed_transform_sensor_points`| whether transform sensor points is succeed or not | none | failed | yes |
271
271
|`sensor_points_max_distance`| the max distance of sensor points | the max distance is **shorter** than `sensor_points.required_distance`| none | yes |
272
272
|`is_activated`| whether the node is in the "activate" state or not | not "activate" state | none | if `is_activated` is false, then estimation is not executed and `skipping_publish_num` is set to 0. |
@@ -280,9 +280,9 @@ initial_pose_offset_model_x & initial_pose_offset_model_y must have the same num
280
280
|`nearest_voxel_transformation_likelihood`| the score of how well the map aligns with the sensor points | the score is **smaller** than `score_estimation.converged_param_nearest_voxel_transformation_likelihood` (only in the case of `score_estimation.converged_param_type` is 1=NEAREST_VOXEL_TRANSFORMATION_LIKELIHOOD) | none | yes |
281
281
|`nearest_voxel_transformation_likelihood_diff`| the nvtl score difference for the current ndt optimization | none | none | no |
282
282
|`nearest_voxel_transformation_likelihood_before`| the nvtl score before the current ndt optimization | none | none | no |
283
-
|`distance_initial_to_result`| the distance between the position before convergence processing and the position after | the distance is **longer** than 3 | none | no |
283
+
|`distance_initial_to_result`| the distance between the position before convergence processing and the position after | the distance is **longer** than `validation.initial_to_result_distance_tolerance_m`| none | no |
284
284
|`execution_time`| the time for convergence processing | the time is **longer** than `validation.critical_upper_bound_exe_time_ms`| none | no |
285
-
|`skipping_publish_num`| the number of times rejected estimation results consecutively | the number of times is 5 or more| none | - |
285
+
|`skipping_publish_num`| the number of times rejected estimation results consecutively | the number of times is `validation.skipping_publish_num` or more | none | - |
286
286
287
287
※The `sensor_points_callback` shares the same callback group as the `trigger_node_service` and `ndt_align_service`. Consequently, if the initial pose estimation takes too long, this diagnostic may become stale.
Copy file name to clipboardexpand all lines: localization/ndt_scan_matcher/schema/sub/sensor_points.json
+7-1
Original file line number
Diff line number
Diff line change
@@ -5,13 +5,19 @@
5
5
"sensor_points": {
6
6
"type": "object",
7
7
"properties": {
8
+
"timeout_sec": {
9
+
"type": "number",
10
+
"description": "Tolerance of timestamp difference between current time and sensor pointcloud. [sec]",
11
+
"default": 1.0,
12
+
"minimum": 0.0
13
+
},
8
14
"required_distance": {
9
15
"type": "number",
10
16
"description": "Required distance of input sensor points [m]. If the max distance of input sensor points is lower than this value, the scan matching will not be performed.",
0 commit comments