-
Notifications
You must be signed in to change notification settings - Fork 659
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
new ground_segmentation filter #4443
Comments
Looks great! I'm actually implementing patchwork++ and I want to update it combining with TRAVEL. Therefore if you get any progress let's discuss about it! https://github.com/ktro2828/autoware.universe/tree/feat/patchworkpp |
Thanks for your interest, excellent work! I will not be able to work on this project next week. I am waiting for your thoughts and future improvements with curiosity. After that, we can work together! |
This pull request has been automatically marked as stale because it has not had recent activity. |
@yusufy1ld1z |
Hello again, apologies for a long break. I have not changed anything since the last update because I thought I already finished the project when I opened this issue. I think @ktro2828 has done a well job but I could not find the package of him after the last updates in the Autoware. If you still interested in my job I am ready to make updates you desire. Initially I adopted my project as an option to ground filters already in the perception ground segmentation stack and I am still agree with that. What are your further thoughts about the project, I am looking forward to open a PR ! |
@ktro2828 Do you have any idea about this? |
This pull request has been automatically marked as stale because it has not had recent activity. |
Checklist
Description
There are many ground points in the output of the current ground filter. I have tried the algorithm accepted by RA-L with IROS'22 option named "TRAVEL: Traversable Ground and Above-Ground Object Segmentation using Graph Representation for 3D LiDAR Scans". The proposed algorithm is sensible and works better in accuracy and processing time than the scan_ground_filter. Due to the fact that this project is licensed with GPL-3.0, I am rewriting the code, making it more performant, and also adapting to Autoware stack by adding pointcloud_preprocessor, etc.
There is an comparison video of two algorithms :
https://youtu.be/VkzRjY9xLdk
Purpose
To give more precise output by the obstacle_segmentation/ground_filter with lowering the processing_time_ms.
Possible approaches
Adding the travel_ground_filter among the other filters as an option
Definition of done
The text was updated successfully, but these errors were encountered: