-
Notifications
You must be signed in to change notification settings - Fork 34
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
feat(lidar_centerpoint): priotizing voxel processing by space #1672
feat(lidar_centerpoint): priotizing voxel processing by space #1672
Conversation
This commit adds the `priority_map` array to the `preprocess_kernel.hpp` and `centerpoint_trt.hpp` files. The `priority_map` is a new CUDA array that is allocated and initialized in the `PreprocessKernelTest::SetUp()` function. The `priority_map` is used in the `generateBaseFeatures_launch()` function to generate base features for the voxel grid. The `priority_map` is also used in the `centerpoint_trt.hpp` file for initializing and updating the `priority_map_` member variable. Signed-off-by: Taekjin LEE <[email protected]>
…tPriorityMap() This commit modifies the `CenterPointTRT::initPriorityMap()` function to initialize and assign a priority score map. The priority score map is created using the `priority_map` vector, which contains pairs of scores and indices. The map is sorted in descending order based on the scores and then assigned to the `priority_map_` member variable. This change improves the efficiency of the priority map initialization process. feat: initialize and assign priority score map in CenterPointTRT::initPriorityMap() Signed-off-by: Taekjin LEE <[email protected]>
Signed-off-by: Taekjin LEE <[email protected]>
This commit refactors the `CenterPointTRT::initPriorityMap()` function to optimize its performance. The changes include: - Simplifying the calculation of `pos_x` and `pos_y` - Introducing two new variables, `score_a` and `score_b`, to calculate the total score - Adjusting the weights of `score_a` and `score_b` to improve the accuracy of the priority map These optimizations enhance the efficiency and accuracy of the priority map initialization process. Signed-off-by: Taekjin LEE <[email protected]>
Signed-off-by: Taekjin LEE <[email protected]>
Signed-off-by: Taekjin LEE <[email protected]> refactor: optimize CenterPointTRT::initPriorityMap() refactor: optimize CenterPointTRT::initPriorityMap()
4c7e93f
to
7e8a3f8
Compare
Signed-off-by: Taekjin LEE <[email protected]>
Signed-off-by: Taekjin LEE <[email protected]>
Quality Gate passedIssues Measures |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
v4.0.1 is a temporary version for testing in many ODDs and I think this PR will prevent some edge cases in the test driving. LGTM for merge this into this version.
This PR will be replaced by #1688 |
Description
@TomohitoAndo
こちら、centerpointのmax voxelを超える出力があった際の挙動を調整するPRです。
基本的には今お台場でやっているvoxel sizeの調整がメインで万一漏れた際のセーフティとしてこのPRが活きてくるイメージでいます by Yoshi Ri
Current voxel processing is done by order of X, Y sequentially.
IF the number of filled voxel exceed the ML model limit, the detectable range is limited.
The priority map is set by a scalar field as following.
The following visualization is to show filled voxel distribution. Configurations are as follwing.
Then lower score object will be shown (due to the lower score_threshold), indirectly visualize where the voxel is filled.
Related links
warn the voxel number reaches the limit
feat(autoware_lidar_centerpoint): added a check to notify if we are dropping pillars autowarefoundation/autoware.universe#9488
chore(autoware_lidar_transfusion): added a warning if we are dropping voxels autowarefoundation/autoware.universe#9486
PR for AWF
feat(autoware_lidar_centerpoint): add priority map to preprocess kernel and centerpoint_trt autowarefoundation/autoware.universe#9583
ticket
https://tier4.atlassian.net/browse/RT1-8767
How was this PR tested?
Processing time
left: Before this PR
right: After this PR
Notes for reviewers
None.
Interface changes
None.
Effects on system behavior
None.