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

Solved Maze Memory #13

Open
acbuynak opened this issue Aug 2, 2022 · 0 comments
Open

Solved Maze Memory #13

acbuynak opened this issue Aug 2, 2022 · 0 comments
Labels
enhancement New feature or request

Comments

@acbuynak
Copy link
Member

acbuynak commented Aug 2, 2022

Once a maze is solved a few times, it is unnecessary to continually re-solve the maze just to update the position of the maze relative to the camera. A potential solution could be to separate vision capabilities:

  • maze board tracking
  • maze image segmentation, maze solver, and path registration
  • tool path planner

Once segmented, all three components would be utilized to find and solve the maze initially. After a few successful solves, it is safe to assume the maze is known and will not change (unless a new maze is introduced). The successful solves could average the resulting local path and be fed into a tool path planner.

Assuming the maze doesn't change, the board tracking and tool path planner could be called to update the path as the maze moves around in the environment, but computation time not wasted on image segmentation and solving.
If deployed, the image segmentation should only be called periodically to ensure the maze hasn't changed.

@acbuynak acbuynak added the enhancement New feature or request label Aug 2, 2022
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