forked from autowarefoundation/autoware.universe
-
Notifications
You must be signed in to change notification settings - Fork 34
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #388 from tier4/sync-upstream
chore: sync upstream
- Loading branch information
Showing
54 changed files
with
2,329 additions
and
781 deletions.
There are no files selected for viewing
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
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,10 @@ | ||
cmake_minimum_required(VERSION 3.14) | ||
project(map4_localization_launch) | ||
|
||
find_package(autoware_cmake REQUIRED) | ||
autoware_package() | ||
|
||
ament_auto_package(INSTALL_TO_SHARE | ||
eagleye_pose_twist_localization_launch | ||
eagleye_twist_localization_launch | ||
) |
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,44 @@ | ||
# map4_localization_launch | ||
|
||
This localization launch package is a sample package to introduce eagleye into autoware. | ||
|
||
Eagleye provides a cost-effective alternative to LiDAR and point cloud-based localization by using low-cost GNSS and IMU sensors to provide vehicle position and orientation. | ||
|
||
Autoware users will be able to choose between their existing LiDAR and point cloud-based localization stacks or GNSS/IMU-based eagleye localizer, depending on their specific needs and operating environment. | ||
|
||
In addition to the LiDAR-based solution provided by `tier4_localization_launch` (shown in the first row of the following table), there are two ways to utilize eagleye in `map4_localization_launch` with the autoware localization stack. | ||
|
||
| localization launch | twist estimator | pose estimator | | ||
| --------------------------------------------------------------- | --------------------------------- | --------------------------------- | | ||
| tier4_localization_launch | gyro_odometry | ndt_scan_matcher | | ||
| map4_localization_launch/eagleye_twist_localization_launch | eagleye_rt(gyro/odom/gnss fusion) | ndt_scan_matcher | | ||
| map4_localization_launch/eagleye_pose_twist_localization_launch | eagleye_rt(gyro/odom/gnss fusion) | eagleye_rt(gyro/odom/gnss fusion) | | ||
|
||
## Structure | ||
|
||
- eagleye_twist_localization_launch | ||
|
||
![map4_localization_launch/eagleye_twist_localization_launch](./eagleye_twist_localization_launch/localization_launch.drawio.svg) | ||
|
||
- eagleye_pose_twist_localization_launch | ||
|
||
![map4_localization_launch/eagleye_pose_twist_localization_launch](./eagleye_pose_twist_localization_launch/localization_launch.drawio.svg) | ||
|
||
## Package Dependencies | ||
|
||
Please see `<exec_depend>` in `package.xml`. | ||
|
||
## Usage | ||
|
||
Include `localization.launch.xml` in other launch files as follows. | ||
|
||
Note that you should provide parameter paths as `PACKAGE_param_path`. The list of parameter paths you should provide is written at the top of `localization.launch.xml`. | ||
|
||
```xml | ||
<include file="$(find-pkg-share map4_localization_launch)/eagleye_twist_localization_launch/localization.launch.xml"> | ||
<!-- Parameter files --> | ||
<arg name="FOO_param_path" value="..."/> | ||
<arg name="BAR_param_path" value="..."/> | ||
... | ||
</include> | ||
``` |
33 changes: 33 additions & 0 deletions
33
...h/map4_localization_launch/eagleye_pose_twist_localization_launch/localization.launch.xml
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,33 @@ | ||
<?xml version="1.0"?> | ||
<launch> | ||
<!-- Parameter files --> | ||
<arg name="localization_error_monitor_param_path"/> | ||
<arg name="ekf_localizer_param_path"/> | ||
<arg name="pose_initializer_param_path"/> | ||
<arg name="pose_initializer_common_param_path"/> | ||
<arg name="eagleye_param_path"/> | ||
|
||
<!-- localization module --> | ||
<group> | ||
<push-ros-namespace namespace="localization"/> | ||
<!-- util module --> | ||
<group> | ||
<push-ros-namespace namespace="util"/> | ||
<include file="$(find-pkg-share map4_localization_launch)/eagleye_pose_twist_localization_launch/util/util.launch.xml"/> | ||
</group> | ||
<!-- pose_twist_estimator module --> | ||
<group> | ||
<push-ros-namespace namespace="pose_twist_estimator"/> | ||
<include file="$(find-pkg-share map4_localization_launch)/eagleye_pose_twist_localization_launch/pose_twist_estimator/pose_twist_estimator.launch.xml"/> | ||
</group> | ||
<!-- pose_twist_fusion_filter module --> | ||
<group> | ||
<push-ros-namespace namespace="pose_twist_fusion_filter"/> | ||
<include file="$(find-pkg-share tier4_localization_launch)/launch/pose_twist_fusion_filter/pose_twist_fusion_filter.launch.xml"/> | ||
</group> | ||
<!-- localization_error_monitor_module --> | ||
<group> | ||
<include file="$(find-pkg-share tier4_localization_launch)/launch/localization_error_monitor/localization_error_monitor.launch.xml"/> | ||
</group> | ||
</group> | ||
</launch> |
Oops, something went wrong.