|
1 | 1 | # Overview
|
| 2 | + |
2 | 3 | This package is used to enable GNSS and NDT to be used together in localization.
|
3 |
| -GNSS and NDT are different sources that generate poses for use in EKF. For EKF, |
4 |
| -the covariance values of the pose source are important. The GNSS system can provide |
| 4 | +GNSS and NDT are different sources that generate poses for use in EKF. For EKF, |
| 5 | +the covariance values of the pose source are important. The GNSS system can provide |
5 | 6 | us with its own error (RMSE) values. Using these error values, covariance values for
|
6 |
| -GNSS can be calculated. However, in default autoware, NDT covariance values are determined |
7 |
| -by default values. While this package manages which pose source will be used by reference |
8 |
| -to the error values coming from GNSS, it also manages situations where GNSS and NDT are used together. |
| 7 | +GNSS can be calculated. However, in default autoware, NDT covariance values are determined |
| 8 | +by default values. While this package manages which pose source will be used by reference |
| 9 | +to the error values coming from GNSS, it also manages situations where GNSS and NDT are used together. |
9 | 10 |
|
10 | 11 | ## Flowchart
|
11 |
| -Default Autoware Pose Source is only NDT: |
12 | 12 |
|
13 |
| - |
| 13 | +Default Autoware Pose Source is only NDT: |
| 14 | + |
| 15 | + |
| 16 | + |
| 17 | +You can see how autoware_pose_covariance_modifier_node works in the diagram below: |
14 | 18 |
|
15 |
| -You can see how autoware_pose_covariance_modifier_node works in the diagram below: |
| 19 | + |
| 20 | + |
| 21 | +## Activate This Feuture |
16 | 22 |
|
17 |
| - |
18 |
| -## Activate This Feuture |
19 | 23 | This package is not used by default autoware, you need to activate it to use it.
|
20 | 24 |
|
21 |
| -To activate, you need to change the `use_autoware_pose_covariance_modifier` parameter to true within the [tier4_localization_launch](https://github.com/autowarefoundation/autoware.universe/blob/main/launch/tier4_localization_launch/launch/localization.launch.xml |
22 |
| -). |
| 25 | +To activate, you need to change the `use_autoware_pose_covariance_modifier` parameter to true within the [tier4_localization_launch](https://github.com/autowarefoundation/autoware.universe/blob/main/launch/tier4_localization_launch/launch/localization.launch.xml). |
| 26 | + |
23 | 27 | # Node
|
| 28 | + |
24 | 29 | ## Subscribed Topics
|
25 |
| -| Name | Type | Description | |
26 |
| -|-------------------------------------| ------------------------------------------------ |------------------------| |
27 |
| -| `input_trusted_pose_with_cov_topic` | `geometry_msgs::msg::PoseWithCovarianceStamped` | Input GNSS pose topic. | |
28 |
| -| `input_ndt_pose_with_cov_topic` | `geometry_msgs::msg::PoseWithCovarianceStamped` | Input NDT pose topic. | |
| 30 | + |
| 31 | +| Name | Type | Description | |
| 32 | +| ----------------------------------- | ----------------------------------------------- | ---------------------- | |
| 33 | +| `input_trusted_pose_with_cov_topic` | `geometry_msgs::msg::PoseWithCovarianceStamped` | Input GNSS pose topic. | |
| 34 | +| `input_ndt_pose_with_cov_topic` | `geometry_msgs::msg::PoseWithCovarianceStamped` | Input NDT pose topic. | |
29 | 35 |
|
30 | 36 | ## Published Topics
|
31 |
| -| Name | Type | Description | |
32 |
| -|-------------------------------------| ------------------------------------------------ |-----------------------------------------------------------------------| |
33 |
| -| `output_pose_with_covariance_topic` | `geometry_msgs::msg::PoseWithCovarianceStamped` | Output pose topic. It will be sent as input to ekf_localizer package. | |
| 37 | + |
| 38 | +| Name | Type | Description | |
| 39 | +| ----------------------------------- | ----------------------------------------------- | --------------------------------------------------------------------- | |
| 40 | +| `output_pose_with_covariance_topic` | `geometry_msgs::msg::PoseWithCovarianceStamped` | Output pose topic. It will be sent as input to ekf_localizer package. | |
34 | 41 |
|
35 | 42 | ## Parameters
|
36 |
| -| Name | Type | Description | |
37 |
| -|-----------------------------|------------|--------------------------------------------------------------------------------| |
38 |
| -| `gnss_error_reliable_max` | `double` | Threshold value for the range in which GNSS error is most reliable. | |
39 |
| -| `gnss_error_unreliable_min` | `double` | Threshold value at which GNSS error is not considered reliable. | |
40 |
| -| `yaw_error_deg_threshold` | `double` | Threshold value to understand whether the yaw error is within reliable limits. | |
41 | 43 |
|
42 |
| -### Important Notes: |
43 |
| -* In order to use this package, your GNSS sensor must provide you with the error value. If you do not have a GNSS sensor that provides you with the error value, you cannot use this package. |
| 44 | +| Name | Type | Description | |
| 45 | +| --------------------------- | -------- | ------------------------------------------------------------------------------ | |
| 46 | +| `gnss_error_reliable_max` | `double` | Threshold value for the range in which GNSS error is most reliable. | |
| 47 | +| `gnss_error_unreliable_min` | `double` | Threshold value at which GNSS error is not considered reliable. | |
| 48 | +| `yaw_error_deg_threshold` | `double` | Threshold value to understand whether the yaw error is within reliable limits. | |
| 49 | + |
| 50 | +### Important Notes |
44 | 51 |
|
| 52 | +- In order to use this package, your GNSS sensor must provide you with the error value. If you do not have a GNSS sensor that provides you with the error value, you cannot use this package. |
0 commit comments