forked from autowarefoundation/autoware_launch
-
Notifications
You must be signed in to change notification settings - Fork 4
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
fix(localization): add ar tag based localizer param (autowarefoundati…
…on#871) Added ar_tag_based_localizer.param.yaml Signed-off-by: Shintaro Sakoda <[email protected]>
- Loading branch information
1 parent
1cf2e8f
commit 6a2320e
Showing
2 changed files
with
43 additions
and
0 deletions.
There are no files selected for viewing
40 changes: 40 additions & 0 deletions
40
autoware_launch/config/localization/ar_tag_based_localizer.param.yaml
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,40 @@ | ||
/**: | ||
ros__parameters: | ||
# marker_size | ||
marker_size: 0.6 | ||
|
||
# target_tag_ids | ||
target_tag_ids: ['0','1','2','3','4','5','6'] | ||
|
||
# base_covariance | ||
# This value is dynamically scaled according to the distance at which AR tags are detected. | ||
base_covariance: [0.2, 0.0, 0.0, 0.0, 0.0, 0.0, | ||
0.0, 0.2, 0.0, 0.0, 0.0, 0.0, | ||
0.0, 0.0, 0.2, 0.0, 0.0, 0.0, | ||
0.0, 0.0, 0.0, 0.02, 0.0, 0.0, | ||
0.0, 0.0, 0.0, 0.0, 0.02, 0.0, | ||
0.0, 0.0, 0.0, 0.0, 0.0, 0.02] | ||
|
||
# Detect AR-Tags within this range and publish the pose of ego vehicle | ||
distance_threshold: 13.0 # [m] | ||
|
||
# consider_orientation | ||
consider_orientation: false | ||
|
||
# Detector parameters | ||
# See https://github.com/pal-robotics/aruco_ros/blob/7787a6794d30c248bc546d1582e65dd47bc40c12/aruco/include/aruco/markerdetector.h#L106-L126 | ||
detection_mode: "DM_NORMAL" # select from [DM_NORMAL, DM_FAST, DM_VIDEO_FAST] | ||
min_marker_size: 0.02 | ||
|
||
# Parameters for comparison with EKF Pose | ||
# If the difference between the EKF pose and the current pose is within the range of values set below, the current pose is published. | ||
# [How to determine the value] | ||
# * ekf_time_tolerance: Since it is abnormal if the data comes too old from EKF, the tentative tolerance value is set at 5 seconds. | ||
# This value is assumed to be unaffected even if it is increased or decreased by some amount. | ||
# * ekf_position_tolerance: Since it is possible that multiple AR tags with the same ID could be placed, the tolerance should be as small as possible. | ||
# And if the vehicle is running only on odometry in a section without AR tags, | ||
# it is possible that self-position estimation could be off by a few meters. | ||
# it should be fixed by AR tag detection, so tolerance should not be smaller than 10 meters. | ||
# Therefore, the tolerance is set at 10 meters. | ||
ekf_time_tolerance: 5.0 # [s] | ||
ekf_position_tolerance: 10.0 # [m] |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters