1
- # pose_estimator_arbiter
1
+ # autoware_pose_estimator_arbiter
2
2
3
3
Table of contents:
4
4
@@ -35,7 +35,7 @@ Also, even if both can be activated at the same time, the Kalman Filter may be a
35
35
- [ ndt_scan_matcher] ( https://github.com/autowarefoundation/autoware.universe/tree/main/localization/ndt_scan_matcher )
36
36
- [ eagleye] ( https://autowarefoundation.github.io/autoware-documentation/main/how-to-guides/integrating-autoware/launch-autoware/localization/eagleye/ )
37
37
- [ yabloc] ( https://github.com/autowarefoundation/autoware.universe/tree/main/localization/yabloc )
38
- - [ landmark_based_localizer] ( https://github.com/autowarefoundation/autoware.universe/tree/main/localization/landmark_based_localizer )
38
+ - [ landmark_based_localizer] ( https://github.com/autowarefoundation/autoware.universe/tree/main/localization/autoware_landmark_based_localizer )
39
39
40
40
### Demonstration
41
41
@@ -117,8 +117,8 @@ If it does not seems to work, users can get more information in the following wa
117
117
> [ !TIP]
118
118
>
119
119
> ``` bash
120
- > ros2 service call /localization/pose_estimator_arbiter /config_logger logging_demo/srv/ConfigLogger \
121
- > ' {logger_name: localization.pose_estimator_arbiter , level: debug}'
120
+ > ros2 service call /localization/autoware_pose_estimator_arbiter /config_logger logging_demo/srv/ConfigLogger \
121
+ > ' {logger_name: localization.autoware_pose_estimator_arbiter , level: debug}'
122
122
> ` ` `
123
123
124
124
# # Architecture
@@ -135,7 +135,7 @@ Following figure shows the node configuration when NDT, YabLoc Eagleye and AR-Ta
135
135
136
136
# ## Case of running multiple pose estimators
137
137
138
- When running multiple pose_estimators, pose_estimator_arbiter is executed.
138
+ When running multiple pose_estimators, autoware_pose_estimator_arbiter is executed.
139
139
It comprises a ** switching rule** and ** stoppers** corresponding to each pose_estimator.
140
140
141
141
- Stoppers control the pose_estimator activity by relaying inputs or outputs, or by requesting a suspend service.
@@ -187,14 +187,14 @@ ros2 launch autoware_launch logging_simulator.launch.xml \
187
187
Even if ` pose_source ` includes an unexpected string, it will be filtered appropriately.
188
188
Please see the table below for details.
189
189
190
- | given runtime argument | parsed pose_estimator_arbiter 's param (pose_sources) |
191
- | ------------------------------------------- | ---------------------------------------------------- |
192
- | ` pose_source:=ndt ` | ` ["ndt"] ` |
193
- | ` pose_source:=nan ` | ` [] ` |
194
- | ` pose_source:=yabloc_ndt ` | ` ["ndt","yabloc"] ` |
195
- | ` pose_source:=yabloc_ndt_ndt_ndt ` | ` ["ndt","yabloc"] ` |
196
- | ` pose_source:=ndt_yabloc_eagleye ` | ` ["ndt","yabloc","eagleye"] ` |
197
- | ` pose_source:=ndt_yabloc_nan_eagleye_artag ` | ` ["ndt","yabloc","eagleye","artag"] ` |
190
+ | given runtime argument | parsed autoware_pose_estimator_arbiter 's param (pose_sources) |
191
+ | ------------------------------------------- | ------------------------------------------------------------- |
192
+ | ` pose_source:=ndt ` | ` ["ndt"] ` |
193
+ | ` pose_source:=nan ` | ` [] ` |
194
+ | ` pose_source:=yabloc_ndt ` | ` ["ndt","yabloc"] ` |
195
+ | ` pose_source:=yabloc_ndt_ndt_ndt ` | ` ["ndt","yabloc"] ` |
196
+ | ` pose_source:=ndt_yabloc_eagleye ` | ` ["ndt","yabloc","eagleye"] ` |
197
+ | ` pose_source:=ndt_yabloc_nan_eagleye_artag ` | ` ["ndt","yabloc","eagleye","artag"] ` |
198
198
199
199
</details >
200
200
0 commit comments