Making a path planning abstraction that avoids standard obstacles.#646
Draft
Making a path planning abstraction that avoids standard obstacles.#646
Conversation
rokadias
force-pushed
the
saqib/swerve-point-path-planning
branch
from
6cbe351 to
064eae6
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why are we doing this?
Making last year's swerve point mapping capable year over year.
Whats changing?
I've created FieldObstacles that are irrespective of which year. The obstacles are likely going to either match into a circle or rectangular shape, but can be considered tough or not as well.
Tough terrain may allow us to decide at times whether we'd like to trek through it or not, (e.g. Bump for 2026 model)
Questions/notes for reviewers
How this was tested