description: The robot state is tracked currently by two main objects, one is the self.robot.hull.position in robot_obstacles.py, and the second is the self.maze object in the same file. This is primarily used because we need a discrete grid for A* -- however, this isn't a very robust and dynamic way to store the robot position, since it means that the A* pathfinding needs to start from the closest maze tile to the robot hull.
criteria
- brainstorm a new way to store the state, and submit an empty pull request detailing the plan
description: The robot state is tracked currently by two main objects, one is the
self.robot.hull.positioninrobot_obstacles.py, and the second is theself.mazeobject in the same file. This is primarily used because we need a discrete grid for A* -- however, this isn't a very robust and dynamic way to store the robot position, since it means that the A* pathfinding needs to start from the closest maze tile to the robot hull.criteria