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

Using Unordered Map for dynamic obstacle validity checking #1

Open
JustinKottinger opened this issue Apr 27, 2023 · 0 comments
Open
Assignees
Labels
enhancement New feature or request

Comments

@JustinKottinger
Copy link
Collaborator

Using an unordered map for dynamic obstacle collision checking is not very clean. In addition, the current implementation does not account for robots with different propagation step sizes. A better solution would be to add a method to og::Path and oc::Path to return a state along the path at a given time. Not only will this resolve the aforementioned issue, it could possibly outperform the unordered_map, which averages O(1) complexity, with a vector lookup, which has truly O(1) complexity. Then, the collision checkers can use this method instead of relying on the map.

@JustinKottinger JustinKottinger self-assigned this Apr 27, 2023
@JustinKottinger JustinKottinger added the enhancement New feature or request label Apr 27, 2023
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

When branches are created from issues, their pull requests are automatically linked.

1 participant