This repository has been archived by the owner on Nov 16, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 1
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
3 changed files
with
82 additions
and
13 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
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,62 @@ | ||
# Lidar Distance Utility | ||
|
||
**Summary:** | ||
|
||
This node can filter points from a [PoinCloud2](http://docs.ros.org/en/melodic/api/sensor_msgs/html/msg/PointCloud2.html) | ||
which are located in a given bounding box. | ||
It then publishes a filtered [PoinCloud2](http://docs.ros.org/en/melodic/api/sensor_msgs/html/msg/PointCloud2.html) containing | ||
the points located in the given restriction. | ||
Additionally, it publishes a [Range](http://docs.ros.org/en/melodic/api/sensor_msgs/html/msg/Range.html) message | ||
containing the closest and the farest point. | ||
This can then be used to detect the distance to the closest object in front of us. | ||
|
||
--- | ||
|
||
## Author | ||
|
||
Tim Dreier | ||
|
||
## Date | ||
|
||
16.03.2023 | ||
|
||
--- | ||
<!-- TOC --> | ||
* [Title of wiki page](#title-of-wiki-page) | ||
* [Author](#author) | ||
* [Date](#date) | ||
* [Prerequisite](#prerequisite) | ||
* [Some Content](#some-content) | ||
* [more Content](#more-content) | ||
* [Sources](#sources) | ||
<!-- TOC --> | ||
|
||
## Configuration | ||
|
||
The possible params for this node are summed up in the following table: | ||
|
||
| Parameter | Description | Default value | | ||
|-------------------|-------------------------------------------------------|-----------------------------------| | ||
| min_x | Minimum x value of the coordinate | `np.inf` | | ||
| max_x | Maximum x value of the coordinate | `np.inf` | | ||
| min_y | Minimum y value of the coordinate | `np.inf` | | ||
| max_y | Maximum y value of the coordinate | `np.inf` | | ||
| min_z | Minimum z value of the coordinate | `np.inf` | | ||
| max_z | Maximum z value of the coordinate | `np.inf` | | ||
| point_cloud_topic | Topic to publish the filtered PointCloud2 | `/carla/hero/<namespace>filtered` | | ||
| range_topic | Topic to publish the Range | `/carla/hero/<namespace>_range` | | ||
| source_topic | Topic on which the PointCloud2 messages are read from | `/carla/hero/LIDAR` | | ||
|
||
### Example | ||
|
||
```xml | ||
<node pkg="perception" type="lidar_distance.py" name="lidar_distance" output="screen"> | ||
<param name="max_y" value="1.5"/> | ||
<param name="min_y" value="-1.5"/> | ||
<param name="min_x" value="2.5"/> | ||
<param name="min_z" value="-1.5"/> | ||
<param name="max_z" value="0"/> | ||
<param name="point_cloud_topic" value="/carla/hero/LIDAR_filtered"/> | ||
<param name="range_topic" value="/carla/hero/LIDAR_range"/> | ||
</node> | ||
``` |