You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The proposed enhancement introduces a ring-based filtering mechanism to the existing functionality of the repository. This feature aims to remove unwanted points from specified rings within defined angle ranges, specifically targeting reflected and vehicle points directly within the driver. The intention is to elude crop box filters to decrease the delay of the sensing pipeline.
Details
The key aspects of this feature include:
Point Removal: The feature allows for the removal of points based on their position within specified rings.
Ring and Angle Specification: Users will be able to define which rings they want to apply filtering to. Each ring will be associated with one or more angle ranges for removal.
Angle Ranges: For each specified ring, users can define multiple angle ranges within which points should be removed. These angle ranges are determined by the starting and ending angles.
Fine-Tuned Filtering: The ability to define multiple angle ranges for a single ring provides fine-tuned control over the filtering process, enabling users to selectively remove points.
Expected Behavior: Upon enabling the invalid_point_remove option and specifying the relevant invalid_rings, invalid_angles_start, and invalid_angles_end configurations, the ring-based filter will remove points located within the defined angle ranges for the specified rings.
Could you please provide any feedback, suggestions, and guidance on the proposed enhancement @drwnz@amc-nu ?
The text was updated successfully, but these errors were encountered:
@mebasoglu thank you for the proposal.
I imagine this works at the decoder level, requiring an implementation for each sensor? This would be the fastest implementation, but require more work in implementation than adding a separate node which filters from the output pointcloud and publishes a new topic.
Yes, I thought a decoder level implementation for each sensor, so that we can deactivate crop box filters to remove vehicle points.
It could be also useful to remove reflected points from the vehicle's glasses:
Overview
The proposed enhancement introduces a ring-based filtering mechanism to the existing functionality of the repository. This feature aims to remove unwanted points from specified rings within defined angle ranges, specifically targeting reflected and vehicle points directly within the driver. The intention is to elude crop box filters to decrease the delay of the sensing pipeline.
Details
The key aspects of this feature include:
Point Removal: The feature allows for the removal of points based on their position within specified rings.
Ring and Angle Specification: Users will be able to define which rings they want to apply filtering to. Each ring will be associated with one or more angle ranges for removal.
Angle Ranges: For each specified ring, users can define multiple angle ranges within which points should be removed. These angle ranges are determined by the starting and ending angles.
Fine-Tuned Filtering: The ability to define multiple angle ranges for a single ring provides fine-tuned control over the filtering process, enabling users to selectively remove points.
Usage Example:
Expected Behavior: Upon enabling the
invalid_point_remove
option and specifying the relevantinvalid_rings
,invalid_angles_start
, andinvalid_angles_end
configurations, the ring-based filter will remove points located within the defined angle ranges for the specified rings.Could you please provide any feedback, suggestions, and guidance on the proposed enhancement @drwnz @amc-nu ?
The text was updated successfully, but these errors were encountered: