There has been some work started on adding the path planner and stripping out the 2016-specific content. For now, I believe it is finished (but untested) to create a class describing a path of waypoints, and some basic architecture to run a given path.
We will need to add in an event system integrated with the given path. This should allow the user to define "events" during the autonomous path cycle with timestamps to execute at, and callback functions to run. Callback functions can do actions like "raise arm" or "start shoot cycle".
There has been some work started on adding the path planner and stripping out the 2016-specific content. For now, I believe it is finished (but untested) to create a class describing a path of waypoints, and some basic architecture to run a given path.
We will need to add in an event system integrated with the given path. This should allow the user to define "events" during the autonomous path cycle with timestamps to execute at, and callback functions to run. Callback functions can do actions like "raise arm" or "start shoot cycle".