From b58eff29ce9fa8afa8b35bc9e7dde8492cda2f23 Mon Sep 17 00:00:00 2001 From: Yamato Ando Date: Thu, 25 Jan 2024 14:40:00 +0900 Subject: [PATCH] fix(ndt_scan_matcher): fix type of critical_upper_bound_exe_time_ms (#819) * fix type Signed-off-by: Yamato Ando * fix order Signed-off-by: Yamato Ando --------- Signed-off-by: Yamato Ando --- .../config/localization/ndt_scan_matcher.param.yaml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/autoware_launch/config/localization/ndt_scan_matcher.param.yaml b/autoware_launch/config/localization/ndt_scan_matcher.param.yaml index 9bc62d3f91..a5a4941bfe 100644 --- a/autoware_launch/config/localization/ndt_scan_matcher.param.yaml +++ b/autoware_launch/config/localization/ndt_scan_matcher.param.yaml @@ -54,6 +54,9 @@ # Tolerance of distance difference between two initial poses used for linear interpolation. [m] initial_pose_distance_tolerance_m: 10.0 + # The execution time which means probably NDT cannot matches scans properly. [ms] + critical_upper_bound_exe_time_ms: 100.0 + # Number of threads used for parallel computing num_threads: 4 @@ -98,6 +101,3 @@ # If lidar_point.z - base_link.z <= this threshold , the point will be removed z_margin_for_ground_removal: 0.8 - - # The execution time which means probably NDT cannot matches scans properly. [ms] - critical_upper_bound_exe_time_ms: 100