Skip to content
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✨]: Efficient coneMap.msg data structure #85

Open
1 task done
dyu056 opened this issue Mar 1, 2024 · 0 comments
Open
1 task done

[✨FEAT✨]: Efficient coneMap.msg data structure #85

dyu056 opened this issue Mar 1, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@dyu056
Copy link
Contributor

dyu056 commented Mar 1, 2024

Is there an existing enhancement request for this?

  • I have searched the existing feature requests

Description

The simulation shows that the current cone map node and path planning node can not catchup the speed of the car after there are large number of cones recorded in the ConeMap message we are using for path planning and localization. Currently it is O(nlog(n)) complex to order the cones from the coneMap msg. It is desired that the trajectory planning node is just able to grab a sub set of the pre sorted cones in constant time.
Please produce a improved data collection to store cones in an array format and provide functions for building, appending and moving cones within that structure. Change the coneMap message appropriately if applicable.
The structure is to be used by the Trajectory Planning node the Cone Mapping node is responsible for creating and manipulating the data structure.

Additional Information

No response

@dyu056 dyu056 added the enhancement New feature or request label Mar 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant