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

Port auto system to command robot #52

Open
7 tasks
IanTapply22 opened this issue Dec 18, 2023 · 0 comments
Open
7 tasks

Port auto system to command robot #52

IanTapply22 opened this issue Dec 18, 2023 · 0 comments
Labels
enhancement New feature or request high priority This is a high priority issue release critical This feature or bug needs to be merged before we release this project publicly

Comments

@IanTapply22
Copy link
Member

IanTapply22 commented Dec 18, 2023

This is just to port over the auto system to use a command-based system. This should all be new code and I think we can say that we can move on from our old system which has served us many years. The migration to using WPILib commands over our old command-based system is critical for the integrity of our code which will hopefully serve us another decade or two.

You can find the requirements for this system in the following:

  • Create a "main" class to house the auto inner-workings.
  • An auto chooser. Used to select the autonomous mode we want to run for the match via controller bindings.
  • Integrate our drive system with the auto system. This will give capabilities of our robot to drive on its own.
  • Create auto-only commands. These will sort of act like building blocks to create our autos and will only be accessible in the autonomous period.
  • Create commands for our subsystems. Allows us to utilize our subsystems (arm, intake, etc) during our autonomous period AND our teleoperated period. These should technically already be made when making subsystems, but this should be on the list of requirements.
  • Integrate PathPlanner with our codebase to create custom paths using an easy-to-use UI.
  • Create an example auto using PathPlanner. This will just give an example to teams on how to use PathPlanner and use it in their codebase.

All of the above can be done in separate PRs and should all be relatively small (200-300 lines of code at the MAX).

Time Estimate: 8 hours

@IanTapply22 IanTapply22 added enhancement New feature or request high priority This is a high priority issue labels Dec 18, 2023
@IanTapply22 IanTapply22 added this to the Porting 2023 Code milestone Dec 18, 2023
@IanTapply22 IanTapply22 added the release critical This feature or bug needs to be merged before we release this project publicly label Dec 18, 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 high priority This is a high priority issue release critical This feature or bug needs to be merged before we release this project publicly
Projects
None yet
Development

No branches or pull requests

1 participant